Arthur Edelstein authored Nov 08, 2016 and Georg Koppen committed Nov 08, 2016

Fixes bug in the main 20347 patch, reported at
https://trac.torproject.org/projects/tor/ticket/20347#comment:13

Arthur Edelstein authored Oct 17, 2016 and Georg Koppen committed Nov 07, 2016

This patch moves the security slider code from torbutton.js
to its own file (security-prefs.js) and refactors it.

Kathleen Brade authored Oct 11, 2016 and Georg Koppen committed Oct 20, 2016

Retrieve SOCKS port configuration from Tor Launcher if available.
Support the TOR_SOCKS_IPC_PATH environment variable.

Consistently use IPC to refer to Unix domain sockets.

Enhance torbutton_local_tor_check() to correctly handle spaces and
escaped characters within the 'GETINFO net/listeners/socks' response.

Within startup-observer.js, use Services.jsm, Cc and similar
constants, and remove unused code.

Also, remove the 'extensions.torbutton.resist_fingerprinting' pref
and just use the 'privacy.resistFingerprinting' pref instead. We will
use this to implement a checkbox in the about:preferences#privacy page.

Also, we remove the 'extensions.torbutton.restrict_thirdparty'
and use the 'privacy.thirdparty.isolate' pref. At the same time we
will need to add a checkbox to the about:preferences#privacy page
that toggles 'privacy.thirdparty.isolate'.

Note that 'privacy.thirdparty.isolate' will be renamed to
'privacy.firstparty.isolate' in Firefox 52.

This patch also removes the 'extensions.torbutton.no_tor_plugin'
pref and simply uses the 'plugin.disable' pref instead.

Thanks to our patch for Bug 10280 in tor-browser.git,
buttons on the plugins section of about:addons
already let you "Enable plugins" and "Disable plugins"
(i.e., toggle the 'plugin.disable' pref).

Also it's probably better to remove this footgun in the UI.

An equivalent checkbox, "Always use private browsing mode"
is already available in about:preferences#privacy. Better to leave
it more hidden from the user in any case, as it is inadvisable
to disable private browsing mode.

We remove the 'extensions.torbutton.block_disk' pref and use the
'browser.privatebrowsing.autostart' pref instead, because they
are equivalent.

We'll also use add a patch to disable remote jars in tor-browser.git

arthuredelstein@gmail.com authored Sep 15, 2016 and Georg Koppen committed Sep 26, 2016

If the dialog is too small to show all descriptions, then the
descriptions text area will show a scrollbar.

Call Tor Launcher's new TorGetControlSocketFile() function to determine
if a Unix domain socket is being used for Tor control port communication
and, if it is, use it instead of a TCP connection.

When performing the local Tor check (which compares the configured
Firefox SOCKS proxy to the one reported by GETINFO net/listeners/socks),
correctly handle UNIX domain sockets as well as IPv6 addresses.

Restore previous behavior: do not reset the SOCKS-related preferences when
the TOR_SOCKS_HOST and TOR_SOCKS_PORT environment variables are not set.

We need to clear site security settings (like HSTS) explicitely now
as they don't belong to the permissions manager anymore.

Remove the remains of the Torbutton settings panel (which was hidden
by the fix for bug 14630).

Remove the status bar panel (the status bar was removed in Firefox 4).

Remove the outdated "Disable Torbutton to change these settings"
message from the Firefox proxy settings dialog.

Change the behavior of the "Restore Defaults" button in the Privacy
and Security Settings window to no longer reset the browser's proxy
preferences. Our general philosophy is that if Torbutton does not
provide a GUI for changing a preference, Torbutton should not modify
the preference. The exceptions are that Torbutton still supports the
TOR_SOCKS_PORT and TOR_TRANSPROXY environment variables.

Remove a lot of toggle logic, including extensions.torbutton.tor_enabled
and related preferences.

Remove the dual cookie jar support since Tor can no longer be turned off.

Rename torbutton_close_on_toggle() to torbutton_close_tabs_on_new_identity().

Remove torbutton_check_socks_remote_dns() since SOCKS remote DNS is
supported by all modern versions of Firefox.

Remove torbutton_has_good_socks() since it was testing for Firefox 5
or newer.

Remove unused Firefox version check variables, unused functions, and
commented out code.

Yawning Angel authored Aug 15, 2016 and Georg Koppen committed Aug 19, 2016

Firefox requires being able to load chrome:// and resource:// URLs for
things like the media player, with the origin set to the remote URL
that triggered the load.

This is unfortunate in that there's no way to disambiguate malicious JS
versus someone opening a video file (for example).

See https://trac.torproject.org/projects/tor/ticket/19837#comment:5
for why this is a huge nightmare and will eventually require C++ code.

Do not add another notification if one is already visible.

CHANGELOG update, version bump