News for hackers. Stuff that matters.
Re:OpenSSL Security Advisory by 0x0 on Thursday December 03, 2015 @04:15PM (#10672694)
Can this bug cause invalid or easily breakable private keys?
Re:OpenSSL Security Advisory by ecesena on Thursday December 03, 2015 @08:40PM (#10674069)
Not private key in public-key schemes (RSA, DH), because these are generally random integer and BN_mod_exp is not used in private key generation -- but it's used in public key generation so the result could be an invalid key pair.

In addition, I think it could produce a wrong symmetric key, as a result of a bad computation e.g. in the Diffie-Hellman protocol. So you could have insecure symmetric (e.g., AES) keys.

Re:OpenSSL Security Advisory by cperciva on Thursday December 03, 2015 @04:22PM (#10672739)
I certainly wouldn't be surprised.
Re:OpenSSL Security Advisory by tptacek on Thursday December 03, 2015 @04:56PM (#10672990)
I would be. How un-surprised would you be? Enough to bet?
Re:OpenSSL Security Advisory by cperciva on Thursday December 03, 2015 @05:38PM (#10673262)
Not without looking at the code first. But the first thing which comes to mind is accidentally generating RSA primes which aren't prime because the broken multiplication makes a SPSP test accidentally pass.

Granted, finding a concrete example would probably be very difficult, considering that replacing modexp by rand() is only going to pass N as a suspected prime with probability 1/N; but the question was can it, not will anyone ever find an example.