Result for 1F118731E913C22D90E31BE12BC862E01AAAB166

Query result

Key Value
FileName./usr/lib/erlang/lib/p1_pkix-1.0.0/ebin/pkix.beam
FileSize51280
MD5EF1835C037271DF2C70E67D19994110E
SHA-11F118731E913C22D90E31BE12BC862E01AAAB166
SHA-256D012B4AADCFE191A402D7DCF25ECBF059C0606DCD2F1CF4C3C072D06803BB491
SSDEEP1536:+hwJ6aHoghCbUIfeIsRpZqcPdH+6nuTzWBm:qwJxFwUeeIsJqiHnE
TLSHT1DA33C06807B00A83EFD34FB474DA97027BF4F978572827133589B5BB99D0B686118C2B
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
MD5D99C4186CDC50C220711A9A7771AEC3C
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-114C60CB4A0F67B7C88C82AB50C9377AD8E9B60A5
SHA-2567381B41D7BDEF80D5AC4D6054418A95DAC2998E4605891711020F35D2E6A66E7