||2 months ago|
|LICENSE||3 months ago|
|README.md||2 months ago|
|trust-seeker||2 months ago|
Verify TLS certificates using different network perspectives.
Trust Seeker is a certificate pinning program that can be run privately, on the command line, or publicly, as a server-side CGI script. Each public trust seeker can be asked what certificate it sees for a certain host. Client software can query multiple trust seekers, to check for consensus.
It aims to bring as much relevant information as possible to bear on any trust decision. This includes the TLS version and cipher suite, to help defend against downgrade attacks.
trust-seeker --ask https://example.org/cgi/trust-seeker \ --verify gemini.circumlunar.space:1965 \ --fingerprint sha256:1234567890123456789012345678901234567890123456789012345678901234 # Response: status=mismatch fingerprint=sha256:1a03a15619200db4496494ec90381c1fe8bd9e0142260f6d8a3d962ed3cfc72f fingerprint_base64=sha256:GgOhVhkgDbRJZJTskDgcH+i9ngFCJg9tij2WLtPPxy8= expires=1759488637 tls_version=1.3 cipher_suite=TLS_AES_256_GCM_SHA384 first_seen=1617463930 last_seen=1618133995 seen_count=2
Trust Seeker mixes ideas from:
- Moxie Marlinspike's Convergence project
- Recommendations made in "Public Key Pinning for TLS Using a Trust on First Use Model" (Gabor X Toth & Tjebbe Vlieg, 2013)
It can verify TLS certificates on any host and port, regardless of the protocol underneath: HTTP, DNS (DoT and DoH), e-mail (SMTP, IMAP, POP3), IRC, FTP, Gemini, Gopher, etc.
SSH and STARTTLS support are on the roadmap.
Trust Seeker can be used with command line tools that support public key pinning, such as curl and wget, to protect every connection they make. For instance, this is how it can be used with curl to verify a self-signed certificate based on example.org's network perspective:
# ask example.org about self-signed.badssl.com response=$(trust-seeker --ask https://example.org/cgi/trust-seeker \ self-signed.badssl.com:443) # get certificate's public key (SubjectPublicKeyInfo) spki=$(echo "$response" | grep 'fingerprint_base64=sha256:' | cut -d ':' -f 2) # get minimum TLS version tlsv=$(echo "$response" | grep 'tls_version=' | cut -d '=' -f 2) # run curl with key pinning instead of CA validation curl -k --pinnedpubkey "sha256//$spki" "--tlsv$tlsv" https://self-signed.badssl.com/
The holy grail is to enable this kind of dynamic key pinning for e-mail server-to-server communication, which generally relies on opportunistic encryption.
The code is in an early exploratory stage. You can experiment with it, but big changes are planned and there is no regard for backward compatibility at this point.