Result for 06CB12A3171E1F92FBD3AA703828EEECC8371918

Query result

Key Value
FileName./usr/share/erlang/lib/pkix-1.0.8/ebin/pkix.app
FileSize546
MD5C127A6A1CB7A67DB1396F12FBD048E93
SHA-106CB12A3171E1F92FBD3AA703828EEECC8371918
SHA-256670D2D76B267EA596220DCA5AD337735157786BB91723FC7AEF8EE8FDD5CBE48
SSDEEP12:Ietkb5AetQo77uXiEH/3GYiAtRvrlyxKY:jqbaeBOH/2YJRvrkF
TLSHT171F0E5AB8DD454012F861D9EBBB9A1060CBB25CB4DD8A8A433AE014A1F9C54F54B9631
hashlookup:parent-total47
hashlookup:trust100

Network graph view

Parents (Total: 47)

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

Key Value
FileSize176516
MD5BE0CE9F15F99DB11E2F7AE33965F0C03
PackageDescriptionPKIX 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.
PackageMaintainerEjabberd Packaging Team <ejabberd@packages.debian.org>
PackageNameerlang-p1-pkix
PackageSectionlibs
PackageVersion1.0.8-1~bpo11+1
SHA-101801573E01064A95DE14A7308C113763213C9D5
SHA-2567D8B78177FD3E078BD3B6BB20E0E77044758C562B858965600A0A6FEA71D116E
Key Value
MD50018F49D8F1FD935747F5EECB57DB91C
PackageArchx86_64
PackageDescriptionThe 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.
PackageNameerlang-pkix
PackageReleaselp152.8.1
PackageVersion1.0.8
SHA-102CD8E0D8A76C754B1818063B317D3A7F569199B
SHA-256ADAFAAF7F376045F46E8F64485B8A569332EBB9219F72DCBDE598260A24CC87F
Key Value
FileSize176516
MD5E8E4EAB8FED11AAF6E51E44AC51EBC51
PackageDescriptionPKIX 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.
PackageMaintainerEjabberd Packaging Team <ejabberd@packages.debian.org>
PackageNameerlang-p1-pkix
PackageSectionlibs
PackageVersion1.0.8-1~bpo11+1
SHA-103E301B50ACEF3A8AAA28F1FA7B4A79F0B6AF402
SHA-2565503603FA23E17E241A3D54D5DF5BBE079F7BFA02ED0DE71AE0D57CF5560DB2E
Key Value
MD5C7D3146B2D4165EA223C5977B337AADC
PackageArchx86_64
PackageDescriptionThe 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.
PackageNameerlang-pkix
PackageRelease8.2
PackageVersion1.0.8
SHA-1077E440C2C080B70D0592E08E7737E353E671760
SHA-256F3FFFC86EA8D815DE9758F4FC64C4B681BA229CE5D7161576C8E572B9FB748E8
Key Value
FileSize176512
MD534E26746EE0779B7AA040267B1461539
PackageDescriptionPKIX 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.
PackageMaintainerEjabberd Packaging Team <ejabberd@packages.debian.org>
PackageNameerlang-p1-pkix
PackageSectionlibs
PackageVersion1.0.8-1~bpo11+1
SHA-110811C4B67F29CB82E1C3EAD7FF5994A767995A5
SHA-256445F35077A11A5A810B27B5E476581CA01B5DC75969DC7C3DA621822533D8092
Key Value
FileSize176516
MD5632BAFC7C105E37DF3DA60A51E450CA1
PackageDescriptionPKIX 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.
PackageMaintainerEjabberd Packaging Team <ejabberd@packages.debian.org>
PackageNameerlang-p1-pkix
PackageSectionlibs
PackageVersion1.0.8-1~bpo11+1
SHA-12162D3F11726D7BE528941F4FF6299BD404738F3
SHA-25648EE595640BB0DA058ECFDBA0F3074F1E08CE49A73FA6883326C12B3DE7E2106
Key Value
FileSize176588
MD58575E8BF3512A7778F7F1B47E222AA3F
PackageDescriptionPKIX 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.
PackageMaintainerEjabberd Packaging Team <ejabberd@packages.debian.org>
PackageNameerlang-p1-pkix
PackageSectionlibs
PackageVersion1.0.8-2~bpo11+1
SHA-123A0ACE3378D227948AEE4D2D7D2B2FBEF8CB0C6
SHA-256B83DF384CCD9A9B7CB8B737EBFDC06513FBDA2DE64B54FBC168B2334C0538806
Key Value
FileSize184752
MD56630F6BA2DDF868E0277C7B657CC64BD
PackageDescriptionPKIX 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.
PackageMaintainerEjabberd Packaging Team <ejabberd@packages.debian.org>
PackageNameerlang-p1-pkix
PackageSectionlibs
PackageVersion1.0.8-1
SHA-12BBE782C70C7458D957D63A475D4F32CD156FA06
SHA-256B98786EF2354882A7047B8E469B143126F690B2189A3528D4D3441FD0197DE80
Key Value
FileSize176588
MD5A0D1739559326FF392A2ECB0D4B0A47A
PackageDescriptionPKIX 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.
PackageMaintainerEjabberd Packaging Team <ejabberd@packages.debian.org>
PackageNameerlang-p1-pkix
PackageSectionlibs
PackageVersion1.0.8-2~bpo11+1
SHA-12ED9CE6D6C2601470B10C255655DDBC0DD553E39
SHA-25674A8B13EC8C527BC6469335909B512C963A0EA9B57011EAC443BF7DD13D109FF
Key Value
FileSize185156
MD5CBBEDA307692509FD7F2CA11300DD89D
PackageDescriptionPKIX 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.
PackageMaintainerEjabberd Packaging Team <ejabberd@packages.debian.org>
PackageNameerlang-p1-pkix
PackageSectionlibs
PackageVersion1.0.8-2
SHA-137FD872CACD503F5E26A0239792C80D60BC8EE1E
SHA-2566B538170E9374E9F31D29481B9B3BECE3E002D8F6E061830C9E6D4761BF1FC1D