Result for 0AB9234DBB8AE01553981E7598C6B2B0C3E1EDEC

Query result

Key Value
FileName./usr/lib/arm-linux-gnueabihf/knot-resolver/ahocorasick.so
FileSize17828
MD5611C917F320461382FB88F5A3E2C1CB2
SHA-10AB9234DBB8AE01553981E7598C6B2B0C3E1EDEC
SHA-2562E73DE6D5C4DEBE59D89E53F5E87B17802FEE50E2569ED83903BB993660D5282
SSDEEP192:bYPD8Hkfn58J/JjzFGo292Gm2y6Wbo+qp9tjxtJ/7PBe0kBnVEorB99w:bYPSoexPFGR2Gm2PD+e7jxzwV1i
TLSHT140825C84F7823E33CD858574E0878F961621C006938F47A3262CB9AA7FD2B647E57F65
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
FileSize265240
MD54384330B59CE2DCE0A104A4ED70BA512
PackageDescriptioncaching, DNSSEC-validating DNS resolver The Knot Resolver is a caching full resolver implementation written in C and LuaJIT, including both a resolver library and a daemon. Modular architecture of the library keeps the core tiny and efficient, and provides a state-machine like API for extensions. There are three built-in modules - iterator, cache, validator, and many external. . The Lua modules, switchable and shareable cache, and fast FFI bindings makes it great to tap into resolution process, or be used for your recursive DNS service. It's the OpenResty of DNS. . The server adopts a different scaling strategy than the rest of the DNS recursors - no threading, shared-nothing architecture (except MVCC cache that may be shared). You can start and stop additional nodes depending on the contention without downtime.
PackageMaintainerknot-resolver packagers <knot-resolver@packages.debian.org>
PackageNameknot-resolver
PackageSectionnet
PackageVersion5.3.1-1
SHA-1676F6821CD638E876FE7BA2C37FFCE1C4C9AD43A
SHA-25688BC5517FF9E7729D6C6605D1EC100BD21635C6B76F4FE770F5C30A50743A1A8