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	6785D0E4FD676C00C5E59649F3F49589
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.1
PackageVersion	1.0.8
SHA-1	FFCE3C6572D86C95C840EDF75836A4AF78853E8F
SHA-256	6863A0EF555187EF4C10B79CADADC3FF08BE45B60F2E0EDC6CFBA98A188EF4A6

Key	Value
MD5	C385DD1B6687F31BAA49A830E73539AE
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	lp153.8.1
PackageVersion	1.0.8
SHA-1	8E040D08CF59A9245BA5E3B03ED50AADD246226B
SHA-256	7E564945BF9CAB2E951B0B5276C3E65C4911667EE55F08D01DFB39835C37A98C