Result for 476394AC63CA43C60D53824B45792930681C6DD8

Query result

Key Value
FileName./usr/lib64/erlang/lib/pkix-1.0.4/ebin/pkix.beam
FileSize58556
MD51F33294CEA5DEF88731E00252B82177E
SHA-1476394AC63CA43C60D53824B45792930681C6DD8
SHA-256F9BA02449421FCB9C84C8BE95A4AD69A36A6C41F4C7C132FE058C395250813DB
SSDEEP768:q0cBU8Xz+mYJcu48h0QOQBMqYP91edStAbXDFGkuFN+UhcrkUK4clD+YzCirNNkT:qHUGz3WhmkIHCHcnP+UhcBK9lKLS1S+m
TLSHT15043CF580B782F15DAE32F7436ED674323A2E9B6479027038050FA7FF6A4F5C6068979
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