Result for 1A8718F02D2638113DF1AA169A2BAD3A50BDAA30

Query result

Key Value
FileName./usr/lib/erlang/lib/p1_pkix-1.0.10/ebin/pkix_app.beam
FileSize1800
MD5055880168F06711910B4831E0A1239E6
SHA-11A8718F02D2638113DF1AA169A2BAD3A50BDAA30
SHA-2568AE0B8B2BC8C6C7E1AD6540EC82E11DF51A8276B190816186D2C77F20386F6A4
SSDEEP48:hsciMYFMt7MNnoc7rBBIoyCjUcYkiMM/IpPYuktWP9:CEpM5p7rTTjUvIiS
TLSHT15431E6108F5D025BC49912729CDD060ABE6070BA577CDE4789B9A6812BC33500F674B8
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