user/brade/tor-launcher, branch bug20951-01

Bug 20951: Back out Unix domain socket related patches for Tor Browser 6.5

2017-01-10T17:03:41+00:00

Revert the following commits, preserving the _strUnescape() fixes that
were made as part of Bug 20111:
    8871259c966755233b134a5ddb2b4926539d25c6
    Bug 14272: Make Tor Launcher work with Unix Domain Socket option

    32ddac7015be571c336be686b4f901103d0d36f6
    Fix typo

    fa4e114a20067810af0c5cc6a57aa6e849386418
    fixup! Bug 14272: Make Tor Launcher work with Unix Domain Socket option

    8ca52414916c3d8bc2a2974017d759901ddc1736
    Bug 20111: use Unix domain sockets for SOCKS port by default

    4dd8f6130f931616cf014e0ded444c30e04c8bad
    Bug 20185: Avoid using Unix domain socket paths that are too long

Version bump (0.2.11.1)

2016-11-14T08:32:16+00:00

Translations update

2016-11-10T21:03:49+00:00

Bug 19646: Mac OS: wrong location for meek browser profile

2016-11-02T15:41:12+00:00

Set an TOR_BROWSER_TOR_DATA_DIR environment variable before starting tor.
meek-client-torbrowser uses this on OSX to determine the location of the
meek browser profile.

Bug 20185: Avoid using Unix domain socket paths that are too long

2016-10-27T16:02:57+00:00

Enforce a maximum length of 100 for Unix domain socket paths.

If $XDG_RUNTIME_DIR is set, create a unique subdirectory within that
  directory and place the control and SOCKS sockets there if the
  resulting paths will not be too long
else if the length of /control.socket is less than 100
  characters, place both sockets under  (this is compatible
  with the Tor Browser 6.5a3 behavior)
else create a unique subdirectory under /tmp and place the sockets there.

The unique subdirectory that is created under $XDG_RUNTIME_DIR or /tmp
will be named Tor if no such directory exists; otherwise, an integer
suffix will be appended until a new, uniquely named directory is found
such as /tmp/Tor-1.

Also, when starting tor, only include a SocksPort argument if a Unix
domain socket path or a host/port is available.

Bug 20429: Do not open progress window if TOR_SKIP_LAUNCH=1

2016-10-26T19:13:05+00:00

After saving tor settings, if TOR_SKIP_LAUNCH=1 or if
extensions.torlauncher.start_tor is false, avoid opening the progress
dialog to monitor bootstrap progress. This avoids displaying a progress
window that will not make progress (and the situation was made worse by
the fact that clicking Cancel set DisableNetwork=1).

Also, leave the network settings dialog open if we fail to set
DisableNetwork=0.

Bug 20111: use Unix domain sockets for SOCKS port by default

2016-10-20T13:59:20+00:00

New preferences:
  extensions.torlauncher.socks_port_use_ipc (Boolean; defaults to true)
  extensions.torlauncher.socks_ipc_path (override default IPC path)
  extensions.torlauncher.socks_port_flags (SocksPort flags)

Also added support for the TOR_SOCKS_IPC_PATH environment variable.

Consistently use IPC to refer to Unix domain sockets.
Renamed preferences:
  extensions.torlauncher.control_port_use_socket is now
    extensions.torlauncher.control_port_use_ipc
  extensions.torlauncher.control_socket_path is now
    extensions.torlauncher.control_ipc_path
Renamed the TOR_CONTROL_SOCKET env variable to TOR_CONTROL_IPC_PATH.

Change _strUnescape() to throw and fix hex and octal unescaping.

Tagging is not enough, we need version bumps as well

2016-09-28T08:36:03+00:00

Translation updates

2016-09-15T08:22:57+00:00

fixup! Bug 14272: Make Tor Launcher work with Unix Domain Socket option

2016-09-06T07:36:09+00:00

Permissions for the Tor data directory are too permissive for control
sockets. We adapt them (and those for creating files) to the ones used
for Linux bundles by default. This fixes: #20076 and #20075 as FileUtils
is not needed anymore (and hence can't be missing in tl-utils.jsm).