You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the client sends a long message to the websocket, the server crashes because Socket.Web.accept! (or even the underlying library) raises an exception. Thus, it is trivial for a malicious client to kill the server, making the game a lot less fun, but as @vhf found out, even a legit client can send such long message if, for instance, the browser has a cookie for the server url (e.g. localhost).
Ideally, we should take care that:
The client does not send irrelevant data through the websocket
If the client sends a long message to the websocket, the server crashes because
Socket.Web.accept!
(or even the underlying library) raises an exception. Thus, it is trivial for a malicious client to kill the server, making the game a lot less fun, but as @vhf found out, even a legit client can send such long message if, for instance, the browser has a cookie for the server url (e.g. localhost).Ideally, we should take care that:
The text was updated successfully, but these errors were encountered: