[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                       |  Actual Points:
Parent ID:                                       |         Points:
 Reviewer:                                       |        Sponsor:
-------------------------------------------------+-------------------------

Comment (by boklm):

 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?
 >
 > What do you think? Should we rather keep OONI's list up-to-date? Mostly,
 I want a single source of truth that includes contact information of the
 operator.

 If there is a git repository containing this CSV file, then maybe we could
 use it in tor-browser-build to generate the .js file containing the prefs
 for Tor Browser.

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