Let’s Encrypt! Wait. Why? How?
summary
Let’s Encrypt issues over 5 million SSL certificates (nearly 4 million active by summer 2016) as a free automated CA that creates keys and gets domain-validated certs with two terminal commands or host integrations. Certificates require 90-day renewals, work on common hosts and WordPress.com (custom domains have HTTPS), but fail for some load‑balanced or exotic setups and don’t protect stored data — they encrypt only in transit and don’t replace good passwords, server hardening, or backup/rotation practices.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 0:55What is HTTPS
- 7:48Edward Snowden
- 11:03Freedom of Software
- 12:57SSL Certificates
- 15:30How Does SSL Work
- 18:02What is a Certificate Authority
- 19:18What is Lets Encrypt
- 20:30Lets Encrypt Setup
- 22:18How to Encrypt
- 23:37VPS
- 23:57WordPresscom
- 24:22Common Issues
- 27:32FAQ
- 30:18Common misconceptions
- 34:55Lets Encrypt
- 36:22Changing Hosts
- 37:35Do I need 3 certificates
- 38:48Is there still benefits to using an SSL certificate
- 40:15Is there a difference between paying for something over a public WiFi network over a private WiFi network
- 42:58Paid certificate authorities vs less encrypt
