Anti-censorship team report: September 2020

Anti-censorship team report: September 2020

Anti-censorship team report: September 2020 Anti-censorship team report: September 2020 png base64 iVBORw0KGgoAAAANSUhEUgAAAAEAAAABAQMAAAAl21bKAAAAA1BMVEUAAP KeNJXAAAAAXRSTlMAQObYZgAAAAlwSFlzAAAOxAAADsQBlSsOGwAAAApJREFUCNdjYAAAAAIAAeIhvDMAAAAASUVORK5CYII

Philipp Winter
October 12, 2020

Tor’s anti-censorship team writes monthly reports to keep the world updated on its progress. This blog post summarizes the anti-censorship work we got done in September 2020. Let us know if you have any questions or feedback!


  • Merged a contribution from Peter Gerber to consider more IP address ranges local, for the purpose of stripping from SDP offers sent to the broker.


  • Built an HTTP streaming API between rdsys’s backend and its distributors that allows distributors to receive resource updates (e.g. a bridge changing its IP address) in real-time.

  • Implemented a registration API that allows standalone-proxies (i.e. without a corresponding Tor bridge) to register themselves:

  • Added lots of unit tests. Rdsys’s domain logic is 72.1% tested.

  • Experimented with reCAPTCHA support in rdsys. We could port BridgeDB’s HTTPS distributor to rdsys and replace our Gimp-generated CAPTCHAs with Google’s reCAPTCHA. To prevent exposing our users to Google, we would have to set up a reverse proxy, so Google only gets to see our machine’s IP address. This is possible but messy to build.

  • Started brainstorming Salmon’s user interface; in particular how we can best integrate it in Tor Browser:

  • Started writing up rdsys’s design and architecture. The goal is to eventually publish a technical blog post that discusses how we built rdsys.




Leave a Reply

Your email address will not be published. Required fields are marked *

Related Posts