Result for 19FC160536C9950D14EAB79CF82B4DECD63B9B2C

Query result

Key Value
FileName./usr/sbin/kres-cache-gc
FileSize26092
MD5F2013A8EA842347AE32AE3EBFDA276AE
SHA-119FC160536C9950D14EAB79CF82B4DECD63B9B2C
SHA-256484BFC4DE1EA4305082939032E8D882CC59F27E171C2A9D74E2FF317D6B743AE
SSDEEP384:GHNggTjNeWzhxXVp+slY2CHhiQP1OlDEeMu3e9M+7Wh7:+fTRvhxX1W2CHhNPslD3Mu3e9M+7Wh7
TLSHT103C2F85BBA90E433F26182B124C783699421AC769713C953FB843FEC7471996EE0637E
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
FileSize324288
MD59EA43B4DE0EB2E12C90E255408D19694
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.4.2-1
SHA-1BC20765DC6FF6FCA65A0BAD6CDF74C001A478186
SHA-256EF399D6B7AE5AAF816CBA92F3C1AB2E580710A739E5DFA0099F142B1CE8FBBC1