Re: [tor-bugs] #20250 [Obfuscation/meek]: macOS 10.12 TorBrowser meek pluggable transport issues

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

#20250: macOS 10.12 TorBrowser meek pluggable transport issues
-------------------------------------------------+-------------------------
 Reporter:  tordevSZ0                            |          Owner:  dcf
     Type:  defect                               |         Status:  new
 Priority:  High                                 |      Milestone:
Component:  Obfuscation/meek                     |        Version:  Tor:
                                                 |  unspecified
 Severity:  Major                                |     Resolution:
 Keywords:  meek, macOS, TorBrowser, 10.12,      |  Actual Points:
  sierra, macOS                                  |
Parent ID:                                       |         Points:
 Reviewer:                                       |        Sponsor:
-------------------------------------------------+-------------------------

Comment (by tordevSZ0):

 Replying to [comment:16 dcf]:
 > Replying to [comment:12 tordevSZ0]:
 > > This may be an error on my part, but when using a fresh install of
 6.5a3 on 10.12, the initial Tor Network Settings window opens, but fails
 to connect to the tor control port, even with
 extensions.torlauncher.control_port_use_socket pref set to false in
 prefs.js.
 >
 > I think I know why setting this pref appeared to have no effect. You
 have to edit the prefs.js file found under `~/Library/Application Support
 /TorBrowser-Data`, not the one in the installation directory under
 `/Applications`. The one under `/Applications` doesn't have an effect once
 it is copied to `~/Library/Application Support/TorBrowser-Data`.

 Placing TorBrowser.app (v6.5a3) on the Desktop solved the control port
 issue, but connecting with meek had the same issue as 6.0.5. The first
 time, the connection UI completed, traffic went through to the meek server
 for around a minute and a half (longer than normal, yes, but I think this
 may have been a coincidence (seen this long on 6.0.5 also). I tested a few
 more times and it behaved as with 6.0.5, lasting very short period and
 stopping abruptly. Logs were also essentially the same as I have already
 posted.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/20250#comment:18>
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