Live data from Hacker News

RSA warns developers not to use RSA products

blog.cryptographyengineering.com

31–40 of 81 posts

Re: RSA warns developers not to use RSA products

#31
post #8

It irks me that many people are calling this a backdoor. It's not. It's a vulnerability. You have to exploit it to get in.

An intentionally introduced vulnerability can be considered a backdoor, even if it's not a matter of saying "open sesame" to open the so-called backdoor.

Yes. The magic, poorly-documented constants are the "public key" while the "private key" is known only to the construction's author.

Re: RSA warns developers not to use RSA products

#32

Hasn't tptacek posted "nothing to see here" regarding this issue on HN a half dozen times because "nobody uses it"? :)

At that point my personal conspiracy is suggesting that tptacek has become some form of alliance officer for hn outreach efforts.

Re: RSA warns developers not to use RSA products

#34
post #12
post #8

It irks me that many people are calling this a backdoor. It's not. It's a vulnerability. You have to exploit it to get in.

Serious question: what's the difference? I would have followed the definition for backdoor since it relies on particular secret information relating P and Q that the NSA might have—but where should one draw the line between backdoors and vulnerabilities? Intent?

Nerd's law: A commenter C declares that concepts X and Y are completely different. Because parent commenter P failed to make this point, P is intellectually inferior to C. Hence C > P for all X and Y.

Re: RSA warns developers not to use RSA products

#35
post #17

Earlier quoted context omitted.

It's a PRNG based on a trapdoor function where apparently the NSA has the key. With that key they can recover the RNG state from just a small amount of it. Thats a backdoor by most descriptions. This isn't just a bug.

Snowden obviously has that key as well.

Haha what? Not only is there no way of knowing that, but it's not even relevant.

Re: RSA warns developers not to use RSA products

#36
post #20
post #3

Earlier quoted context omitted.

Especially the part about KDFs being deliberately slow, and according to him that somehow implies that RNGs should also be slow. Whut? This guy is really a CTO?

"The length of time that Dual_EC_DRBG takes can be seen as a virtue: it also slows down an attacker trying to guess the seed." If a system's seed is weak, one attack is to try all likely seeds, run them through the PRNG to generate keys, and see if any of the keys work. A slow PRNG indeed slows down this process. For instance, it would have slowed down the attack on the Taiwan Cryptocards, which exploited patterns in…

That's a really poor idea. If you're concerned about guessing attacks on your RNG seed, the right response is to increase the size of your seed -- NOT to slow down the function. To put it another way, adding one bit to the seed length is equivalent to doubling the cost of the attack. In other words, a 1000x slowdown in the generator is the same as about 10 bits of additional seed material. Not worth it!

Re: RSA warns developers not to use RSA products

#37
post #8

It irks me that many people are calling this a backdoor. It's not. It's a vulnerability. You have to exploit it to get in.

It's a backdoor. The original paper describing the hole is (hopefully) entitled "On the Possibility of a Back Door in the NIST SP800-90 Dual Ec Prng"[0]. It's no longer a "possibility".

[0] http://rump2007.cr.yp.to/15-shumow.pdf

Re: RSA warns developers not to use RSA products

#40
post #20
post #3

Earlier quoted context omitted.

Especially the part about KDFs being deliberately slow, and according to him that somehow implies that RNGs should also be slow. Whut? This guy is really a CTO?

"The length of time that Dual_EC_DRBG takes can be seen as a virtue: it also slows down an attacker trying to guess the seed." If a system's seed is weak, one attack is to try all likely seeds, run them through the PRNG to generate keys, and see if any of the keys work. A slow PRNG indeed slows down this process. For instance, it would have slowed down the attack on the Taiwan Cryptocards, which exploited patterns in…

No, it wouldn't have slowed the attack on the Taiwan Cryptocards one bit. That and the related "Mining Your P's and Q's" research involved deriving the private keys from the public keys using bulk factorization.

They did not need to simulate the operation of the poorly-seeded PRNG that generated them.

Post reply on HN