Browse Source

minor changes in README.md

master
nervuri 4 weeks ago
parent
commit
5e91fe65e7
  1. 6
      README.md

6
README.md

@ -31,14 +31,14 @@ Trust Seeker mixes ideas from:
* Moxie Marlinspike's [Convergence](https://youtu.be/UawS3_iuHoA?t=2100) project
* Recommendations made in ["Public Key Pinning for TLS Using a Trust on First Use Model"](https://homepages.staff.os3.nl/~delaat/rp/2012-2013/p56/report.pdf) (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](https://github.com/curl/curl/commit/a1f06f32b8603427535fc21183a84ce92a9b96f7)), etc.
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](https://github.com/curl/curl/commit/a1f06f32b8603427535fc21183a84ce92a9b96f7), 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](https://curl.se/libcurl/c/CURLOPT_PINNEDPUBLICKEY.html) 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 using example.org's network perspective:
Trust Seeker can be used with command line tools that support public key pinning, such as [curl](https://curl.se/libcurl/c/CURLOPT_PINNEDPUBLICKEY.html) 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's trust seeker about self-signed.badssl.com
# ask example.org about self-signed.badssl.com
response=$(trust-seeker --ask https://example.org/cgi/trust-seeker \
self-signed.badssl.com:443)

Loading…
Cancel
Save