Re:Apple's SSL/TLS bug
by hueving on Saturday February 22, 2014 @02:50PM
(#7283312)
How is what I said not true? If the same thing as the Deb prng bug happened in a closed source system, it could sit for a couple of years exposing thousands/millions of systems and then be patched quietly to avoid embarrassment, leaving everyone vulnerable.
[ Parent
| on HN ]
FYI -- the source code here is public. Didn't help :D
It helped us realize how easy it would be to test for this, and that Apple isn't.
Re:Apple's SSL/TLS bug
by lawnchair_larry on Saturday February 22, 2014 @08:09PM
(#7284494)
I question your code comprehension. This is not easy to test for at all, and Chrome doesn't do it either. Do you understand how to exploit this issue?
Static analysis would have caught this immediately. It caused unreachable code that the compiler even recognized and optimized away.
You're saying Google Chrome doesn't test that an ephemeral key is actually signed by the cert's private key? If that's the case, that's completely unacceptable because it's the whole point of the protocol.