Result for C6BD5A8CA5ACAC89F3C703FAE0A96A49FE3F21E3

Query result

Key Value
FileName./usr/lib/erlang/lib/p1_pkix-1.0.0/ebin/pkix.beam
FileSize51736
MD59428B3388C46B07590BE0E5D7E2CDDB6
SHA-1C6BD5A8CA5ACAC89F3C703FAE0A96A49FE3F21E3
SHA-2567EB927C6F76BEB0CDD869B1955226AFFF598070D81D0220A4836004BE7AE04AB
SSDEEP768:fgwNwxSnVyRqyovY9cgV3NRyj3U0OQKTKxPFxcFVCAiq5ruF6:fhwxS+HWVjfPr8VnI4
TLSHT18133D05D07B40B92EFE34FB176DF5703BAA8E83025152B0715C1B57B64E4FA8A30A45B
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
MD582F8B4CAA1ADBEEC2D4EF843AEB243FE
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-19323E1EE52F44B8430765958F5C9DA4B58F615A6
SHA-256D2D165288C716D79D6084F8AA10BBC855ED39A6148C5CEACD2B0E7D13D8E2268