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. }

  • ramble81@lemmy.zip
    link
    fedilink
    English
    arrow-up
    2
    ·
    8 hours ago

    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.

      • ramble81@lemmy.zip
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 hour ago

        Yes, be in is why having 8 of them total in the 2 digit range (I.e only using up to 6 bits of 384-bits) just screams incompetence of a hand generated key.

    • Kraiden@piefed.social
      link
      fedilink
      English
      arrow-up
      3
      ·
      4 hours ago

      Ye, I’d struggle to believe ONE key getting generated like that, but 8 points to pure incompetence