Result for 6E1F1BAAE415F9392CC92C322C7D6AD7545817A2

Query result

Key Value
FileName./usr/lib/erlang/lib/p1_pkix-1.0.0/ebin/pkix.beam
FileSize51736
MD5E50873AA3D1FF31FCC6E6236F0817789
SHA-16E1F1BAAE415F9392CC92C322C7D6AD7545817A2
SHA-25686B739AE1AEC62778334A33AB3DF99E3CC2BCB578AC849169B08E55F43BE8A29
SSDEEP768:fgwNwxSnVyRqyovY9cgV3NRoj3U0OQKTKxPFxcFVCAiq5ruF6:fhwxS+HMVjfPr8VnI4
TLSHT13833D05D07B40B92EFE34FB176DF5703BA68E83025152B0715C1B57B64E4FA8A30A45B
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
MD5F80E848E1097ADC0AB64509E70A0FF40
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-1F9DAA57D42E22E954044BC26F6CC6EA51D7346BE
SHA-2565483CCC9CA4A8F750F4FF1DF38119E9DC3586CEF5D110D5D06679FE1D21ABB1C