Result for A9007EE1FBBB3DC6098E5D4A5AFA08966A6BA47B

Query result

Key Value
FileName./usr/lib/erlang/lib/p1_pkix-1.0.0/ebin/pkix.beam
FileSize51280
MD5CF584D48ED150890D7ABDEF296D1D81C
SHA-1A9007EE1FBBB3DC6098E5D4A5AFA08966A6BA47B
SHA-2566DDB98B329268D88849EEEED8DD7F28958E8FB26281CB43DDCA8C334EE9F5E0F
SSDEEP1536:+hwJ6aHonhCbUIfeIsRpZqcPdH+6nuTzWBm:qwJxqwUeeIsJqiHnE
TLSHT12E33C06807B00A83EFD34FB474DA97027BF4F978572827133589B5BB99D0B686118C2B
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
FileSize163676
MD5BB2CE7BA3A7CA76730F013023C2D93AD
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-15C768562B89DFC2F226634540BAB74E5CE005B9C
SHA-2562DDFB54DDB7806ACEDFD0DF4C81263E905B99472CCC9EBDA9DC1AB39A5A90FC7