A Walk Through the Land of
summary
Explains how Let’s Encrypt automates domain‑validated TLS certificates using the ACME protocol, issuing 90‑day certs to reduce revocation impact. Describes the stack: Certbot (Python client) talks to Boulder (Go server), integrates with existing PKI checks (OpenSSL chains, CRL and OCSP), supports HTTP and DNS challenges, and manages CSR/chain handling to enable large‑scale HTTPS deployment while leaving EV/org validation and wildcard support for future work.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:47Asymmetric encryption basics
- 7:09X.509 certificate structure
- 14:15Certificate authorities role
- 17:51Certificate chains and trust
- 23:06Revoking compromised certs
- 26:55OpenSSL certificate validation
- 28:40ACME certificate automation
- 31:51ACME protocol details
- 33:14Let’s Encrypt explained
- 36:22Certificate signing demo
related talks
25mSSL All The Things
26mSSL all the things
22mACME: Certificate management has never been easier
42mLet's go HTTPS
06mKeynote: Ten Years as a Free, Open, and Automated Certificate Authority
13mLet's Encrypt or how to make your site HTTPS
45mLet's Encrypt ActiveMQ and Karaf!
24mMaking it easier for everyone to get Let's Encrypt certs w/ Certbot