Result for 4DDADC783FC1B84A388D3021E7D2FE6456BE8070

Query result

Key Value
FileName./usr/lib/erlang/lib/p1_pkix-1.0.0/ebin/pkix_sup.beam
FileSize1564
MD5554DEC496D0374D4A5DDA84B84963967
SHA-14DDADC783FC1B84A388D3021E7D2FE6456BE8070
SHA-25661EF454B3977FFC3822DD8C5C18F0972436B6831974191C126AC15F49C9D74E0
SSDEEP24:hMo2Y4xbkBX4s4yvX9/ZHCt2w/bWju5jG/BMk958HfKHSStYb0Nru7fmZyft0:hMBNCXPP9zaicfKSKYbmOa
TLSHT1103119325FA46693C06F023252269B3DE3B8AFCC476CFD060BBC9E8BD2507F04004504
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
FileSize163676
MD5BB2CE7BA3A7CA76730F013023C2D93AD
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-15C768562B89DFC2F226634540BAB74E5CE005B9C
SHA-2562DDFB54DDB7806ACEDFD0DF4C81263E905B99472CCC9EBDA9DC1AB39A5A90FC7