Result for 2C186A35F81A1CCDC78386B87AA172E7C9E37A4D

Query result

Key Value
FileName./usr/lib/erlang/lib/p1_pkix-1.0.0/ebin/pkix.beam
FileSize51280
MD5D903C870B9AA14888CDC4BFA7AD8FCAE
SHA-12C186A35F81A1CCDC78386B87AA172E7C9E37A4D
SHA-256F7B47BDA7A4841D2E06C368671E749A4611539EF62F8054CC106E78A3E560C52
SSDEEP1536:+hwJ6aHoVhCbUIfeIsRpZqcPdH+6nuTzWBm:qwJxEwUeeIsJqiHnE
TLSHT1C933C06807B00A83EFD34FB474DA97027BF4F978572827133589B5BB99D4B686118C2B
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
MD5B64DE7788349C431DDC121A236121CFC
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-174460F747DFFC9BBF09CC0605A6ACFFED555AA40
SHA-256B35FC4E6714F45FAB6E748ECF0898C226C943D342ECF670B07CBC590613435C3