Result for 1D9AFE568637CCED0C1F4D7C65FE31A3E4C216EA

Query result

Key Value
FileName./usr/lib/ibacm/libibacmp.so
FileSize61712
MD5658A25FD8BBD1246ABF926ABA2BED70B
SHA-11D9AFE568637CCED0C1F4D7C65FE31A3E4C216EA
SHA-256DBF33B4B814899411DC2B25B43B477551FC14A783D5AB95B5356D25F9A488D30
SSDEEP768:0ltr+PfM4lgR7A2qlrFtKxXwwsugn23r9KXqL4cPfuTHcAA4UYf9n9RvZeIRnn8M:MKPfrl52YZzRvqmzcwrvUIRf
TLSHT11F53F8ACBBE3C4F1E15295B017AB5BA234708144D227FAA3EF08F31674667A53D16339
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