The POODLE bites again

https://www.imperialviolet.org/2014/12/08/poodleagain.html

by deepblueocean • 12 years ago

94 16 12 years ago

imperialviolet.org

huxley• 12 years ago

Link didn't work for me, here is the Google Cache text version:

http://webcache.googleusercontent.com/search?q=cache:f01MHrX...

resonantcore• 12 years ago

We look forward to TLS 1.2 support being the norm. (And then, hopefully, the ratification and adoption of TLS 1.3)

A 50% adoption rate is excellent news. Still a long way to go, but that's worth toasting over.

yuhong4• 12 years ago

What is frustrating is how many such servers have TLS 1.3 intolerance (even PayPal), and often the same servers are also affected by this bug. I wonder what TLS implementation is this.

feld4• 12 years ago

TLS 1.3 isn't finished yet...

eyeareque• 12 years ago

Are there any more details than what this write up contains?

cryptbe• 12 years ago

POODLE worked not only against SSLv3, but also against any TLS implementations that check padding in SSLv3's style (e.g., just checking the last byte, and ignoring the rest of the padding). SSL accelerators from F5 and A10 were vulnerable. Thus, many of the world's largest sites were vulnerable.

tacoman• 12 years ago

"This seems like a good moment to reiterate that everything less than TLS 1.2 with an AEAD cipher suite is cryptographically broken."

So this means AES-GCM essentially?

colmmacc• 12 years ago

Well, almost. AES-GCM is also "Cryptographically Broken" if you take into account software implementations using table lookup schemes that are subject to cache timing attacks. But the fundamental AEAD support in TLS1.2 is a much better place to be overall - and GCM tags are much better than the MAC-then-Encrypt HMACs elsewhere in TLS. For practical purposes; AES-GCM is the "least worst", by a long way.

cesarb• 12 years ago

For the future, there's also the encrypt-then-MAC extension (https://tools.ietf.org/html/rfc7366, https://bugzilla.mozilla.org/show_bug.cgi?id=972145), and probably some variant of a ChaCha20+Poly1305 AEAD (https://tools.ietf.org/html/draft-agl-tls-chacha20poly1305-0..., https://bugzilla.mozilla.org/show_bug.cgi?id=917571, already on Chrome AFAIK).

For now, AES-GCM is the best alternative.

The POODLE bites again

Related Stories