Result for 7EA1155CCFA09127F9F7A3ADE3F23C88DE3E25D0

Query result

Key Value
FileName./usr/lib/erlang/lib/p1_pkix-1.0.0/ebin/pkix_app.beam
FileSize1724
MD505509D7D67F1E11E189B329E9BF6378A
SHA-17EA1155CCFA09127F9F7A3ADE3F23C88DE3E25D0
SHA-256C4B7E5EE1403A17527DFC665189B4124B8F9A1C3836660E2AE470C316E9C7662
SSDEEP48:hnoc8MYFMtNM6g497jJG8hjiG23x/DIO+gV2:loWDMR4RjJzh2Ga/1+1
TLSHT173310A399E48839BDA220033EA8E6738F82D87EA33B9649892ECC5464DC01E40527E60
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
FileSize162498
MD59CE7183E049E18D14EFF0322685ECEB5
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-1224CF6579E22FB426ECB13D1464CDA77023C2494
SHA-2566094D97CAF15438D828DDAD767676F01A11EE9E4693BF084A0E7EA1E328BF071