Result for 75EE5B56DA679EDD7C3AD4B88C9CD5D9C9EB3EC3

Query result

Key Value
FileName./usr/lib64/erlang/lib/pkix-1.0.8/ebin/pkix.beam
FileSize58516
MD57985A13B9F13F26E4B5EDD368EF7E837
SHA-175EE5B56DA679EDD7C3AD4B88C9CD5D9C9EB3EC3
SHA-25690777B561C9EB493255FB5FAA2E88FF54AD1A75F8C616B6F52ADD5104B1717C0
SSDEEP1536:CHUGz3WhmkIHMHcnPC31KXgMPRJ7s9kPX3jF5:0UvmkH8n41KQMfAgHZ5
TLSHT14243C0980BB44F20EEA35FB5259E534317E1D8B183A03A036081FBBFB6E4F2C6459579
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
MD55034311CDC0E6486CA61A6FD247E592A
PackageArchx86_64
PackageDescriptionThe 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 (stored somewhere in `/etc/letsencrypt/live/*/*.pem`) 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: ```yaml certfiles: - /etc/letsencrypt/live/*/*.pem ``` The purpose of the library is to do this dirty job under the hood.
PackageNameerlang-pkix
PackageReleasebp150.8.1
PackageVersion1.0.8
SHA-1889F5DD7A81E21F8E9E77AFF9BF60FDAA2C5A53B
SHA-256175E7DA350FC33E0CF625BDFCE94422C487C6204EE740B62D2421DBE0FC6A742