Result for 1C138C362C18335DD0320B3DFCD85BE0CF27A3E7

Query result

Key Value
FileName./usr/lib/erlang/lib/p1_pkix-1.0.0/ebin/pkix_app.beam
FileSize1724
MD5F50A5417C13B04BEBEF90BCAE22CD6D7
SHA-11C138C362C18335DD0320B3DFCD85BE0CF27A3E7
SHA-2563755CB3AA68A503D22EC60C888197E396CA4CC3072B2F4EF2A887A0DC01854BB
SSDEEP48:hnoc8MYFMtNM6g4971NG8hjiG23x/DIO+gV2:loWDMR4R7zh2Ga/1+1
TLSHT13231EC399E488397D6160033EA8F5735E82D97DA33B96498D2ECC5464DD01E44567E60
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
FileSize162494
MD5A26F7A14291AECD894887E0E4DA58FEC
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.
PackageMaintainerEjabberd Packaging Team <ejabberd@packages.debian.org>
PackageNameerlang-p1-pkix
PackageSectionlibs
PackageVersion1.0.0-3~bpo9+1
SHA-1A2B3EB33E7B4C52B1559AEA513EF954296508BBD
SHA-2562CBAB09CA48CEBFD303A1DD836BD02EA4FCA597BDC76A833A33A578D52A1AB0B