Result for CC58015651FE11FF0FB7977D49DF2D7D412E83DD

Query result

Key Value
FileName./usr/lib/erlang/lib/p1_pkix-1.0.0/ebin/pkix_sup.beam
FileSize1564
MD5AB6A803C4A36F9732B8686FF3FA0620B
SHA-1CC58015651FE11FF0FB7977D49DF2D7D412E83DD
SHA-256E9E7AED49FB43B2C55659892C9E7AFF9CBEDF7C4A08BD4E0EA12AAC818ABE2E2
SSDEEP24:hMo2Y4xbkBX4s4yvX9/ZHCt2w/bWju5jG/BMkL58HfKHSStYb0Nru7fmZyft0:hMBNCXPP9zagcfKSKYbmOa
TLSHT1BE31F7325E946683C06F023252269B39E3B8ABCC476CFD060BAC9E8BD2606F04004504
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
FileSize163688
MD50D1D549648EC2A26E0477FFDCC21FE64
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-181207B6E5C23C3F229AD8B5F4E084B408A0FE5BD
SHA-256021388E0612F4F41F0297AE8E6CD905EECD914A47F85C5C50F000CF46CB66A91