We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
As a player I want the app to be secure and no one can impersonate me to disconnect me.
There is a security issue with player ids. They are provided by the backend and remembered and used by the client.
The client could use the browser console to change the id to impersonate other players, for example to disconnect them from a room.
The playerid is stored in the connection.
The id stored in connection is used in the backend for any operation needing a playerid.
The playerids are inserted into the method data in a before hook.
SHOULD: probably the room name should be managed at the same time.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
As a player I want the app to be secure and no one can impersonate me to disconnect me.
Background
There is a security issue with player ids. They are provided by the backend and remembered and used by the client.
The client could use the browser console to change the id to impersonate other players, for example to disconnect them from a room.
Acceptance criteria
The playerid is stored in the connection.
The id stored in connection is used in the backend for any operation needing a playerid.
The playerids are inserted into the method data in a before hook.
SHOULD: probably the room name should be managed at the same time.
The text was updated successfully, but these errors were encountered: