Result for 248301A300273C897F4B38132DB6AD5B7571F97A

Query result

Key Value
FileName./usr/lib/erlang/lib/p1_pkix-1.0.0/ebin/pkix.beam
FileSize51280
MD5E9CDD3FCC6D7801980728E34D2B9FCB7
SHA-1248301A300273C897F4B38132DB6AD5B7571F97A
SHA-256E266027E1DC0A41319C87FC58341858EFEE8EB160152AB6B982F0DB1B15026A7
SSDEEP1536:+hwJ6aHo5hCbUIfeIsRpZqcPdH+6nuTzWBm:qwJxUwUeeIsJqiHnE
TLSHT10F33C06807B00A83EFD34FB474DA97027BF4F978572827133589B5BB99D4B686118C2B
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
FileSize163688
MD50D1D549648EC2A26E0477FFDCC21FE64
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-181207B6E5C23C3F229AD8B5F4E084B408A0FE5BD
SHA-256021388E0612F4F41F0297AE8E6CD905EECD914A47F85C5C50F000CF46CB66A91