Result for 7EC14B55E465AC2BB7EA3FC0577EAA37F6ED745C

Query result

Key Value
FileName./usr/lib/erlang/lib/p1_pkix-1.0.0/ebin/pkix_sup.beam
FileSize1564
MD55BA2C61D54FA1CF98A0E03CFECE6C5AC
SHA-17EC14B55E465AC2BB7EA3FC0577EAA37F6ED745C
SHA-2568BB34539906ED97198B52971C875A563EBFA1078EE826AF8B975DDB9D898BC06
SSDEEP24:hMo2Y4xbkBX4s4yvX9/ZHCt2w/bWju5jG/BMk758HfKHSStYb0Nru7fmZyft0:hMBNCXPP9zaUcfKSKYbmOa
TLSHT1A03119325EA85683C06F023256269B3DF3B8AFCC4B6CFD060BBC9E8BD2607F04004504
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
FileSize163692
MD5B64DE7788349C431DDC121A236121CFC
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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNameerlang-p1-pkix
PackageSectionlibs
PackageVersion1.0.0-3
SHA-174460F747DFFC9BBF09CC0605A6ACFFED555AA40
SHA-256B35FC4E6714F45FAB6E748ECF0898C226C943D342ECF670B07CBC590613435C3