Congratulations to your first post that made me open a private window prior to googling.
Torbjörn Björkman
@torbjornbjorkman.eurosky.social
790 followers 521 following 6.7K posts
He/him. Swede living in Finland. Physics lecturer, violinist, genealogist, generalist, in that order, perhaps. Posting will continue until morale improves.
![Worked for 53s >
Yes—the private key really is the integer 4. I independently checked the published certificate for EM OV TLS CA – G3C: deriving a P-384 public key from private scalar 4 produces exactly the public key in that certificate. [GitHub]
I checked the other seven too. All eight private keys fit in a single byte:
4, 56, 66, 115, 155, 156, 230, 237
They should have been sampled securely from an enormous, roughly 384-bit range. These can instead be recovered by trying the 255 nonzero byte values and comparing the resulting public keys with the certificates. The published proof of concept does precisely that.
[Fluepke/emudrahahahahaha: Private Keys · GitHub +1]
These are CA signing keys: possession lets someone issue fraudulent certificates that clients still trusting those chains could accept. Mozilla explicitly confirms that consequence. [blog.mozilla.org]](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:5hhbgkktcpofpw4ovz6kjjau/bafkreih4y6apxnh2gjuws446gkry33eg7sxjuqlxomwusahgidquitncnm)
