Result for 59B221DA876908D401EE46F65C87B5A4FD8872C1

Query result

Key Value
FileName./usr/lib/erlang/lib/p1_pkix-1.0.8/ebin/pkix.beam
FileSize65988
MD5776543BBFC9CB8F9B603D2665B039A08
SHA-159B221DA876908D401EE46F65C87B5A4FD8872C1
SHA-256EA75F24B798BA67EC32E8775F0A68F816C332CB3C468F9BADBD4351B5FA0BB89
SSDEEP1536:DHsCys7tzveqnRpC7U3Kfgvh4WmUN3BvgSX:RzFC7QKauWjdBn
TLSHT10C53D0B81F741F11F2DB3FB5BBBEAB0A7771DD2297252E0B0060B46868D4F29604495A
hashlookup:parent-total9
hashlookup:trust95

Network graph view

Parents (Total: 9)

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

Key Value
FileSize184752
MD5BFE847C8433F176732DBF9150146A8D2
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-1FCE6EC8A0504123CF9D4B84ED774DBC34E9A03D1
SHA-256C6A84D9E345DAD15959CCFDE0DEFDDB111354A51F9532BEA04AEFE906EBAD6A4
Key Value
FileSize184752
MD5CBA39BEFEDDFBA2D66DD52FD525DD4CE
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-17FCE7211664B0D2EC531605177E9B917A81257B8
SHA-25696506122B1705C6AF85B28EC351A9CB973D9D4DDE0C2A62D4962908D20371459
Key Value
FileSize184752
MD53549E4E8BAEBE4D072CB1CC968D5DA3A
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-1887AC2A327D48B6B3C09C0189BF6AB013C966D35
SHA-2563AC78875545B0A4397F0BAD35044E86EF87FAE7252221C53BA436E9347FF4428
Key Value
FileSize184752
MD587ABBE2790229A5C13EC4E28EB82950E
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-1A579021F1839D6B3CFF9B006E535C0D625C7F495
SHA-25687468F51BBEC13C2FAA058C434C5984AB8CE9F675B2C381B12518D7F55E0012C
Key Value
FileSize184752
MD5BA161514064A8446E30CECBB3C787B98
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-155CBBB9C5EF86B49AF97EABEDC3BD498DDB4E55C
SHA-256A897313DE147CE224DC572DE5700B6421E42266F55AF96DDC9965A388B1FF9E1
Key Value
FileSize184752
MD5DE7713D8838849A04A44C6F46F38AB18
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-17B90A4F6F12ECD08B6EAA7E92A2732EFD87139C9
SHA-2561E14954D368C7B743EC7D6D62DAC9AD671D2DC885FD916AE63732D6A13E9B091
Key Value
FileSize184752
MD551233BC6B6BBAD6DAF983B8B9374327E
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-146FFF6E78F4D3D3DE3589921B77FED4DEA77F831
SHA-25687BD9BA1DABB01989CB8F775AAC413CA9300D6E2BAC5BBA548E2443E86DEA30A
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
FileSize184752
MD516BDEFFD56FE98B9CC2DF4A5BA2EE367
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-1B5592BAAC896F88AF4719EDD92D0CA0A34A41892
SHA-256C904150DDCA614D002F27193D3BEBA9540A6ACE9B4FF3567349B93A3AB33A6A8