Result for C38663FB74E4662E06F9225DC3D849F76659D98F

Query result

Key Value
FileName./usr/lib/erlang/lib/p1_pkix-1.0.0/ebin/pkix_app.beam
FileSize1724
MD5F2D368B5C679BB701DE5B48E9251E303
SHA-1C38663FB74E4662E06F9225DC3D849F76659D98F
SHA-2567B7D2A5A8E1886F637ECC257123EFAB460782A562BFB6B0CD4FE25EC6210CBD2
SSDEEP48:hnoc8MYFMtNM6g497oG8hjiG23x/DIO+gV2:loWDMR4Rozh2Ga/1+1
TLSHT16531EA39DE48839BDA260033EA8E6739E83D97EA33B9649892FCC5464DD01E44567E60
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
FileSize162500
MD56708591F31A43DFFE5B925AA93A44B5D
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-166E52852EE278F819C459DDF2D950E1448792CA2
SHA-256290037E6F9A732EEDD18F847F24B1B9C681781E1CBF0D06DD1B50847E98C76E0