Result for 3A685403988B93FBC69DDE040D3C65A234130026

Query result

Key Value
FileName./usr/lib/erlang/lib/p1_pkix-1.0.0/ebin/pkix.beam
FileSize51736
MD58787EB4D8F38CD00F6B5B73FE301F9A8
SHA-13A685403988B93FBC69DDE040D3C65A234130026
SHA-256AAC26952A90B41C1A07D3DD0E23B7D68CDD10C1F302D6DB74FD8DC066C9B3DFF
SSDEEP768:fgwNwxSnVyRqyovY9cgV3NRmj3U0OQKTKxPFxcFVCAiq5ruF6:fhwxS+H6VjfPr8VnI4
TLSHT14E33C05D07B40B92EFE34FB176DF5703BAA8E83025152B0715C1B57B64E4FA8A30A45B
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
FileSize164108
MD521D01620AF43B91CBD09DC7CCA58A5EA
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-142B987FADCCE0D4AE56EE14FB39A7280705C1E9B
SHA-256E0FDD6C4FFF58B6A78961E4E3FE72676B2B72A31A5D96ABDFCB83E233D8886E9