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

Tor and rate limiting #1015

Closed
Changaco opened this issue Mar 17, 2018 · 1 comment · Fixed by #1092
Closed

Tor and rate limiting #1015

Changaco opened this issue Mar 17, 2018 · 1 comment · Fixed by #1092
Assignees
Labels
defense protecting ourselves, our users and innocent third-parties good first issue suitable for new contributors

Comments

@Changaco
Copy link
Member

For rate limiting purposes we should treat Tor exit nodes as a single origin network. Context: liberapay/salon#192 (comment).

If I remember correctly Cloudflare tags requests coming from Tor with a specific "country" code, so we should be able to use that.

@Changaco Changaco added good first issue suitable for new contributors defense protecting ourselves, our users and innocent third-parties labels Mar 17, 2018
@EdOverflow
Copy link
Member

If I remember correctly Cloudflare tags requests coming from Tor with a specific "country" code, so we should be able to use that.

Yep, that is the case.

Since late February 2016, Cloudflare treats Tor exit nodes as a "country" of their own. There's no geography associated with these IPs, but this approach lets Cloudflare customers override the default Cloudflare threat score to define the experience for their Tor visitors. [1]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
defense protecting ourselves, our users and innocent third-parties good first issue suitable for new contributors
Development

Successfully merging a pull request may close this issue.

2 participants