Result for 3A51EF0B51C60C0F185C19EECAA415559853C546

Query result

Key Value
FileName./boot/xen-4.14-amd64.efi
FileSize2763757
MD5AD277162FC0F83C361718F0F4C17D1BE
SHA-13A51EF0B51C60C0F185C19EECAA415559853C546
SHA-256D67562F54281ABDA3AC37E224C6B243A3A4BC9CEC8FDAB443682F428D270AA9C
SSDEEP49152:CyFlbB4GGcaYQPVE8ntYifYZ/OFkLiLDqHbOj90GAre3bcKmJD7U7Gju5EIa0NAI:LFlbmGGrYQdEA2d/OmiLD6bOj90GAreZ
TLSHT130D56C57B9E368ADC592D13457B7C7727932BC3212213FAB50D4EF322E22E81175AB12
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
FileSize3480384
MD58AC42EEF96AAD4DE1F9F32AA2A63E41A
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~deb11u1
SHA-17CFE4DA88FA39497E8764813E80437562D45DE9D
SHA-25684C34E017C6FE7A4D088B63F9D15191BA20900710637B33234A1A89FDEB2A076