News for hackers. Stuff that matters.
Re:It's not WebSockets it's your broken proxy by sedachv on Thursday December 09, 2010 @02:13PM (#1988689)
Everything I hear about WebSockets (things like http://www.ietf.org/mail-archive/web/hybi/current/msg02149.h... and http://blogs.webtide.com/gregw/entry/how_to_improve_websocke... and now this) makes me convinced the current draft standard is unworkable.
Re:It's not WebSockets it's your broken proxy by m_eiman on Thursday December 09, 2010 @12:26PM (#1988225)
It doesn't really matter, since it's easier to fix four browsers under active development than it is to fix a myriad of old firewalls and proxies.
Re:It's not WebSockets it's your broken proxy by luigi on Thursday December 09, 2010 @10:18AM (#1987716)
I'd expect to see exploits using Flash sockets as the attack vector before seeing attacks using native WebSockets.
Re:It's not WebSockets it's your broken proxy by trotsky on Thursday December 09, 2010 @10:51AM (#1987851)
A vast majority of the installations with these types of vulnerable firewalls don't allow outbound traffic on port 843 which flash needs to be able to communicate on to get raw socket communication permission.
Re:It's not WebSockets it's your broken proxy by mloughran on Thursday December 09, 2010 @12:22PM (#1988201)
Where are you getting the 20-30x number from? There is no demonstrated WebSockets attack in the "Transparent Proxies: Threat or Menace?" paper.
Re:It's not WebSockets it's your broken proxy by trotsky on Thursday December 09, 2010 @12:39PM (#1988275)
You're right, I reread the paper and I'm not even sure what I was thinking... I was going off of memory. Thanks, and corrected.