Result for D0565BF5A51DB29FB5504B2C354C5C66C97A3AC7

Query result

Key Value
FileName./usr/share/doc/erlang-p1-pkix/changelog.Debian.amd64.gz
FileSize232
MD5D18CFF8DE6DE2B7A851F26479BA7D0A6
SHA-1D0565BF5A51DB29FB5504B2C354C5C66C97A3AC7
SHA-256BE1FD16C293525948FB28A0636E6428E0E31F6A1E3B9287E028F13E9DA83880A
SSDEEP6:XtHJL6/LhTS2UAXfOQFANpUe+FXz/yHxW7yi:XVJLWLFS2PX6b4Xz6Hkj
TLSHT10CD097FB07B5099991C247F382034C92C849816BA8EC25B80060604A3BBD3C02188195
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
FileSize177176
MD54D72DFD11CB5A2A8D96260FA558CBBA4
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-10323E06921ABD62898B22C5CC7DCEB5BB8012C4D
SHA-2568E9FF4B1CA0258E4BB9C381D8544F883826F97D4B954158D257EB443CAD84CCD