CPSA ยท Cryptography for testers
SSL/TLS, SSH and PGP: what each protects and how trust works
What each protects, how trust is established and typical misconfigurations.
Key points
- TLS: protects data in transit; server certificate signed by a certificate authority, chained to a trusted root.
- SSH: remote shells and file transfer; trust-on-first-use of a host key in known_hosts, user auth by password or key.
- PGP: files and email end to end; web of trust of key signatures.
- Flaws: SSLv3, TLS 1.0/1.1, weak ciphers, expired or self-signed certificates, ignored host-key warnings, SSH root login or password auth.
Practice questions
Which system builds trust through a 'web of trust' of key signatures rather than certificate authorities?
- TLS
- SSH
- PGP
- IPsec
Show answer
Answer: C. PGP
PGP users sign each other's keys so trust spreads through those signatures. TLS relies on certificate authorities, and SSH normally relies on host keys known to the client.
Which of these are typical TLS misconfigurations a tester would report?
- An expired certificate on a production site
- A self-signed certificate on a public-facing service
- Null or export-grade cipher suites still enabled
- TLS 1.3 enabled alongside TLS 1.2
- HSTS header present
Show answer
Answer: A. An expired certificate on a production site, B. A self-signed certificate on a public-facing service, C. Null or export-grade cipher suites still enabled
Expired or self-signed certificates and null or export ciphers weaken or break the trust and encryption TLS promises. TLS 1.3 and HSTS are good practice.
A changed SSH host-key warning can be ignored, because SSH traffic is encrypted anyway.
Show answer
Answer: False
False. Encryption to the wrong party is worthless. A changed host key can mean a man-in-the-middle or a reinstalled server, and it must be verified out of band before continuing.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
