Parents (Total: 10)

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

Key	Value
MD5	5034311CDC0E6486CA61A6FD247E592A
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	bp150.8.1
PackageVersion	1.0.8
SHA-1	889F5DD7A81E21F8E9E77AFF9BF60FDAA2C5A53B
SHA-256	175E7DA350FC33E0CF625BDFCE94422C487C6204EE740B62D2421DBE0FC6A742

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	7BCCFDCE6AE3BDAC1E4D479DA9865D60
PackageArch	i586
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	68BE157D76710F641F7D421B03462D41E437E7AC
SHA-256	2275ACAC1216AE4EB768A39A5D0FA6972831D21153B563D2C08CCE2A7083CF82

Key	Value
MD5	7E38CE27C83B62539B45E104445EF565
PackageArch	i586
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	B635CA6A236B2622A706A099BB068F5E93F458D5
SHA-256	3CC950FB758398E065088EF097185E623F33C3B5CF75563120B616A9A23B2EDC

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

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

Key	Value
MD5	0018F49D8F1FD935747F5EECB57DB91C
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	lp152.8.1
PackageVersion	1.0.8
SHA-1	02CD8E0D8A76C754B1818063B317D3A7F569199B
SHA-256	ADAFAAF7F376045F46E8F64485B8A569332EBB9219F72DCBDE598260A24CC87F

Key	Value
MD5	8AC841ADD778D80AD06A909B73308422
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	lp151.8.1
PackageVersion	1.0.8
SHA-1	C154F9B1DC4BC6B91AF16BB3E9A43974DD5DD96A
SHA-256	3191B9191C6D08251480C1986E486F9BB89C19D70EF6F2FFD623C77C81534422

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	EAB2BF95CBF707D09D1A5C738C624399
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	9FF00DF2C5F6B19788EE22F161B7AF3D4229763D
SHA-256	F55FD75E2B540E91C54DA13761B74C7B4CD91AEE468E1C9460386A3BE363010E