Result for 12EB558598E52B1648F9B9A5B089E9B94FC34F02

Query result

Key Value
FileName./usr/lib/erlang/lib/p1_pkix-1.0.6/ebin/pkix_app.beam
FileSize1564
MD5F2EE894321DCE6A4B401C33DE6CCDED8
SHA-112EB558598E52B1648F9B9A5B089E9B94FC34F02
SHA-25684CD067D45341A951E3CA2278C07E0993098AC9AEF3DFB1596BF96BD64E51F7A
SSDEEP48:hNcMMYFMtNMfP67fYV2DPyyzRNPIKr/CF9:bmDM3kfYeH9bCX
TLSHT10C311BAC1FC95D07CF08013AD56B321971A227BB97BE1905D6E8C6E8A5C13741FF2A6C
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
FileSize175072
MD53C0752CBB22F28AF269455B743A36408
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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNameerlang-p1-pkix
PackageSectionlibs
PackageVersion1.0.6-1
SHA-1F05B9EE069867D873833E0EA1CFB26E033A17B24
SHA-2561D83CD3A7C3D66047EAF7E3740E4ED207FCD6E7E5381EA6BD668AEABE9F84D6B