Result for 2825E25734D26146070B3357204A397CD25727B3

Query result

Key Value
FileName./usr/share/maven-repo/org/apache/logging/log4j/log4j-jcl/2.11.1/log4j-jcl-2.11.1.pom
FileSize2087
MD5D4BE80526373097AF66BCC5EF8729BCF
SHA-12825E25734D26146070B3357204A397CD25727B3
SHA-256E6835D5941146D7A60AAD3CDD03D219AF8D0DF639DB2A3C442074991AD68D00E
SSDEEP48:cNxKAhNIAh0ehzH31cyp8wHxH3aqbV78a8j+vrp/xq2hBiBXFJ1qU:2QAPIAPzHFcMHxK88a8iLq6CJr
TLSHT1694144A8A4CDDA3153DC4EC5EF2AC456AB7BE1BC9049C3D8F04AC045676C4BA01F6172
hashlookup:parent-total2
hashlookup:trust60

Network graph view

Parents (Total: 2)

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

Key Value
FileSize1721364
MD5D5E4F88D8BA27EA77BDB8A75777D057C
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.11.1-2
SHA-11511CFDB6E9E633D06DC98FACD0FEB2235D1614A
SHA-2564857F694C1A933B69E8A63DC72170885C37172F5FB2D851B3F8A795C88D2D239
Key Value
FileSize1716416
MD5735A1BAAED98F6D05491DD2968881946
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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNameliblog4j2-java
PackageSectionjava
PackageVersion2.11.1-2
SHA-17C8B022F4053C8D951973D977857CADAFAF04856
SHA-25603E18E78E69BEC05BA5FC9FC6DE11B306F263EC2DDACBDCBBB6D8D0590B2EEE1