Result for EAC1B9C0B27A83555363E6E051F8A28E1A0F3D5E

Query result

Key Value
FileName./usr/lib64/erlang/lib/pkix-1.0.4/ebin/pkix_sup.beam
FileSize1556
MD54DFDAE4A71426B609533E2BC8DCA3500
SHA-1EAC1B9C0B27A83555363E6E051F8A28E1A0F3D5E
SHA-25625C9CE41A004F279C9F750DF65BF14654A4040B38C2AE3DD321A699B52E0FE3B
SSDEEP24:h0o2Y4xbkBX4s4y/n9/ZHCt2w/bWju8iz/euM7B8HfKHSStYb0Nru7fmZyft0:h0BNCXPP9zRiCr7BcfKSKYbmOa
TLSHT1FC31E9321B9856C3D06F0232A725A739F3B5BFCC477CAE5F0BAC9A4B81617F48044601
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
MD52A329C5562DCC678BDE5C734B6D92070
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
PackageReleaselp150.4.1
PackageVersion1.0.4
SHA-123A5B895D89CDA3C0508F7535C8F7D89CCF45669
SHA-256DCCD5C9B9842E5B6E307A24E22B4175305A8A4948DF4214F4706D1625CBBF30F