@ApacheArrow / Databases / Compilers. (past @SDFLabs, VoDa, @Spotify). Rust/C++/TLA⁺🇧🇷 → 🇸🇪 → 🌎

Joined June 2008
You have to exorcise your programs from bundled certificates!
PSA: If you use Node or Bun, please upgrade even if you’ve enabled --use-system-ca! That flag unions the system roots with the the bundled roots, so older versions will continue to accept the eMudhra cert even if your OS removes it.
5
437
If you could store one private key per proton in the universe (you can't), you would only be able to store 2^263 keys (log_2(Eddington Number)~=263). A truly random 384-bit key has never been written down or appeared anywhere in the universe. But sure, pick the number 4.
5
372
Very pretentious from eMudhra’s part to say they *chose* to leave the business. The business is trust and they can’t be trusted. There is no business for them anymore.
I suspect the real reason eMudhra is exiting the SSL business is Google indicated it is most likely going to drop eMudhra from being trusted by Chrome AT ALL, after observing inexplicable incompetence in how they mis-generated their private key for the CA certificate.
11
86
1
1,419
9,703
This CA debacle reminds me of Mozilla simply refusing to take SERPRO (a technical Brazilian agency) seriously in its attempts to add itself as a root CA.
1
11
592
I'm adding a `cargo deny` rule that prevents dependency on the bundled CA certificate store in Rust projects. Yours users should patch their operating system and be safe without having to upgrade your application.
1
1
12
497