Result for 061BF96024D77213A40571CC810B1D779E073AF7

Query result

Key Value
FileName./usr/lib/erlang/lib/p1_pkix-1.0.0/ebin/pkix_app.beam
FileSize1700
MD56F62323005155347365CA3375203EF9C
SHA-1061BF96024D77213A40571CC810B1D779E073AF7
SHA-256D3FD468AC16FB3B00EF811236DBC28345F8063D39F8E65BE015B50CC7AFB59AA
SSDEEP48:hPoc8MYFMtNM6ge7+G8hjiG23x/DIO+gV2:NoWDMRK+zh2Ga/1+1
TLSHT19D310C399E488397DA260033EA8E5735F829D7EA33B565D8D2ECC5454DD01E44457E60
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
FileSize162490
MD59C5E8EE0A59DC6C9B0D69102427790CD
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~bpo9+1
SHA-175466162B59133AE573D69799DDE2B7317E31821
SHA-2561A3335C3D4FD74E00530B7AFA728DC97322CB7598B3B33B8524071740B8E0DBE