Every padlock in your browser rests on one assumption: that the certificate authority vouching for a site kept its private key secret. This week a researcher showed that an Indian CA with 60 million-plus certificates in the wild had used single-digit numbers as its keys — one of them was literally the number 4 — and recovered them from public data in under a second.
the actual private key one CA used — a P-384 key should be a random 384-bit number
certificates eMudhra says it issued — all now untrustworthy
to recover the secret keys from fully public data
A certificate authority's whole job is to hold a private key no one else can guess, and to vouch for websites with it. This week security researcher Scott Helme showed that the Indian CA eMudhra had failed at the one thing — eight of its intermediate private keys turned out to be tiny numbers like 4, 56, 66 and 237, recoverable from the public certificates in under a second. A P-384 key is meant to be a random number out of roughly 2384 possibilities; these were single digits. Because eMudhra says it has issued more than 60 million certificates, anyone holding those keys could forge a valid HTTPS certificate for any site — so the entire chain had to be thrown out. Mozilla, Chrome and Apple rejected the certificates and eMudhra revoked them.
Here's the uncomfortable part: you never chose eMudhra, and you'll never audit a certificate authority's key hygiene. The padlock in your browser is a promise made on your behalf by companies you've never heard of — and the whole system only works while every one of them keeps a secret perfectly. When one of them uses 4 as that secret, 60 million promises break at once, and you find out after the fact. That's not a cryptography story. It's a dependence story: your identity and your traffic ride on trust you can't see, can't choose, and can't revoke yourself.
A researcher recovered 8 of eMudhra's CA private keys from public data in under a second — one was literally 4. With 60M+ certs issued, the whole chain became forgeable and had to be rejected.
Every HTTPS padlock trusts a certificate authority to guard a secret key. You didn't choose them and can't check them — and when one uses a single digit, your identity rode on it anyway.
Keep the intelligence — and the trust — on the device in the room. No third-party certificate chain between you and your data means no stranger's key to compromise.
Privacy and resilience are the same decision again. The less of your identity that depends on a chain of third parties keeping secrets you can't verify, the less of it collapses when one of them doesn't — and one of them never fails to, eventually.
On-device.
Aura runs the intelligence on the device in the room. There's no cloud login, no remote certificate authority vouching for who you are, no third-party key sitting between you and your own data. A CA that trusts the number 4 can't break what was never routed through it.
Know someone who should see this? Send it to them.