Result for F1E363611223E654E34B37BA8D85AEE6BD1EFD15

Query result

Key Value
FileName./usr/lib/erlang/lib/p1_pkix-1.0.0/ebin/pkix.beam
FileSize51736
MD569B3CED44A7F5C71AD506FAD0E3545DB
SHA-1F1E363611223E654E34B37BA8D85AEE6BD1EFD15
SHA-25609D6F47DBEF7A1E5A55EDC9E3C0678809DB6A295FF8CCB8365F3D527CBC1001B
SSDEEP768:fgwNwxSnVyRqyovY9cgV3NRQj3U0OQKTKxPFxcFVCAiq5ruF6:fhwxS+HsVjfPr8VnI4
TLSHT1CB33D05D07B40B92EFE34FB176DF5703BAA8E83025152B0715C1B67B64E4FA8A30A45B
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
FileSize164092
MD55AA88B67B4BF6C26C057EA099657AA33
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-113D65A88912ED0496A1520A259D249164128073F
SHA-2568870AED7ABCB198F9D59558B64FE6B6EDB4A38016FE5693F21F044011B2FC017