Result for E9ADD739B16D05970D3494740F8DC1BEFC1B0C33

Query result

Key Value
FileName./usr/lib64/erlang/lib/pkix-1.0.4/ebin/pkix_app.beam
FileSize1732
MD506E419BCC1C066E80E1F2D95236620D7
SHA-1E9ADD739B16D05970D3494740F8DC1BEFC1B0C33
SHA-2561897921E4A12ECF2910F04571499EC6DDB62D11FCD462492B89BFC63D16614C0
SSDEEP24:h1cnbjEMYFMtN/IztvHagl/euM7W2rY5cdC0KseA4kBkj+oAJDobOjcS13g461Jj:h1c8MYFMtNM6gEr7XdCpA6+oAZjK+DQ
TLSHT19931FAB94F496B03D5394131AE912379ADA752F7F2FDDD44434D3AB41F822E68846C14
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