SSL/TLS and certificates: handshakes, certificate authorities, Merkle tree certificates and the post-quantum transition.
The capstone to our RSA series. The math checks out. Shipping it as written gets you breached. This is the nineteen-year-old attack that proves it, and what belongs in production instead.
Microsoft is displaying escalating Secure Boot warnings starting May 13 (Windows 10) and May 16 (Windows 11). The original 2011 certificates expire in October 2026. Unpatched systems may refuse to boot. Here's the full technical picture and what to do.
Two papers dropped at the end of March. Both said the same thing in different ways: the quantum threat to elliptic curve cryptography is closer than we thought.
A deep-dive into the full cryptographic stack powering every HTTPS connection — RSA-OAEP, AES-GCM, ECDHE key exchange, and a working TLS 1.3 handshake simulation, all built in pure Python from first principles.
RSA-2048 can be broken with fewer than 100,000 qubits. What that means for TLS, certificate infrastructure, and the post-quantum transition already underway.
I will first highly recommend to read Installing the NGINX Web Server on Debian & Ubuntu and Installing LetsEncrypt's CertBot Package on Debian & Ubuntu articles
LetsEncrypt is one of many Certificate Authorities (CAs) that provide genuine SSL/TLS Certificates to people who want to secure the connection to their website. This allows people
