The first 200 milliseconds of HTTPS
summary
Step‑by‑step break down of the first 200 milliseconds of an HTTPS connection: ClientHello → ServerHello exchanges ciphers and random nonces, server sends X.509 certificate, client returns an RSA-encrypted pre-master secret, both sides derive master secret and separate client/server keys, then send ChangeCipherSpec and encrypted application data — the handshake completes in about 200 ms. Demo uses Wireshark plus SSLKEYLOGFILE to decrypt captures. Warns that only ~20% of sites use modern TLS1.2/PFS and that weak cipher choices or compromised private keys break past traffic.
AI-written summary · about
chapters (20)
- 0:00Start
- 0:11The First 200 Milliseconds of Http
- 2:40Ssl 1 0
- 7:23Tls 1 2
- 9:12Wireshark
- 13:32Hardware Random Number Generator
- 16:58Different Ways of Communicating through an Http Connection
- 20:00Always Configure Your Ciphers on Your Webserver
- 21:37Cipher Suites
- 21:48Extensions
- 22:45The Heartbeat Extension
- 26:16Certificates
- 26:58Ssl Certificate
- 28:17What an Ssl Certificate Is Not
- 31:47Implied Trust
- 34:42X 509 Certificates Are Used To Authenticate the Server
- 35:51Client Key Exchange
- 42:36Wireshark Can Decrypt Your Http Traffic
- 43:03The Ssl Key Log File
- 51:31How Can I Securely Set Up My Web Server
related talks
45mThe first few milliseconds of HTTPS
53m25 Years of SSL - Secure(ish) Sockets Layer
44mSSL/TLS for Mortals
58m25 Years of SSL - Secure(ish) Sockets Layer
14mJust the Cryptography You Need to Know for TLS
53mHansel and Gretel do TLS
50mSSL/TLS for Mortals
01h 00m25 Years of SSL - Secure(ish) Sockets Layer