Result for 20C79D88BA223622EB46E4D5852A088FFE80888D

Query result

Key Value
FileName./usr/share/doc/erlang-p1-pkix/changelog.Debian.ppc64el.gz
FileSize226
MD51ECB65E8C9274FA8979E32C1E22FCA1C
SHA-120C79D88BA223622EB46E4D5852A088FFE80888D
SHA-25693F703BA98237FCF8C7898BB2B86443751425ADB40B017D4A131365C0B90C979
SSDEEP6:XtTD2kebPIcf9mxsTjEOHwoIM5lCgLs1gKA8JlNOBll:XtDck9Wjsu2ydKAclNOTl
TLSHT1E8D0971400A1324AE20A19B53A0B28886C18230D08BBBA8102589E68A49C2234848984
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
FileSize177168
MD563E594CBAFF331507398E3CF2D1631D8
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-10891EACF0E276F875D66E70D08FB437A1232FC91
SHA-256352C1E72375F997F1FE58DE5917F8353B32A5903B0B4D036FCC99734B2CED977