[tor-bugs] #25405 [Applications/Tor Launcher]: cannot use Moat if a meek bridge is configured

Mon Mar 26 21:27:05 UTC 2018

#25405: cannot use Moat if a meek bridge is configured
---------------------------------------+--------------------------
 Reporter:  mcs                        |          Owner:  brade
     Type:  defect                     |         Status:  new
 Priority:  Medium                     |      Milestone:
Component:  Applications/Tor Launcher  |        Version:
 Severity:  Normal                     |     Resolution:
 Keywords:  TorBrowser201803R          |  Actual Points:
Parent ID:                             |         Points:
 Reviewer:                             |        Sponsor:  Sponsor4
---------------------------------------+--------------------------
Changes (by mcs):

 * cc: dcf (added)
 * keywords:   => TorBrowser201803R

Comment:

 Kathy and I created a fix that implements option (a) "use a separate
 browser profile for the meek http helper browser when it is used for
 Moat." It requires three patches:
 1. A small enhancement to `meek-client-torbrowser` to allow use of a
 different http helper browser profile:
 https://gitweb.torproject.org/user/brade/meek.git/commit/?h=bug25405-01&id=6a70f67dd895d1b9124a08dac06e0cba1b7a30bb
 2. Changes to Tor Launcher to pass the correct path for a new moat-
 specific profile: https://gitweb.torproject.org/user/brade/tor-
 launcher.git/commit/?h=bug25405-01&id=2861a871b6d47d257b5ede41bf754144bfd34182
 3. Changes to tor-browser-build to include the moat profile on Windows and
 Linux (the meek-client-torbrowser code already knows to create it from a
 template on macOS). Since we don't yet have a `tor-browser-build` repo
 (one was requested in #25267), I added this patch as an attachment
 (0001-Bug-25405-cannot-use-Moat-if-a-meek-bridge-is-config.patch).

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