Result for 38788954999ED368E70F419E398D9112E5CE5731

Query result

Key Value
FileName./usr/lib/erlang/lib/p1_pkix-1.0.0/ebin/pkix_app.beam
FileSize1724
MD574D28875A08C56C9D29D3304AA19A614
SHA-138788954999ED368E70F419E398D9112E5CE5731
SHA-256EE1AFDB162FAC53F4F5AC0885103F36AEF797A226B42241CD498A57898778228
SSDEEP48:hnoc8MYFMtNM6g497oJG8hjiG23x/DIO+gV2:loWDMR4RoJzh2Ga/1+1
TLSHT1A9310C399E488397D6160033EA8E5739E42D97DA33B56498D2ECC5064DC01E40527E60
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
FileSize162500
MD5B1810A4A4907C89271A321C4992C5384
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-1BB744316714A75ACCE4C64DB94663E99C9DDE643
SHA-256238E0C2431BA77CFB15B351AFBC4C3A8BCF952CC73548F88FAA1AD072F65B97D