Get default bridges checked for reachability by OONI
Talk to OONI about getting our default bridges scanned. This should be done for new PTs once they are deployed.
Activity
Trac:
Parent Ticket: #31274 (moved)Tor Browser's default bridges are already tested by OONI: https://github.com/citizenlab/test-lists/blob/master/lists/services/tor/bridges.csv
But the lists might be out of date.
To elaborate on teor's comment: I had a chat with our friends over at OONI and was told that the bridge reachability test already takes care of this. The relevant list is here, but only used by OONI probes up to version 2.3: https://github.com/OpenObservatory/ooni-resources/blob/master/bridge_reachability/tor-bridges-ip-port.csv
Arturo mentioned that this ticket discusses the future for mobile and 3.x probes.
We should be able to see the test results in OONI's explorer. One can filter by test name. All "bridge reachability" tests I've seen are quite old, though -- from 2014 or 2015. I'll try to find out what's going on here.
FYI, the Tor Browser hacking guide has a small section that discusses the process of adding new default bridges. It includes having the bridges added to OONI's test list: https://trac.torproject.org/projects/tor/wiki/doc/TorBrowser/Hacking#AddingNewDefaultBridges
Replying to phw:
We should be able to see the test results in OONI's explorer. One can filter by test name. All "bridge reachability" tests I've seen are quite old, though -- from 2014 or 2015. I'll try to find out what's going on here.
"Bridge reachability" is a different test, and as you found hardly run. The bridges are actually tested in the "TCP Connect" test. E.g. https://explorer.ooni.torproject.org/measurement/20190107T070320Z_AS4134_d5QVa5d13jHeRFwOVn63qJmX0CXVymh47lFwR27iq8Y2hfqxr3?input=obfs4%20154.35.22.13:6041
It's only a TCP connect, and not a full bootstrap, but it is run pretty frequently. https://api.ooni.io/api/v1/files?since=2019-04-01&test_name=tcp_connect finds 454 reports for me currently.
I did some early analysis of the TCP connect tests here: https://lists.torproject.org/pipermail/ooni-dev/2016-December/000482.html
More recently Briar has been doing analysis on them. https://code.briarproject.org/briar/briar/issues/1266 https://code.briarproject.org/briar/tor-circumvention-analytics/ https://lists.torproject.org/pipermail/tor-dev/2019-February/013708.html
-
Replying to dcf:
Replying to phw:
We should be able to see the test results in OONI's explorer. One can filter by test name. All "bridge reachability" tests I've seen are quite old, though -- from 2014 or 2015. I'll try to find out what's going on here.
"Bridge reachability" is a different test, and as you found hardly run. The bridges are actually tested in the "TCP Connect" test. E.g. https://explorer.ooni.torproject.org/measurement/20190107T070320Z_AS4134_d5QVa5d13jHeRFwOVn63qJmX0CXVymh47lFwR27iq8Y2hfqxr3?input=obfs4%20154.35.22.13:6041
Perfect, thanks David!
-
Since OONI is already doing a great job at scanning our bridges, the next (and remaining?) question related to this ticket is how we can make sure that OONI's list of default bridges is up-to-date. There's some discussion on this over at https://trac.torproject.org/projects/tor/ticket/30006#comment:7.
-
Replying to phw:
Since OONI is already doing a great job at scanning our bridges, the next (and remaining?) question related to this ticket is how we can make sure that OONI's list of default bridges is up-to-date. There's some discussion on this over at https://trac.torproject.org/projects/tor/ticket/30006#comment:7.
We agreed that the anti-censorship team will create a pull request for OONI's tor_targets.json each time the set of default bridges changes. I tried to make this clear on our default bridge wiki page. We can close this ticket now.
Trac:
Resolution: N/A to fixed
Status: new to closed -
Trac:
Parent: N/A to #31274 (moved)
Keywords: N/A deleted, s30-o21a1 added mentioned in issue #29279 (moved)
mentioned in issue #30006 (moved)
mentioned in issue #31274 (moved)
