Result for 5E57E0E7949580287DB2A66C6A8467A8E85BA915

Query result

Key Value
FileName./usr/lib/erlang/lib/p1_pkix-1.0.0/ebin/pkix.beam
FileSize51280
MD589320E7918B8B5317191B7E2BD9ACFD7
SHA-15E57E0E7949580287DB2A66C6A8467A8E85BA915
SHA-2568F816118C6A1CE6F4629E50A27A0D762B615E5BE0CE46EA4AC8D42DB1B48E57C
SSDEEP1536:+hwJ6aHoThCbUIfeIsRpZqcPdH+6nuTzWBm:qwJx6wUeeIsJqiHnE
TLSHT1AE33C06807B00A83EFD34FB474DA97027BF4F978572827133589B5BB99D4B686118C2B
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
FileSize163692
MD555AA6789D5080E007E4EDF351020ADFF
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.0-3
SHA-1630259DB5B34C393025AF54A9DA69125BF56AEE9
SHA-256E0888AB5D8A6EDC04532BFFC2946ECEC7792F709FA7C4CE0830E635358312E96