Result for EB4EB9D992AB77B074116168BC538BF3B9B4395B

Query result

Key Value
FileName./usr/lib/erlang/lib/p1_pkix-1.0.0/ebin/pkix_app.beam
FileSize1724
MD5EF0877E580F4352EE038A02804833205
SHA-1EB4EB9D992AB77B074116168BC538BF3B9B4395B
SHA-256AFC3A14846130EFF572DA889674FD74FC8A2E141D9EC6D7690FE0EC23D6E49A9
SSDEEP48:hnoc8MYFMtNM6g497PG8hjiG23x/DIO+gV2:loWDMR4RPzh2Ga/1+1
TLSHT1CB310A399E48839BDA220033EA8E6739E82E87EA33B5649892FCC5064DC01E00527E60
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
FileSize162496
MD5B08B3659FDAC7CE45968BBC05B059AD2
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-13A6FACD8D2E2D971E3D074154FFD851B1194DAFC
SHA-2561F9C9472D4CF1E4F48C17FBD16436E1C57787E3CFB6CBA9A9C21C853CF0108F4