[tor-bugs] #15159 [Ooni]: Add meek support to ooni-probe

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#15159: Add meek support to ooni-probe
-------------------------+-------------------------
 Reporter:  dcf          |          Owner:  hellais
     Type:  enhancement  |         Status:  new
 Priority:  normal       |      Milestone:
Component:  Ooni         |        Version:
 Keywords:               |  Actual Points:
Parent ID:               |         Points:
-------------------------+-------------------------
 It would be nice if ooni-probe could test current and potential front
 domains used by meek. This could be as simple as doing an HTTPS fetch and
 seeing if it completes successfully, with the expected certificate. The
 idea is, that the most likely way for a censor to block meek is to block
 the front domain somehow.

 The current list of fronts is:
 https://gitweb.torproject.org/builders/tor-browser-bundle.git/tree/Bundle-
 Data/PTConfigs/bridge_prefs.js
  * www.google.com
  * a0.awsstatic.com
  * ajax.aspnetcdn.com
 Then, it would be good to test some potential future domain names, so we
 would know which ones are reachable in case we need to switch (like this
 mailing list post, [https://lists.torproject.org/pipermail/tor-
 talk/2015-January/036410.html What to do if meek gets blocked]). For
 example,
  * www.gmail.com
  * www.google.com.mx
  * www.orkut.com
  * ssl.google-analytics.com
  * www.doubleclick.net
  * officeimg.vo.msecnd.net
 It might be fun to test also the non-fronted domains, just in case a
 censor tried doing that:
  * meek-reflect.appspot.com
  * d2zfqthxsdq309.cloudfront.net
  * az668014.vo.msecnd.net

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/15159>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs