Parents (Total: 2)

The searched file hash is included in 2 parent files which include package known and seen by metalookup. A sample is included below:

Key	Value
MD5	953185AC07D442095791DFDA7C6C5B21
PackageArch	x86_64
PackageDescription	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 (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.
PackageName	erlang-pkix
PackageRelease	8.2
PackageVersion	1.0.8
SHA-1	685C9306BBFB2BDE28DAA9D58801786A349F9D3C
SHA-256	D75EC8197ADD94B94A2A1BA9DD267D4B21794688B2BADE27D0C9C69531CB4B36

Key	Value
MD5	C7D3146B2D4165EA223C5977B337AADC
PackageArch	x86_64
PackageDescription	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 (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.
PackageName	erlang-pkix
PackageRelease	8.2
PackageVersion	1.0.8
SHA-1	077E440C2C080B70D0592E08E7737E353E671760
SHA-256	F3FFFC86EA8D815DE9758F4FC64C4B681BA229CE5D7161576C8E572B9FB748E8