Result for 424652FC29EA7F53A8B20E0B9F6C8036C73D426B

Query result

Key Value
FileName./usr/share/maven-repo/org/apache/logging/log4j/log4j-jul/debian/log4j-jul-debian.pom
FileSize2076
MD52102D02B79AEB3FA161337BCD2C950E7
SHA-1424652FC29EA7F53A8B20E0B9F6C8036C73D426B
SHA-2561AC94AD4E72C683121FD1C2D2BC747556C6E7C03BF70F0575E1AD7D1DF0558D5
SSDEEP48:cprxskFKLK10edH31wETp8wHxHlQqbVwpy1HLh1qFJ1yuM:2ukFKL6THFwIHxe01H1AJon
TLSHT1D34133A9F08EDAB1528C0AD6DE3E8056B77BE5BC9049C388F48AC055676D4BA00F7172
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
FileSize1716040
MD530AC6CFCF1D71F5767E4EBE071707CE5
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.10.0-2
SHA-1DC1623BF2471FC800B7BDD1A4024389D32584DA1
SHA-256E0697DA5CB1C4C4B8AFF17F7AB20910112E659814CC165413F243D3E40CA53A4
Key Value
FileSize1710912
MD596A4474B88C18F70D2115D4330C7AAB1
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.10.0-2ubuntu0.1
SHA-1144CFEA5746CAEE37BF02F0E6BB5FB335A0874B6
SHA-2563BF9550B629B9E3740EAFDC4D0A224285F35B10502C6AFEDF34B5E4A005BAF72