Result for 3C2F5EB57892DD2B2F69182EC779FE4735578EA8

Query result

Key Value
FileName./usr/lib/erlang/lib/p1_pkix-1.0.0/ebin/pkix.beam
FileSize51736
MD500DBED50787C0BBB859BB505C54D6360
SHA-13C2F5EB57892DD2B2F69182EC779FE4735578EA8
SHA-2566C57984A6D463D882E2D67D874BA67A76928D4223B493BF2C1B293728714ED2D
SSDEEP768:fgwNwxSnVyRqyovY9cgV3NRrj3U0OQKTKxPFxcFVCAiq5ruF6:fhwxS+HXVjfPr8VnI4
TLSHT16733C05D07B40B92EFE34FB176DF5703BAA8E83025152B0715C1B67B64E4FA8A30A45B
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
MD522960356A676901DC96DA17E8F1C2C82
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-17980749CBB23516F99E1BA6DA5260BDB541B023B
SHA-2567FBA2E884680BAB9DA511B9FFC7F39057A5D92F86C188003012C9CB3CAD46FED