Result for 66A5B4D3B0105439C62F04823D9435ED07A09BC7

Query result

Key Value
FileName./usr/bin/ib_acme
FileSize68984
MD5B4AB9EE4C21675651186A81459F5F64B
SHA-166A5B4D3B0105439C62F04823D9435ED07A09BC7
SHA-256B7DC1A407C5F50C0602425747082815502238908320054ADE77AF04F7C6A90B6
SSDEEP1536:uZA+lsjSI/uFszS5gnGtkbqA3Gd0b6BoKo4eIE7ce2HU397cTXhGM:uO7ce8JX/
TLSHT1BA63E77DF78A7416C292C7B5BF861390FBB1D09C8352C29F340E926CD787D985BA6284
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
MD5F6AD12C256C0593AB61F0E90F30956FE
PackageArchaarch64
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
PackageRelease3.fc24
PackageVersion1.2.0
SHA-1BA23C112044EB7B058A7BF47C0F64F8A9CFCB1E0
SHA-256C56ED2F4DE21FA1368BBC40CEB109C2CC663B1B674DA9CA7307353E97E12509F