It's not WebSockets it's your broken proxy (opens in new tab)

(blog.pusherapp.com)

43 pointsmaxthelion15y ago6 comments

6 comments

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.

m_eiman15y ago

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.

luigi15y ago

I'd expect to see exploits using Flash sockets as the attack vector before seeing attacks using native WebSockets.

trotsky15y ago

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.

mloughran15y ago

Where are you getting the 20-30x number from? There is no demonstrated WebSockets attack in the "Transparent Proxies: Threat or Menace?" paper.

1 more reply

j / k navigate · click thread line to collapse