Result for AA77C32B76BD1025D7E4CF17E8717FFB4E903F5F

Query result

Key Value
FileName./boot/xen-4.14-arm64.config
FileSize2229
MD577EC5C658E109489621A6F11C3EC3F1C
SHA-1AA77C32B76BD1025D7E4CF17E8717FFB4E903F5F
SHA-256A4483AD5A0DA29456C09D84E3699550C813F9F39BCDFF4BF832DB24DECC696CB
SSDEEP48:gi5fXpI+TH/HtxOJG19OGvtlwOTdPtzbqwz0dSdOaQh3:gi5fXpFj19BCj13
TLSHT1C441DDFB1F2BD82510D30E66973C329E229B16D96258EAA7EB48F70720EDC394513747
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
FileSize739100
MD598429443760D0C530AF2D9434FFF790F
PackageDescriptionXen Hypervisor on ARM64 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-arm64
PackageSectionkernel
PackageVersion4.14.3-1
SHA-195B8E2AFE5CB7418D51F18AB99ECC22075C7E9F7
SHA-2560C9F8BE64F9A8573731537632703532DD47E274ED83A03F882A7AB694E5AB2DD