Result for 77FD362B8B9DF3A8CBBA6FD2124C69C08E02DEF2

Query result

Key Value
FileName./boot/xen-4.11-armhf.config
FileSize1274
MD51B21951030BF45CB253C019810F6BAF7
SHA-177FD362B8B9DF3A8CBBA6FD2124C69C08E02DEF2
SHA-256FA84FAA6530CFA5EA69E85B058C9A76F91246410B142EEDDE1320CA8BBA9C884
SSDEEP24:fvz0Bsms+IVH/arWxRMe46uW4ui2/+IPqg4AqgPIbQqwr31bcdSnsZpU4Ma:gBu+WH/uoGF9uJ/+IPtzIbQqwz9cdSng
TLSHT1F22179FB2F2AE86920930565973C725F265711EC6240EF3BEA05E90B20DDC378053713
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
FileSize3285924
MD5EC66FD6B84DD3D6348F0412557E4F464
PackageDescriptionXen Hypervisor on ARMHF 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-armhf
PackageSectionkernel
PackageVersion4.11.4+107-gef32c7afa2-1
SHA-1F58CB53F94D49DC08B298C3331073883E7CF98D6
SHA-25618FCCADBD34FB3DD844D5665D1028997D66BF9CABEC5C292C0F33A17712C51ED