[tor-project] Anti-censorship team monthly report: June 2019
phw at torproject.org
Mon Jul 1 22:50:02 UTC 2019
Here's a summary of the anti-censorship team's progress in June:
* Blacklisted 53 bridges whose obfs4 port was unreachable. Most of
these bridges had no contact info. Some did, but the operators did
not respond to our emails.
* Tried to understand why BridgeDB responded to many requests with no
- Eventually, the problem seems to have fixed itself.
- We'll keep a close eye on the logs.
* After hearing back from Tor's research safety board, we implemented a
new feature that lets BridgeDB export statistics:
The feature is currently under review.
* Removed support for Yahoo email accounts:
* Published a blog post about BridgeDB's new 0.7.1 release:
* We released a prototype for snowflake's webextension! For Firefox,
you can get it here:
We're still working on getting it published in Chrome's web store.
By installing the addon, you turn your browser into a circumvention
proxy for censored users.
* Working on integrating pion/webrtc to ease builds and reduce
* We wrapped up a ticket to collect statistics on snowflake's broker:
* Brainstormed mechanism for snowflake update versioning:
* Implemented a patch to reorder PT/proxy phases:
The patch is currently under review.
* Brainstormed ideas for obfs4's successor:
- We decided to first study the "long tail" of network traffic because
it will allow us to make better design decisions:
* We made some progress on improving our PT spec:
- For now, we have been collecting a list of issues with the v1 spec.
* We made some progress with loading shared libraries for PTs into the
Tor executable (on Linux for now).
* Deployed <https://bridges.torproject.org/scan/>. The service allows
obfs4 operators to test the reachability of their obfs4 port -- at
least until we are done with the following ticket:
* We wrapped up our "does the GFW block obfs4?" ticket:
The answer is: no.
* Published a blog post that introduces our anti-censorship team and our
Sponsor 19 report:
* Asked tor-relays@ to set up more obfs4 bridges:
* Worked with a handful operators whose obfs4 bridges were broken.
Several operators believed that only a bridge's OR port must be
externally reachable. Others forgot to configure port forwarding for
their obfs4 port.
More information about the tor-project