Result for 3FBE7221B7B5EA863381CBA174DEB141BAACC46A

Query result

Key Value
FileName./usr/lib/erlang/lib/p1_pkix-1.0.0/ebin/pkix.beam
FileSize51736
MD56BF196C490A6EF672FFF29E0C607D6B0
SHA-13FBE7221B7B5EA863381CBA174DEB141BAACC46A
SHA-256E1D0862EBF8960B3B7A1CB62882830591C9F467B91E176FFA12D94DBBCEC9F5F
SSDEEP768:fgwNwxSnVyRqyovY9cgV3NRhj3U0OQKTKxPFxcFVCAiq5ruF6:fhwxS+HFVjfPr8VnI4
TLSHT1AA33D05D07B40B92EFE34FB176DF5703BAA8E83025152B0715C1B57B64E4FA8A30A45B
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
FileSize164108
MD58B6D79E0A12A2D85C200ADE2C47F164D
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-1E9252931A31235EFB3FA0451A801B66DDB81EA67
SHA-2565E516F69FEDF27EC5AF8DB113C4B0A8BF5D43AC52A5717F1B76647F7AE14FF8D