Result for 9733371C84E45875B14E6B9B1934118438B40CAE

Query result

Key Value
FileName./usr/lib/erlang/lib/p1_pkix-1.0.0/ebin/pkix.beam
FileSize51736
MD5F0309327D772E020F3A7B30C07AE7E9A
SHA-19733371C84E45875B14E6B9B1934118438B40CAE
SHA-256FD64BD20C9CA555D4EE5F37A0368D9ED137DB09A9E5B1292F2D6596F152180A6
SSDEEP768:fgwNwxSnVyRqyovY9cgV3NRqj3U0OQKTKxPFxcFVCAiq5ruF6:fhwxS+HmVjfPr8VnI4
TLSHT16533D05D07B40B92EFE34FB176DF5703BAA8E83025152B0715C1B67B64E4FA8A30A45B
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
FileSize164112
MD57B8AB134A70245A9E4F61F23EA7598E8
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-11C82192DA36321B2300736AB07599D7A0FAAED5A
SHA-2561295057D46146F5BD4409B5094858BA7D6047D813585DD8CB1999659A46DCF50