[tor-bugs] #32740 [Circumvention/BridgeDB]: Implement a feedback loop between BridgeDB and OONI

[Tor Bug Tracker & Wiki]

#32740: Implement a feedback loop between BridgeDB and OONI
-------------------------------------------------+-------------------------
 Reporter:  phw                                  |          Owner:  (none)
     Type:  project                              |         Status:  new
 Priority:  Medium                               |      Milestone:
Component:  Circumvention/BridgeDB               |        Version:
 Severity:  Normal                               |     Resolution:
 Keywords:  s30-o23a2, anti-censorship-roadmap-  |  Actual Points:
  2020Q1                                         |
Parent ID:  #31280                               |         Points:  10
 Reviewer:                                       |        Sponsor:
                                                 |  Sponsor30-must
-------------------------------------------------+-------------------------

Comment (by phw):

 We discussed this task at today's [http://meetbot.debian.net/tor-
 meeting/2020/tor-meeting.2020-02-11-18.00.html sponsor 30 sync meeting].
 Here's a summary:

 * OONI currently tests our
 [https://trac.torproject.org/projects/tor/wiki/doc/TorBrowser/DefaultBridges
 default bridges] and directory authorities. The test targets can however
 be changed dynamically on the server side.

 * OONI recently made it possible for their Tor test to
 [https://github.com/ooni/orchestra/issues/82 take a test target]. There's
 [https://github.com/ooni/spec/blob/master/nettests/ts-023-tor.md a spec]
 for this. The [https://github.com/ooni/sysadmin/blob/master/ansible/roles
 /probe-services/templates/tor_targets.json list of targets] can even
 include private bridges, which wouldn't end up in a public git repository
 and OONI can also redact a bridge's IP address (and fingerprint?) from the
 test results. It's also possible to retrieve private bridges at run time
 using OONI Probe Services. (The
 [https://github.com/ooni/orchestra/blob/master/orchestrate/orchestrate/handler/test_lists.go#L209
 current code] for this is very basic.)

 * Arturo mentioned that the following query fetches all Tor test results:
 https://api.ooni.io/api/v1/measurements?test_name=tor

 * ...for casual browsing, the Explorer may be more useful:
 https://explorer.ooni.org/search?test_name=tor&until=2020-02-12 To get an
 idea of what a test result looks like, take a look at
 [https://explorer.ooni.org/measurement/20200207T050741Z_AS56041_vF6LpJlK1box3R7IR3YWXDv4rFKXjfgmjSERc22nGpH5s58SZM
 this result from China] and
 [https://explorer.ooni.org/measurement/20200206T184551Z_AS197207_SjXBx35FSWpdi3W0GzpbdN9dBL8VxRwIKJeNUBUURdXP1iRJVx
 this result from Iran].

 * To get test results from OONI back to to BridgeDB, Arturo suggested that
 we shouldn't use OONI's API because it's not designed for batch use. Over
 at [https://trac.torproject.org/projects/tor/ticket/32126#comment:4
 #32126], Arturo provided some more details. It's okay however to use the
 API for testing.

 In the next step, the anti-censorship team should think about how OONI
 should partition the test targets it hands out to probes. What bridges
 should be tested? And how often? By what probes?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/32740#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online