Result for 14EC5C48DB7EDE37B6E54F374697CB5C05B86FD2

Query result

Key Value
FileName./usr/lib64/erlang/lib/pkix-1.0.8/ebin/pkix_sup.beam
FileSize1512
MD5407973202E26A650F9CEDFFE5D372BBF
SHA-114EC5C48DB7EDE37B6E54F374697CB5C05B86FD2
SHA-256EF49A9F5ACEADB1D4CFC852DCFF077CBFDB5CB665E85E6AA777925E4E8668FC3
SSDEEP24:h9o2Y4xbkBX4s4y/n9/ZHCt2w/bWju8iz/LEDI0jUPvlZlBQGeMV6DlafmuIEf6d:h9BNCXPP9zRiU/yjbnwo+uIEf6NBR
TLSHT19331E9201FA54BC3C0C941B861124B1BDD3172DE0FB88D4917646DCBE681EFD648CBCA
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