Result for EF41B7A40CA0C5021B926005235764B0EB8837F7

Query result

Key Value
FileName./usr/share/doc/erlang-p1-pkix/changelog.Debian.arm64.gz
FileSize223
MD59F028949BA0A28C8420CD5D2659CFF7C
SHA-1EF41B7A40CA0C5021B926005235764B0EB8837F7
SHA-256BBC692B7DA32F2842E488EDA8922DE11635374F3A3E93C029CC42EF57F7C05D0
SSDEEP6:XtjD3hN5cVzznfN4f0Q19oI9Jfr/bOMfIePV/t862Z9:X9D2F1vIrzTOeIePs
TLSHT1C1D097322A968081816A6F74839A548230898700869C0AA200E41827BD01F30239F6E0
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
FileSize177132
MD588E43CD3DF01ACD0DC219D5900DBEC6A
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.10-2+b1
SHA-14A74915B854299BCB2ED06856F070519ED36ECF1
SHA-25627AADD826BF51DCC68A7591A12A192923EE93EE64AAE80D6C8E30D9ADCB5BD0F