#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 gk): Replying to [comment:3 anarcat]: > the more i look at the list of bridges, the less happy i am. :) i was able to extract a list of host:port things with the atrocious: > > {{{ > curl -sSL 'https://gitweb.torproject.org/builders/tor-browser- build.git/plain/projects/tor-browser/Bundle- Data/PTConfigs/bridge_prefs.js' | sed -n '/default_bridge\.obfs/{s/.*obfs. //;s/ .*$//;p}' > }}} > > ... but that's pretty nasty. ideally, we'd have a plain-text file listing each host, one per line, without anything else. then we could do a stronger regex that would sanitize the output for inclusion in the prometheus server. is there another, simpler data format, canonical source for this? 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. So, I'd suggest to make sure that one is always kept up-to-date (not sure how the .csv file is generated on the OONI side, but hopefully in a scriptable way) and then both OONI and the solution for this bug could use that one as canonical source. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/30006#comment:5> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs