Result for EA0A90E2A7AF6844C0008F184553F68206D10889

Query result

Key Value
FileName./boot/xen-4.11-amd64.efi
FileSize2687456
MD56CB5D91AE30600226B188313A349DBEC
SHA-1EA0A90E2A7AF6844C0008F184553F68206D10889
SHA-256FF91AC21DC956B5966893C890388FD66D6D05A47CF7441B27E793BF0D71783CB
SSDEEP49152:JTHdAaWy6/SRBzFHQtohT3NcqLyMcjrPwsOet+UdSi3/O1gk3mrPumlcH:ddDuYBzFHQtohT3NcqLyMcjrPQ+SivOb
TLSHT161C57D0BB9E364BDC593C13447BB967279327C2153317FBB5184EB322E62E906B1AB11
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
FileSize15110692
MD56A4C3823CE535A3AFC92CA8B6F4B0C50
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.11-amd64
PackageSectionkernel
PackageVersion4.11.4+107-gef32c7afa2-1
SHA-1166B616D983CF4D5B4DE00EEAB7789F279F8EB0F
SHA-25638475F11A5DC0FDB22953D211F22F1C63CCA7BB52D926D8EFB728F17ECC801D0