Post-quantum TLS in Go: on by default, unless your go.mod says otherwise
Go 1.24+ negotiates X25519MLKEM768 by default, but an old go line in go.mod, CurvePreferences or TLS 1.2 turn it off. How to check and fix it.
Read articleGo 1.24+ negotiates X25519MLKEM768 by default, but an old go line in go.mod, CurvePreferences or TLS 1.2 turn it off. How to check and fix it.
Read articleNode.js 22.20+ and 24.5+ negotiate X25519MLKEM768 by default. Which versions do it, how to verify it, and the ecdhCurve setting that turns it off.
Read articleGo says x509: certificate signed by unknown authority but your browser works? The four causes, how to tell them apart, and the right fix for each.
Read articleNode.js says unable to verify the first certificate but your browser works? What UNABLE_TO_VERIFY_LEAF_SIGNATURE means and how to fix it properly.
Read articleCSP across 25 endpoints, AEAD-only ciphers on Cloudflare and Go servers, and CAA records took SSLBoard from 92 to 99.
Read articleSSLBoard achieved post-quantum cryptography readiness by replacing Kubernetes ingress-nginx with Cloudflare Tunnel, enabling quantum-resistant TLS termination.
Read articleStoring 1 billion SSL certificates is a challenge. We use BadgerDB, an LSM-Tree database optimized for fast writes, efficient expiration, low-latency lookups.
Read article