Key | Value |
---|---|
FileName | ./usr/share/doc/erlang-p1-pkix/README.md |
FileSize | 2862 |
MD5 | 702A3DB47637DD834E086A6894D0FBB6 |
SHA-1 | D89ABC2C1814E0F969AC9325104C999C805C4240 |
SHA-256 | 77B05FC6BED2E7134C70B0CB24EA121DE7C99236AE79A870FC0260FE88E70335 |
SSDEEP | 48:uLfh5p2VZdHALjgv2C+FFv+4stgmBBOzvG+Q+8MlEFGeYun1qea:8h5Mh+C+/v+3B5xMCFYun1c |
TLSH | T1F55178ABEF8C3D3159E217F6260E71D0EE18C1AB87551809095E40673315FB1A27F578 |
hashlookup:parent-total | 35 |
hashlookup:trust | 100 |
The searched file hash is included in 35 parent files which include package known and seen by metalookup. A sample is included below:
Key | Value |
---|---|
FileSize | 162514 |
MD5 | E16BC2A79B06644AC044ED383AC9EB29 |
PackageDescription | PKIX certificates management library for Erlang 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 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: . certfiles: - /etc/letsencrypt/live/*/*.pem . The purpose of this library is to do this dirty job under the hood. |
PackageMaintainer | Ejabberd Packaging Team <ejabberd@packages.debian.org> |
PackageName | erlang-p1-pkix |
PackageSection | libs |
PackageVersion | 1.0.0-3~bpo9+1 |
SHA-1 | 09C0EBB81676F1C2891D9B58A8FA0A3AAD7A37B8 |
SHA-256 | EC1BF2687A0E35D02D2CCE690FC65CE8FDB58B6D38CCD58E754F3C37BE69FB11 |
Key | Value |
---|---|
FileSize | 164092 |
MD5 | 5AA88B67B4BF6C26C057EA099657AA33 |
PackageDescription | PKIX certificates management library for Erlang 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 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: . certfiles: - /etc/letsencrypt/live/*/*.pem . The purpose of this library is to do this dirty job under the hood. |
PackageMaintainer | Ejabberd Packaging Team <ejabberd@packages.debian.org> |
PackageName | erlang-p1-pkix |
PackageSection | libs |
PackageVersion | 1.0.0-3+deb10u1 |
SHA-1 | 13D65A88912ED0496A1520A259D249164128073F |
SHA-256 | 8870AED7ABCB198F9D59558B64FE6B6EDB4A38016FE5693F21F044011B2FC017 |
Key | Value |
---|---|
FileSize | 163692 |
MD5 | D99C4186CDC50C220711A9A7771AEC3C |
PackageDescription | PKIX certificates management library for Erlang 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 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: . certfiles: - /etc/letsencrypt/live/*/*.pem . The purpose of this library is to do this dirty job under the hood. |
PackageMaintainer | Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> |
PackageName | erlang-p1-pkix |
PackageSection | libs |
PackageVersion | 1.0.0-3 |
SHA-1 | 14C60CB4A0F67B7C88C82AB50C9377AD8E9B60A5 |
SHA-256 | 7381B41D7BDEF80D5AC4D6054418A95DAC2998E4605891711020F35D2E6A66E7 |
Key | Value |
---|---|
MD5 | 8598D8DCC7B361EBC49CD1856677B62C |
PackageArch | noarch |
PackageDescription | A library for managing TLS certificates in Erlang. |
PackageMaintainer | Fedora Project |
PackageName | erlang-pkix |
PackageRelease | 2.fc32 |
PackageVersion | 1.0.4 |
SHA-1 | 19232F1ABD8A2B310F125CE15D5C3E10E80ACFA1 |
SHA-256 | C3370398690201F57D8661A351FB14EEE63FA0E0E55525360ABF147CAA2F7501 |
Key | Value |
---|---|
FileSize | 164112 |
MD5 | 7B8AB134A70245A9E4F61F23EA7598E8 |
PackageDescription | PKIX certificates management library for Erlang 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 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: . certfiles: - /etc/letsencrypt/live/*/*.pem . The purpose of this library is to do this dirty job under the hood. |
PackageMaintainer | Ejabberd Packaging Team <ejabberd@packages.debian.org> |
PackageName | erlang-p1-pkix |
PackageSection | libs |
PackageVersion | 1.0.0-3+deb10u1 |
SHA-1 | 1C82192DA36321B2300736AB07599D7A0FAAED5A |
SHA-256 | 1295057D46146F5BD4409B5094858BA7D6047D813585DD8CB1999659A46DCF50 |
Key | Value |
---|---|
FileSize | 162498 |
MD5 | 9CE7183E049E18D14EFF0322685ECEB5 |
PackageDescription | PKIX certificates management library for Erlang 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 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: . certfiles: - /etc/letsencrypt/live/*/*.pem . The purpose of this library is to do this dirty job under the hood. |
PackageMaintainer | Ejabberd Packaging Team <ejabberd@packages.debian.org> |
PackageName | erlang-p1-pkix |
PackageSection | libs |
PackageVersion | 1.0.0-3~bpo9+1 |
SHA-1 | 224CF6579E22FB426ECB13D1464CDA77023C2494 |
SHA-256 | 6094D97CAF15438D828DDAD767676F01A11EE9E4693BF084A0E7EA1E328BF071 |
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 |
---|---|
FileSize | 162496 |
MD5 | B08B3659FDAC7CE45968BBC05B059AD2 |
PackageDescription | PKIX certificates management library for Erlang 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 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: . certfiles: - /etc/letsencrypt/live/*/*.pem . The purpose of this library is to do this dirty job under the hood. |
PackageMaintainer | Ejabberd Packaging Team <ejabberd@packages.debian.org> |
PackageName | erlang-p1-pkix |
PackageSection | libs |
PackageVersion | 1.0.0-3~bpo9+1 |
SHA-1 | 3A6FACD8D2E2D971E3D074154FFD851B1194DAFC |
SHA-256 | 1F9C9472D4CF1E4F48C17FBD16436E1C57787E3CFB6CBA9A9C21C853CF0108F4 |
Key | Value |
---|---|
FileSize | 164064 |
MD5 | 3A2C8B7A1D471510CEE9DDF199CE1806 |
PackageDescription | PKIX certificates management library for Erlang 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 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: . certfiles: - /etc/letsencrypt/live/*/*.pem . The purpose of this library is to do this dirty job under the hood. |
PackageMaintainer | Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> |
PackageName | erlang-p1-pkix |
PackageSection | libs |
PackageVersion | 1.0.3-1 |
SHA-1 | 3ED1F2C6928CE12D925D89216DAA68AF5A600149 |
SHA-256 | 2A4B5E9C121C99C6BA4CA165E208E80A5F2CBD73B3FA81AEF917772DF2AA850A |
Key | Value |
---|---|
FileSize | 164108 |
MD5 | 21D01620AF43B91CBD09DC7CCA58A5EA |
PackageDescription | PKIX certificates management library for Erlang 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 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: . certfiles: - /etc/letsencrypt/live/*/*.pem . The purpose of this library is to do this dirty job under the hood. |
PackageMaintainer | Ejabberd Packaging Team <ejabberd@packages.debian.org> |
PackageName | erlang-p1-pkix |
PackageSection | libs |
PackageVersion | 1.0.0-3+deb10u1 |
SHA-1 | 42B987FADCCE0D4AE56EE14FB39A7280705C1E9B |
SHA-256 | E0FDD6C4FFF58B6A78961E4E3FE72676B2B72A31A5D96ABDFCB83E233D8886E9 |