Result for AF007A08F0DBFC535741E5E784C91F6684F47361

Query result

Key Value
FileName./usr/bin/ib_acme
FileSize45180
MD520007EE4523D2EB323934ED3AF9BB870
SHA-1AF007A08F0DBFC535741E5E784C91F6684F47361
SHA-25666A62E09146AFDCD1CC5564B359515CB48EDB108D06E77B6F5A8D98A67A06F3C
SSDEEP768:Ytn5Bt5w9/aj5o5ZnktAjkQWvu7LF+yXvSLIRj:Ytn5BjN5o55yAjV97bSkRj
TLSHT161133974F787C230C0D281B45E5B56113131C05723A7EAA3B9ACB525F3A2AE4AF5B27D
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
MD5177644DF6863214DF05F03009B2F1805
PackageArchi686
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.
PackageMaintainerCentOS Buildsys <bugs@centos.org>
PackageNameibacm
PackageRelease4.el8
PackageVersion32.0
SHA-18E0696B9F323BD9F2E6C1AE18DB5CF1122895563
SHA-256CA6494E0DF513EA3512E948E409381BFDBFD8F48393DA1BC6B5EA581FECBFC2E