eMudhra Crisis: What self-hosters should check on their reverse proxies and containers
retained text
By now you've probably seen the news, eight intermediate CA private keys from eMudhra turned out to be trivial integers. One of them was literally the number 4. Chrome and Firefox pushed emergency revocations but if you run headless Linux servers, Docker containers, or reverse proxies, they don't get browser push updates. Quick checks for your setup: 1. Update stale container trust stores Old Docker containers built months ago still carry the CA store from the day they were built. Rebuild stale images or run: `sudo apt-get update && sudo apt-get install --only-upgrade ca-certificates` `sudo update-ca-certificates --fresh` 2. Add a DNS CAA record Lock down your domain so rogue or compromised CAs can't legally issue certs for your hostname. 3. Enable OCSP stapling on your reverse proxy Ensure your proxy validates revocations automatically. (If you run Caddy, you're already good, it handles OCSP stapling by default). 4. Turn on Certificate Transparency alerts If your DNS is on Cloudflare, turn on "Certificate Transparency Monitoring" in the SSL tab. You'll get an instant email if ANY CA on earth signs a cert for your domain.
document fetched 2026-10-27 00:30 · canonical https://reddit.com/r/selfhosted/comments/1xfxf8v/emudhra_crisis_what_selfhosters_should_check_on