Result for 6B5250AD212941B3C3E5C4948701072F621E5F77

Query result

Key Value
FileName./usr/share/doc/httpcomponents-core-4.1.4/RELEASE_NOTES.txt
FileSize35849
MD5771C43C393712CE00D294C9B10140BB5
SHA-16B5250AD212941B3C3E5C4948701072F621E5F77
SHA-25611025410FCFDF7E32B3FF214D652436D054F5D5DE2FCBCF44D0E555CE8F6A42C
SSDEEP768:/+urzS+8fL8xwug5m8lyD0Y8WW6m6Id7JSzvpCllfKg19Z+:/jf4fIxwuCfZWW6CfSzs8
TLSHT111F253313E4A37354E03D4D7DBC39500EBFAA99CE7A554F2958DC41C218A8A891BF7D8
hashlookup:parent-total3
hashlookup:trust65

Network graph view

Parents (Total: 3)

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

Key Value
MD5E9DC76DDFDEFEAE10ADCCCD37AE7A576
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.fc17
PackageVersion4.1.4
SHA-1FCA5089A3BEF68BB91F69A73ED8542829DEACD55
SHA-256F050013D9F325299FC6B8A14C2C65AF34E1EF4336FDF5C962EC1AFC1AB27678D
Key Value
MD5A059DB16DA3E6545CD639B972CBDD47B
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.fc17
PackageVersion4.1.4
SHA-1958A95DD8D2C988CC2D53DA7E58A2D4F17A2AA68
SHA-25698849B8B77628CC9C1EA47C4B1E9B96B3EE087BE09AD2F0D8D5588C1AF5C4D36
Key Value
MD5AC6DB1CC2ADBB3EFACC983D9155A78FA
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.fc17
PackageVersion4.1.4
SHA-1FDD205DA20779D880C3F00306F57F70F8981CBFE
SHA-2563F0C4AF69DEF0AD646599209CB16E3BE3CFDCBDF7DF2C7D7D082F824301770F2