Result for 5A5BB640F6892EDFB166199CAAA59B2810068BF4

Query result

Key Value
FileName./usr/lib/erlang/lib/p1_pkix-1.0.0/ebin/pkix_sup.beam
FileSize1564
MD5EC1A81A5680E27340BE8E5783BB1EF6B
SHA-15A5BB640F6892EDFB166199CAAA59B2810068BF4
SHA-256383433285192ABDB87EBD9BD0D76B03649B21EB1D3C9C63E23877D2B4876A0CD
SSDEEP24:hMo2Y4xbkBX4s4yvX9/ZHCt2w/bWju5jG/BMkv58HfKHSStYb0Nru7fmZyft0:hMBNCXPP9zaocfKSKYbmOa
TLSHT10B31F7325E949683C06F023252269B39E2B8ABCC476CFD060BAC9E8BD2606F14044504
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
FileSize163696
MD588ACCDCE6CA9F6A3A6852251460ADBD1
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-1F37875F73449B9CCFC001AA74A40DC981F0B3EAA
SHA-256A0F8CF956572374C62ED68A97685BD1D8AE43DE2DFDB2D8C6CE3FFA24C02C8CD