Skip to content

Comment on An Introduction to Web Sockets

Comments

I can't watch the slides, but I wonder if they spend any time discussing how WebSockets don't offer any client security beyond raw TCP sockets.

Why would WebSockets offer any client security beyond raw TCP sockets?

It was one of the original promises of WS and the reason that browsers offer it to client-side JS.

There are some people building on top of WebSockets with an eye towards security. Check out http://pusher.com/ for example, they designed system to account for 100% untrusted client.

I agree, security in Web Socket must be robust/comprehensive in both ends. This post says so too: http://blog.kotowicz.net/2011/03/html5-websockets-security-n.... Thanks!

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.