Parents (Total: 22)

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

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	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	9707CF4C4BE8A7FEC102811A717CAFA0
PackageArch	i586
PackageDescription	P1 Utility modules from ProcessOne for ejabberd
PackageName	erlang-p1_utils
PackageRelease	10.1
PackageVersion	1.0.24
SHA-1	14D3BD3A3032EDD4922288B1D2AF55DFF88B9F64
SHA-256	C13C2AC30134352A59A22F5C8427B3517EFA33FC6F82D2B143FBFE82B305D553

Key	Value
MD5	2A329C5562DCC678BDE5C734B6D92070
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	lp150.4.1
PackageVersion	1.0.4
SHA-1	23A5B895D89CDA3C0508F7535C8F7D89CCF45669
SHA-256	DCCD5C9B9842E5B6E307A24E22B4175305A8A4948DF4214F4706D1625CBBF30F

Key	Value
MD5	A81B577F89CF4945DD2D6BE2A8B1D978
PackageArch	x86_64
PackageDescription	P1 Utility modules from ProcessOne for ejabberd
PackageName	erlang-p1_utils
PackageRelease	bp150.10.1
PackageVersion	1.0.24
SHA-1	2D0776878D024CF465B4D4809C7C1A39ED3F45D0
SHA-256	D88BCB58B0EF527FEC41465E43B3B30040260A91C8954E370D8BA107D4716399

Key	Value
MD5	80B66B45F590682F5E2E873D749C8216
PackageArch	x86_64
PackageDescription	P1 Utility modules from ProcessOne for ejabberd
PackageName	erlang-p1_utils
PackageRelease	10.1
PackageVersion	1.0.24
SHA-1	38A2CA17014A78AFD8178F8B887B815F781276E2
SHA-256	ECCE3310316701FF717DB764A7BFF8C5B7A6FF4E17B604D2FFD8CA04CE3FD8DA

Key	Value
MD5	4FEDBBB27947B00EDA45AAA25713409A
PackageArch	x86_64
PackageDescription	P1 Utility modules from ProcessOne for ejabberd
PackageName	erlang-p1_utils
PackageRelease	10.1
PackageVersion	1.0.24
SHA-1	489EDE86DDC3D808B67BC68D89B564EA3B9EB4EB
SHA-256	635C0BEFDDDB832DE4290E4EF3E24B3E07A74A0659E9E13C52BAC4724C85BE04

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	584C3F444C13050B6F074F630CF0A83E
PackageArch	x86_64
PackageDescription	P1 Utility modules from ProcessOne for ejabberd
PackageName	erlang-p1_utils
PackageRelease	lp151.10.1
PackageVersion	1.0.24
SHA-1	6ADA306A2C835B55E3CBFBEF62C253E7E17FA1B5
SHA-256	5A89F5F2220D0E382B7311147B25CD8D0C474E3BA16C4AA76158AEE79CD3922A