Result for 6399676A2CBE0BD3988EA3D1FE4D41724C86EACC

Query result

Key Value
FileName./usr/lib64/erlang/lib/pkix-1.0.8/ebin/pkix_sup.beam
FileSize1516
MD5DDE01F074C3F55A1E1116C10099803B3
SHA-16399676A2CBE0BD3988EA3D1FE4D41724C86EACC
SHA-25601102EBCA4B0A15DC6288B9802FFD6ED066C8B7BF032CDF147E48613F14E05E2
SSDEEP24:hxo2Y4xbkBX4s4y/n9/ZHCt2w/bWju8iz/ahw0jUPvlZlBQGeMV6DlafmuIEf6eQ:hxBNCXPP9zRimxyjbnwo+uIEf6NBR
TLSHT11231E9211FA55BC3C0C942B860164B1FDD3172DE0FB88D491B646DCBA681EFD6548BCA
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