Result for 4C4CC42E65A38804EA181B25F5E3BE3E29603633

Query result

Key Value
FileName./usr/share/java/httpcomponents/httpcore-nio.jar
FileSize683043
MD598C2349ED09D74EA396EAC599DE42A30
SHA-14C4CC42E65A38804EA181B25F5E3BE3E29603633
SHA-256F7894617ECE1C321051FADD2CD0222B64AC6F12670CFE97EA41AA7FAB167B2BB
SSDEEP12288:cSajkepJ0cjheaSZMS0/zFWDFTskAWAJZCaSZtCCnCyZRUnldkpNSW:Ejkeb0iheES0/zM5Tp7vtFCyZYd2V
TLSHT159E4C09EDCE57079EE67D23198524A9BE43E8098D14B51BF34FC5F8794A18CA6F03328
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
MD58E022A42A9EBFA630FE9CEE06074EC95
PackageArchnoarch
PackageDescriptionHttpCore is a set of low level HTTP transport components that can be used to build custom client and server side HTTP services with a minimal footprint. HttpCore supports two I/O models: blocking I/O model based on the classic Java I/O and non-blocking, event driven I/O model based on Java NIO. The blocking I/O model may be more appropriate for data intensive, low latency scenarios, whereas the non-blocking model may be more appropriate for high latency scenarios where raw data throughput is less important than the ability to handle thousands of simultaneous HTTP connections in a resource efficient manner.
PackageMaintainerFedora Project
PackageNamehttpcomponents-core
PackageRelease1.module_f28+4409+43f8f627
PackageVersion4.4.11
SHA-18311940DAA3355A7A629D63997F53BAC94733A77
SHA-256B852E73CB8344B8956D62823E0EE2A2B3D01ECE75058F9B829B640C1F231438A
Key Value
MD58448844877E55454CB0D565CF066F125
PackageArchnoarch
PackageDescriptionHttpCore is a set of low level HTTP transport components that can be used to build custom client and server side HTTP services with a minimal footprint. HttpCore supports two I/O models: blocking I/O model based on the classic Java I/O and non-blocking, event driven I/O model based on Java NIO. The blocking I/O model may be more appropriate for data intensive, low latency scenarios, whereas the non-blocking model may be more appropriate for high latency scenarios where raw data throughput is less important than the ability to handle thousands of simultaneous HTTP connections in a resource efficient manner.
PackageMaintainerFedora Project
PackageNamehttpcomponents-core
PackageRelease1.module_f28+4409+43f8f627
PackageVersion4.4.11
SHA-13324424E045A841626772C9E1A756FCF2B3E0038
SHA-25654126A46046CE827DCBF57429DD76F202ABFFFBF3BC7CB8C04011EF40D1CC41D