Result for B4A58244393C398F3E01FE8E1D027024B3A05740

Query result

Key Value
FileName./usr/lib/erlang/lib/p1_pkix-1.0.0/ebin/pkix.beam
FileSize51280
MD57014FC1A17C427870D2F1BD6B35CFA9E
SHA-1B4A58244393C398F3E01FE8E1D027024B3A05740
SHA-25617AEBEA8805ACA8EC7A5857E7B87C02AAC69A9DF5586191AB8289B2E220CFD53
SSDEEP1536:+hwJ6aHoJhCbUIfeIsRpZqcPdH+6nuTzWBm:qwJxYwUeeIsJqiHnE
TLSHT1D533C06807B00A83EFD34FB474DA97027BF4F978572827133589B5BB99D4B686118C2B
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
FileSize163696
MD588ACCDCE6CA9F6A3A6852251460ADBD1
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-1F37875F73449B9CCFC001AA74A40DC981F0B3EAA
SHA-256A0F8CF956572374C62ED68A97685BD1D8AE43DE2DFDB2D8C6CE3FFA24C02C8CD