Result for 438DFA8FE914DD17FAEC1BAA0ECB92A9943A86D9

Query result

Key Value
FileName./usr/share/java/log4j-1.2-api.jar
FileSize199436
MD539D068DC58D89BB19A7A7A81446A2796
SHA-1438DFA8FE914DD17FAEC1BAA0ECB92A9943A86D9
SHA-256AE1C4E4F9A0995EFC00D6F096E5D0FB0335016FA9F205C28254CB0302F0DFD31
SSDEEP3072:ReThd+by6N6xuT8GXA/IsniN28yWzVNBD2rufFF7E6NDyZg6kRUtHo9UW/lVm2F+:RMhdyr64T/AwsctBuqEIX64USF+
TLSHT12414C077D04C1226F037067B80D19E2364BB50DCD48FE16B546E227B883ACA666FB379
hashlookup:parent-total1
hashlookup:trust55

Network graph view

Parents (Total: 1)

The searched file hash is included in 1 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
FileSize2080200
MD568E09F47EFD064E0D21CD52BB51A04D5
PackageDescriptionApache Log4j - Logging Framework for Java Apache Log4j 2 is an upgrade to Log4j that provides significant improvements over its predecessor, Log4j 1.x: . API Separation: The API for Log4j is separate from the implementation making it clear for application developers which classes and methods they can use while ensuring forward compatibility. . Improved Performance: Log4j 2 contains next-generation Asynchronous Loggers based on the LMAX Disruptor library. In multi-threaded scenarios Asynchronous Loggers have 10 times higher throughput and orders of magnitude lower latency than Log4j 1.x. . Support for multiple APIs: While the Log4j 2 API will provide the best performance, Log4j 2 provides support for the SLF4J and Commons Logging APIs. . Automatic Reloading of Configurations: Log4j 2 can automatically reload its configuration upon modification. It will do so without losing log events while reconfiguration is taking place. . Advanced Filtering: Log4j 2 supports filtering based on context data, markers, regular expressions, and other components in the Log event. Filtering can be specified to apply to all events before being passed to Loggers or as they pass through Appenders. . Plugin Architecture: Log4j uses the plugin pattern to configure components. As such, no code is needed to create and configure an Appender, Layout, Pattern Converter, and so on. Log4j automatically recognizes plugins and uses them when a configuration references them. . Property Support: Properties can be referenced in a configuration, Log4j will directly replace them, or Log4j will pass them to an underlying component that will dynamically resolve them. Properties come from values defined in the configuration file, system properties, environment variables, the ThreadContext Map, and data present in the event.
PackageMaintainerDebian Java Maintainers <pkg-java-maintainers@lists.alioth.debian.org>
PackageNameliblog4j2-java
PackageSectionjava
PackageVersion2.17.0-1
SHA-114FB53E20A27AAA1301F88D314C2AFC09D8E8754
SHA-256AE785BF30505F6DC7C2D7D60C3BDDC85A4D9462E99FE2BDA142EE0AFE0678326