Your Windows Trust List Is a Network Dependency, and eMudhra Just Proved It
A while back, somebody generated eight P-384 private keys for eMudhra intermediate certificate authorities, and all eight came out with values smaller than 256. One of them was, as far as anyone can tell, the number 4. A researcher going by Wayne spotted the problem on October 17 while scanning publicly available certificate data; another, Flüpke, published a recovered key — the private key behind eMudhra's "EM OV TLS CA - G3C" certificate, value 4 — on GitHub as a demonstration. Mozilla's incident report puts the recovery cost at testing 256 possible numbers. That is not a cryptanalytic breakthrough. That is a for-loop an intern could write before lunch, pointed at the layer everyone builds TLS on top of. Because the keys were real and the certificate authorities sat in every mainstream trust store, anything signed with them would look legitimate to a browser. eMudhra held six TLS keys and two code-signing keys, so the risk splits in two directions: impersonate a web...