Result for 2707D5E839A2AF7ACFAAF226E462AE35F1767B49

Query result

Key Value
FileName./usr/lib/debug/xen-4.14.3.efi.map.gz
FileSize46623
MD573F48AD1E49A83CE87B3A0B71D88A47B
SHA-12707D5E839A2AF7ACFAAF226E462AE35F1767B49
SHA-256B9E062FD5397B149364DEBC45EFF03507590E4254395DBC351088AEDF0B787BF
SSDEEP768:JRx/WmTT6ZBgUupfE2N1ekc4X8FisnB7c6EOqDp3U8N9X04spBr:j3KB+pE2D9RX8xnB7c6xU3U8vk4sXr
TLSHT13823023D0B305C072308ADFCBADE1A3D59379130C264856AE6543C979B3B67A1B3868F
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
FileSize3494608
MD5CBCEC8CC55237EE548F89D3651104A75
PackageDescriptionXen Hypervisor on AMD64 The hypervisor is the "core" for XEN itself. It gets booted by the boot loader and controls cpu and memory, sharing them between your administrative domain (Domain 0) and the virtual guest systems. . In order to boot a XEN system along with this package you also need a kernel specifically crafted to work as the Domain 0, mediating hardware access for XEN itself.
PackageMaintainerDebian Xen Team <pkg-xen-devel@lists.alioth.debian.org>
PackageNamexen-hypervisor-4.14-amd64
PackageSectionkernel
PackageVersion4.14.3-1
SHA-1388A8D3D086D4FA1A28A42270B235C78971CBAB2
SHA-256F2F932B34B7AC856F3811A8DA41572C0D57D47CEF6B48501CCFAFB49046B787E