[tor-bugs] #30006 [Applications/Quality Assurance and Testing]: Monitor "aliveness" of default bridges in Tor Browser

[Tor Bug Tracker & Wiki]

#30006: Monitor "aliveness" of default bridges in Tor Browser
-------------------------------------------------+-------------------------
 Reporter:  phw                                  |          Owner:  phw
     Type:  defect                               |         Status:
                                                 |  assigned
 Priority:  Medium                               |      Milestone:
Component:  Applications/Quality Assurance and   |        Version:
  Testing                                        |
 Severity:  Normal                               |     Resolution:
 Keywords:  default bridge tbb-bridges           |  Actual Points:
Parent ID:                                       |         Points:
 Reviewer:                                       |        Sponsor:
-------------------------------------------------+-------------------------
Changes (by dcf):

 * keywords:  default bridge => default bridge tbb-bridges


Comment:

 Replying to [comment:5 gk]:
 > I guess .csv would work for you? See over at #29275 the OONI folks have
 such a thing it seems (even though it might be outdated):
 ​https://github.com/citizenlab/test-
 lists/blob/master/lists/services/tor/bridges.csv.

 That list is not maintained. An up-to-date one (used for the tcp_connect
 test, and containing more than just default bridges) is at
 https://github.com/OpenObservatory/ooni-
 resources/blob/master/bridge_reachability/tor-bridges-ip-port.csv. However
 that, too, is probably going to change in the future as OONI deploys its
 orchestrator.

 Replying to [comment:7 phw]:
 > I'm considering creating a git repository, maintained by the anti-
 censorship team, that contains an up-to-date CSV file (which would be
 simple for anarcat to fetch and parse) for our default bridges with the
 following information:
 >
 > * Fingerprint
 > * IP address and port(s)
 > * Email address (or other contact info) of owner
 > * What protocols the bridge speaks (e.g., vanilla Tor, obfs3, ...)
 > * Date of when the bridge was set up
 > * ...anything else?

 You may want a list separate from the OONI one, because the OONI one
 doesn't have all the information you want.

 There's some past data (2015–2018) https://repo.eecs.berkeley.edu/git-
 anon/users/fifield/proxy-probe.git, see the files proxy-probe.csv and
 significant_dates.txt.

 I try to make sure that every ticket about default bridges is tagged with
 the
 [https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=closed&status=merge_ready&status=needs_information&status=needs_review&status=needs_revision&status=new&status=reopened&keywords
 =~tbb-bridges&order=priority tbb-bridges] tag. You can look over those
 tickets to get information about timing and who the operator is.

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