commit d8cc048fad46ea99e5753740d3a4dbabd763ce4c Author: Pili Guerra <pili@piliguerra.com> Date: Mon Mar 2 17:38:45 2020 +0100 Add some tips for students on how to contribute --- content/gsoc/cloudflare-captcha-monitoring/contents.lr | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/content/gsoc/cloudflare-captcha-monitoring/contents.lr b/content/gsoc/cloudflare-captcha-monitoring/contents.lr index e6ba0d5..fab93fb 100644 --- a/content/gsoc/cloudflare-captcha-monitoring/contents.lr +++ b/content/gsoc/cloudflare-captcha-monitoring/contents.lr @@ -35,7 +35,15 @@ One catch is that Cloudflare currently gives alt-svc headers in response to fetc Once we get the infrastructure set up, we would be smart to run a second one which is just wget or curl or lynx or something, i.e. which doesn't behave like Tor Browser, in order to be able to track the difference between how Cloudflare responds to Tor Browser vs other browsers. -I imagine that Cloudflare should be internally tracking how they're handling Tor requests, but having a public tracker (a) gives the data to everybody, and (b) helps Cloudflare have a second opinion in case their internal data diverges from the public version. +# Getting Started + +As this is a new project, in order to demonstrate your skills and familiarise yourself with this project you may want to: + +1. Set up the required infrastructure for this project e.g by setting up a very simple static webpage to be fronted by Cloudflare. +2. Familiarise yourself and start experimenting with various web clients to fetch pages via Tor, bearing in mind you may need to adapt them to your needs if they are lacking the required functionality. +3. Read the comments in ticket [#33010](https://trac.torproject.org/projects/tor/ticket/33010) for more ideas + +# Resources The Berkeley ICSI group did research that included this sort of check: ​https://www.freehaven.net/anonbib/#differential-ndss2016