News for hackers. Stuff that matters.
Re:Google disables compression for OpenSSL in Chrome - SSL e... by anonymous on Wednesday September 12, 2012 @03:17PM (#4512523)
So, to summarize for the laypeople, if the user has Javascript and/or cookies disabled, this exploit will not work?
Re:Google disables compression for OpenSSL in Chrome - SSL e... by Daniel_Newby on Wednesday September 12, 2012 @04:00PM (#4512815)
Hidden <iframe> elements would probably work just as well.

It might even work with JacaScript turned. Have a page with nested iframes. Serve each one from a different IP address and have the server not answer right away. The server answers with the first iframe having a chosen URL while Eve snoops the wire. Eve tells the server which URL to use for the next iframe body that it sends. Repeat until the cookie is deduced. The server can use a nested tree of iframes to avoid having a bazillion iframes in the top level document.

Re:Google disables compression for OpenSSL in Chrome - SSL e... by fakjshflaskjhf on Wednesday September 12, 2012 @04:30PM (#4513025)
Javascript just makes the attack faster, but it can be accomplished with raw html. Cookies are required though; it's what you are after when using this attack.