Result for 2B4778F596CFA2FA14DBDEDBAF3DBD9298D86333

Query result

Key Value
FileName./usr/lib/erlang/lib/p1_pkix-1.0.4/ebin/pkix_app.beam
FileSize1564
MD5C2C6336331A4BCE2A02339CC7062C115
SHA-12B4778F596CFA2FA14DBDEDBAF3DBD9298D86333
SHA-256CF285904C2E4407320E68E960627131F68675C588839AE968B01F42D85894DC9
SSDEEP48:hNc8MYFMtNM6gJO7fYV2DPyyzRNPIKr/CF9:bWDMRifYeH9bCX
TLSHT1C731E96C1F884D07CE18013AD57A3119719627BB57BE1905D5A8C6E865913B01FF2A2C
hashlookup:parent-total1
hashlookup:trust55

Network graph view

Parents (Total: 1)

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

Key Value
FileSize175112
MD52AF84B2F4415FC33B643BA473F8C16D4
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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNameerlang-p1-pkix
PackageSectionlibs
PackageVersion1.0.4-2
SHA-1501485FF6DCE216479B477414F2D6FE67D023A39
SHA-2567CD612058FD2F57203AE95FEC475C3BDE9C66297D8F81CB2034583E2D47F073A