Result for F6EE09BD71FCDC1A3FCF63EA899C052EA8A285AF

Query result

Key Value
FileName./usr/lib/erlang/lib/p1_pkix-1.0.10/ebin/pkix.beam
FileSize65768
MD551A71F895F694165D1D9A56DB9DC8C95
SHA-1F6EE09BD71FCDC1A3FCF63EA899C052EA8A285AF
SHA-25619B99EE0B632337CD3DD9DE8DA61243AB9574C3AB24E8A1332A3144E646E1B5F
SSDEEP1536:kspahoUB+2CeB3ZeyCXiUdYEX5n2yXz2Xq459e/i58tE6OG:DahzBJ1E2UdYOnBf40HOG
TLSHT13B53C05A0FB40F63DA87AFBA27ADD743B710EC71A7383C130285756985B4F4870969E8
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
FileSize178460
MD5075843C5416EB9899C58B9D3AE6F06FB
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.10-2
SHA-1945D20F24A6185328D1EE118310E4228C30C9598
SHA-25691CBF83FBD4BEB475E162355382424BA2AE0A3F412AE73F830D3FCE357E79250