Result for E0C5A4820118ADE48AB7DB6FAF59FAECB2BF3EA7

Query result

Key Value
FileName./usr/lib/erlang/lib/p1_pkix-1.0.0/ebin/pkix.beam
FileSize51736
MD5A303CC8E99FC52C7101E264EC68355E9
SHA-1E0C5A4820118ADE48AB7DB6FAF59FAECB2BF3EA7
SHA-256C22FBDFC70413CC32881C5CBE561BEC36C676CD97CF76FB9B689BA31D668FD3C
SSDEEP768:fgwNwxSnVyRqyovY9cgV3NR2j3U0OQKTKxPFxcFVCAiq5ruF6:fhwxS+HKVjfPr8VnI4
TLSHT1E933D05D07B40B92EFE34FB176DF5703BAA8E83025152B0715C1B57B64E4FA8A30A45B
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
FileSize164104
MD5C4018A38B49BEDF33C440E6A623F2E5E
PackageDescriptionPKIX certificates management library for Erlang The idea of the library is to simplify certificates configuration in Erlang programs. Typically an Erlang program which needs certificates (for HTTPS/ MQTT/XMPP/etc) provides a bunch of options such as certfile, chainfile, privkey, etc. The situation becomes even more complicated when a server supports so called virtual domains because a program is typically required to match a virtual domain with its certificate. If a user has plenty of virtual domains it's quickly becoming a nightmare for them to configure all this. The complexity also leads to errors: a single configuration mistake and a program generates obscure log messages, unreadable Erlang tracebacks or, even worse, just silently ignores the errors. Fortunately, the large part of certificates configuration can be automated, reducing a user configuration to something as simple as: . certfiles: - /etc/letsencrypt/live/*/*.pem . The purpose of this library is to do this dirty job under the hood.
PackageMaintainerEjabberd Packaging Team <ejabberd@packages.debian.org>
PackageNameerlang-p1-pkix
PackageSectionlibs
PackageVersion1.0.0-3+deb10u1
SHA-17806B54F2AFA45BEC063A096AACE8795EDBD744F
SHA-256C5CFCA2DFDAA8F6CCADE36A5513F799AFAEF071FB3F2831FCF0DAA8ECBBED39F