Astonishingly, the private keys were 4, 56, 66, 115, 155, 156, 230, 237.

exploiting compromised certificates requires an active adversary-in-the-middle attack, meaning the attacker must act as a proxy between two TLS parties and receive encrypted traffic, decrypt it, reencrypt it, and send it to the other party. Such capabilities, in some cases, are usually limited to only the most well-resourced attackers. People with control of a local network—at a coffee shop, university, or other organization—face much less of a challenge.

https://emudhra.we-have-a-problem.com/

Xkcd 221: int getRandomNumber() { return 4; // chosen by fair dice roll. guaranteed to be random. }

you are viewing a single comment's thread
view the rest of the comments
[–] 265 points 3 days ago* (19 children)

I think that this isn't really getting the right attention, about what a massive WTF situation this is...

its a 384 bit certificate and this is the private key

00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:
00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:
00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:
00:00:04

that is just fucking NUTS

  • source
  • hideshow 19 child comments
  • [–] 10 points 2 days ago* (5 children)
    4E:65:76:65:72:20:67:6F:6E:6E:61:20:67:69:76:
    65:20:79:6F:75:20:75:70:20:4E:65:76:65:72:20:
    67:6F:6E:6E:61:20:6C:65:74:20:79:6F:75:20:64:
    6F:77:6E
    

    is much more secure.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 10 points 2 days ago (4 children)

    LOL, People are never gonna give this up.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 7 points 2 days ago (3 children)

    I mean, yes, it’s entirely possible and within the realm of probability of getting that as a key. But realistically it’s very, very, fucking unlikely.

  • source
  • parent
  • hideshow 3 child comments