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

Investigate how to reject connections (abuse) #64

Open
willyaranda opened this issue Sep 18, 2012 · 3 comments
Open

Investigate how to reject connections (abuse) #64

willyaranda opened this issue Sep 18, 2012 · 3 comments

Comments

@willyaranda
Copy link
Contributor

The server::onWSRequest::originIsAllowed() should be intelligent enough to reject abuse (in websocket connections)

@frsela
Copy link

frsela commented Sep 20, 2012

First we should define "what is abuse" :)

1.- Too many connections from the same IP
2.- Check a blacklist?

N.- ... Discussion open ...

But don't forget that to many abuse controls can be managed by the firewalls in front of our server so don't re-invent the wheel ;)

@willyaranda
Copy link
Contributor Author

Agree. Let's check with Antonio about what he thinks.

@frsela
Copy link

frsela commented Oct 24, 2012

Also: Too many connections from different IPs to the same App (same Public Key) - Possible Private key leak?

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

No branches or pull requests

2 participants