Skip to content
New issue

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

Broadcast authorisation. #1

Open
3rd-Eden opened this issue Jun 17, 2013 · 1 comment
Open

Broadcast authorisation. #1

3rd-Eden opened this issue Jun 17, 2013 · 1 comment

Comments

@3rd-Eden
Copy link
Member

Broadcasting is done through HTTP PUT messages against the /stream/broadcast/ route. There's some basic data validation done to ensure that don't receive any broken information but these routes are still approachable from the outside.

We should add some basic authentication to these routes to prevent hacker from broadcasting messages to all our users. The easiest way to do this would be generate a random username + password when the server is generated and to store these details with every host + socket.io inside of redis. If we probably sandbox and firewall redis, it should be good enough.

@3rd-Eden
Copy link
Member Author

Something like https://github.com/joyent/node-http-signature might be suitable as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant