Result for FFE7B5ADD8CC20F750B11A3EEE7916052F37544A

Query result

Key Value
FileName./usr/lib64/erlang/lib/pkix-1.0.8/ebin/pkix.beam
FileSize58520
MD5B19B632756A39BA57AB7DDEA4B93FD35
SHA-1FFE7B5ADD8CC20F750B11A3EEE7916052F37544A
SHA-25680E67CEB540932B3EC5ACB5FF4D0C45C3B83D6CA2F92DCE5767404AE2B446E6D
SSDEEP768:m0cBU8Xz+mYJcu48h0QOQBMqYP91edSxAbXDFGkuFN+UhcrkUK4clD+YzCirNNkJ:mHUGz3WhmkIHuHcnP+UhcBK9lKLS1S+I
TLSHT1E943CF590B782F15DAE31F7436ED670323A2E9B6479027038050FA7FF6A4F5C6068979
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
MD58AC841ADD778D80AD06A909B73308422
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
PackageReleaselp151.8.1
PackageVersion1.0.8
SHA-1C154F9B1DC4BC6B91AF16BB3E9A43974DD5DD96A
SHA-2563191B9191C6D08251480C1986E486F9BB89C19D70EF6F2FFD623C77C81534422