Result for 326941AE6AA30D043178C1F9C92F0A95B587756D

Query result

Key Value
FileName./usr/lib/erlang/lib/p1_pkix-1.0.0/ebin/pkix_sup.beam
FileSize1564
MD5B3228170E80EC5509CDB6FDC4E21A59D
SHA-1326941AE6AA30D043178C1F9C92F0A95B587756D
SHA-25636945F241FDE1BF023C225E58ABD54B8E3695980AEB536626ECCC730D674EACC
SSDEEP24:hMo2Y4xbkBX4s4yvX9/ZHCt2w/bWju5jG/BMkg458HfKHSStYb0Nru7fmZyft0:hMBNCXPP9zaGcfKSKYbmOa
TLSHT1EF3119325EA46683C06F02325226AB3DE3B8AFCC47ACFD060BBC9E8BD2507F04044504
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
FileSize163692
MD555AA6789D5080E007E4EDF351020ADFF
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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNameerlang-p1-pkix
PackageSectionlibs
PackageVersion1.0.0-3
SHA-1630259DB5B34C393025AF54A9DA69125BF56AEE9
SHA-256E0888AB5D8A6EDC04532BFFC2946ECEC7792F709FA7C4CE0830E635358312E96