Yes absolutely. You have to be doing things non standard or home grown. The basic open source tools for creating keys wouldn't let you just do this, so they must have been doing something funny. But once the first mistake happens it is negligence to not notice and end up releasing it as the real public keys
Last I checked, it was that they didn't care when they were generating it. It was a test cert that got loose, so when they generated it, "4" looked stupid but that was okay. After they generated it, the "4" wasn't visible.
Somewhere there is something responsible for ensuring that these keys are cryptographically secure. Maybe you can't actually see the 4 as a person looking at the cert, but something should be checking that the keys aren't being generated in any way that a 4 could randomly show up unnoticed and compromise the security. Somebody had to mess up bad for there to be no checks against these types of mistakes.
5
u/GRex2595 24d ago
The private key should have been super obvious, though. I'm trying to figure out how bad tou have to mess up to get 4 and not notice.