Result for 13A05539DB0FA6C61822F7B19D9EFC42315C9F7A

Query result

Key Value
FileName./usr/bin/ib_acme
FileSize49984
MD5265C8AC181AACC2497A3142FFFA4D280
SHA-113A05539DB0FA6C61822F7B19D9EFC42315C9F7A
SHA-2569D2D178658430EB5E0B5666D5FC0BC9C523E19677443DD93B25CCB94A7823F97
SSDEEP768:jGaw45g4QoAYwIg4QoAYwIg4QbTLD7zrjbTLD7zrjbTLD7zrjbTLD7zTkHOkzb/i:PHb/2PYcjrgDm
TLSHT191230815AA910078C092D933CEDF81567EB1F9996332272F358CA3763F4B9274E6AD70
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
MD5E03B2636886981ED8DC3D27CFC45F1DD
PackageArchx86_64
PackageDescriptionThe ibacm daemon helps reduce the load of managing path record lookups on large InfiniBand fabrics by providing a user space implementation of what is functionally similar to an ARP cache. The use of ibacm, when properly configured, can reduce the SA packet load of a large IB cluster from O(n^2) to O(n). The ibacm daemon is started and normally runs in the background, user applications need not know about this daemon as long as their app uses librdmacm to handle connection bring up/tear down. The librdmacm library knows how to talk directly to the ibacm daemon to retrieve data.
PackageMaintainerFedora Project
PackageNameibacm
PackageRelease1.fc32
PackageVersion28.0
SHA-17E23FECC7B32CBD25633DF4067A6E9CB47D87CCB
SHA-256F0294C8565ACA3C6E93378460EBF52F6E09DB3EB30421C10BAC5848A486CA147