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

[Tor Bug Tracker & Wiki]

#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 dcf):

 Replying to [comment:12 tordevSZ0]:
 > Replying to [comment:11 dcf]:
 > > Replying to [ticket:20250 tordevSZ0]:
 > > > Having issues using the meek pluggable transports on macOS 10.12
 installation with a fresh install of TorBrowser.
 > >
 > > Please try the alpha release 6.5a3. If it works for you, that means we
 have to use a newer version of Go to compile the next stable release.
 >
 > 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 monitor file accesses by applications and noticed that the
 TorBrowser.app, after creating and writing to the '~/Library/Application
 Support/TorBrowser-Data' directory as it should, then tries to write to
 the non-existent '~/Library/Application', and then times out trying to
 connect to tor.real with the message 'failed to connect to control port'.
 It might be something else, but this makes me wonder whether a hard-coded
 path with spaces in it isn't written properly - e.g. ~/Library/Application
 Support which would yield ~/Library/Application with an error instead of
 '~/Library/Application Support'.

 What you describe really sounds like #20210 (also #20215, #18753), but
 that should have been fixed by setting
 `extensions.torlauncher.control_port_use_socket=false`.

 Please try installing the alpha bundle into a directory other than
 /Applications, for example in your home directory or on your desktop. That
 should work around the space issue either way.

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