Result for 56FA39D711A9D352E237DE49D4AE435731B92007

Query result

Key Value
FileName./usr/lib/erlang/lib/p1_pkix-1.0.0/ebin/pkix.beam
FileSize51736
MD542054699B7A6BDB5F17A1F1142045E0E
SHA-156FA39D711A9D352E237DE49D4AE435731B92007
SHA-25629D7EBCC7068B24F8D7B26DDD5428BE855179C7A08A5E3AD2D66B79D2FFA517E
SSDEEP768:fgwNwxSnVyRqyovY9cgV3NRZj3U0OQKTKxPFxcFVCAiq5ruF6:fhwxS+HNVjfPr8VnI4
TLSHT1E833D05D07B40B92EFE34FB176DF5703BAA8E83025152B0715C1B67B64E4FA8A30A45B
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
FileSize164104
MD5976072488795929B8ED1C6E90E1420D7
PackageDescriptionPKIX certificates management library for Erlang The 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 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: . certfiles: - /etc/letsencrypt/live/*/*.pem . The purpose of this library is to do this dirty job under the hood.
PackageMaintainerEjabberd Packaging Team <ejabberd@packages.debian.org>
PackageNameerlang-p1-pkix
PackageSectionlibs
PackageVersion1.0.0-3+deb10u1
SHA-14645BB1D51A81DB583FF9BCA873741A52755B0E9
SHA-256C2202139C97F2D464D286E5C4D5BC87DBBEE98B00A6F117A5E17C1C8F6EF7642