Tor Browser 4.0 is released

Update (Oct 22 13:15 UTC): Windows users that are affected by Tor Browser crashes might try to avoid this problem by opening "about:config" and setting the preference "media.directshow.enabled" to "false". This is a workaround reported to help while the investigation is still on-going.

Update (Oct 25 02:32 UTC): If you are unhappy with the new Firefox 31 UI, please check out Classic Theme Restorer.

Update (Oct 16 20:35 UTC): The meek transport still needs performance tuning before it matches other more conventional transports. Ticket numbers are now listed in the post.

The first release of the 4.0 series is available from the Tor Browser Project page and also from our distribution directory.

This release features important security updates to Firefox. Additionally, due to the POODLE attack, we have also disabled SSLv3 in this release.

The primary user-facing change since the 3.6 series is the transition to Firefox 31-ESR.

More importantly for censored users who were using 3.6, the 4.0 series also features the addition of three versions of the meek pluggable transport. In fact, we believe that both meek-amazon and meek-azure will work in China today, without the need to obtain bridge addresses. Note though that we still need to improve meek's performance to match other transports, though. so adjust your expectations accordingly. See tickets #12428, #12778, and #12857 for details.

This release also features an in-browser updater, and a completely reorganized bundle directory structure to make this updater possible. This means that simply extracting a 4.0 Tor Browser over a 3.6.6 Tor Browser will not work. Please also be aware that the security of the updater depends on the specific CA that issued the www.torproject.org HTTPS certificate (Digicert), and so it still must be activated manually through the Help ("?") "about browser" menu option. Very soon, we will support both strong HTTPS site-specific certificate pinning (ticket #11955) and update package signatures (ticket #13379). Until then, we do not recommend using this updater if you need stronger security and normally verify GPG signatures.

There are also a couple behavioral changes relating to NoScript since 3.6. In particular, by default it now enforces script enable/disable for all sub-elements of a page, so you only need to enable scripts once for a page to work, rather than enabling many sub-scripts. This will hopefully make it possible for more people to use the "High Security" setting in our upcoming Security Slider, which will have Javascript disabled globally via NoScript by default. While we do not recommend per-element whitelisting due to fingerprinting, users who insist on keeping this functionality may wish to check out RequestPolicy.

Note to MacOS users: We intend to deprecate 32bit OSX bundles very soon. If you are still using 32bit OSX 10.6, you soon will need to either update your OS to a later version, or begin using the Tails live operating system.

Here is the changelog since 4.0-alpha-3:

  • All Platforms
    • Update Firefox to 31.2.0esr
    • Update Torbutton to 1.7.0.1
      • Bug 13378: Prevent addon reordering in toolbars on first-run.
      • Bug 10751: Adapt Torbutton to ESR31's Australis UI.
      • Bug 13138: ESR31-about:tor shows "Tor is not working"
      • Bug 12947: Adapt session storage blocker to ESR 31.
      • Bug 10716: Take care of drag/drop events in ESR 31.
      • Bug 13366: Fix cert exemption dialog when disk storage is enabled.
    • Update Tor Launcher to 0.2.7.0.1
      • Translation updates only
    • Udate fteproxy to 0.2.19
    • Update NoScript to 2.6.9.1
    • Bug 13027: Spoof window.navigator useragent values in JS WebWorker threads
    • Bug 13016: Hide CSS -moz-osx-font-smoothing values.
    • Bug 13356: Meek and other symlinks missing after complete update.
    • Bug 13025: Spoof screen orientation to landscape-primary.
    • Bug 13346: Disable Firefox "slow to start" warnings and recordkeeping.
    • Bug 13318: Minimize number of buttons on the browser toolbar.
    • Bug 10715: Enable WebGL on Windows (still click-to-play via NoScript)
    • Bug 13023: Disable the gamepad API.
    • Bug 13021: Prompt before allowing Canvas isPointIn*() calls.
    • Bug 12460: Several cross-compilation and gitian fixes (see child tickets)
    • Bug 13186: Disable DOM Performance timers
    • Bug 13028: Defense-in-depth checks for OCSP/Cert validation proxy usage
    • Bug 13416: Defend against new SSLv3 attack (poodle).

Here is the list of all changes in the 4.0 series since 3.6.6:

  • All Platforms
    • Update Firefox to 31.2.0esr
    • Udate fteproxy to 0.2.19
    • Update Tor to 0.2.5.8-rc (from 0.2.4.24)
    • Update NoScript to 2.6.9.1
    • Update Torbutton to 1.7.0.1 (from 1.6.12.3)
      • Bug 13378: Prevent addon reordering in toolbars on first-run.
      • Bug 10751: Adapt Torbutton to ESR31's Australis UI.
      • Bug 13138: ESR31-about:tor shows "Tor is not working"
      • Bug 12947: Adapt session storage blocker to ESR 31.
      • Bug 10716: Take care of drag/drop events in ESR 31.
      • Bug 13366: Fix cert exemption dialog when disk storage is enabled.
    • Update Tor Launcher to 0.2.7.0.1 (from 0.2.5.6)
      • Bug 11405: Remove firewall prompt from wizard.
      • Bug 12895: Mention @riseup.net as a valid bridge request email address
      • Bug 12444: Provide feedback when “Copy Tor Log” is clicked.
      • Bug 11199: Improve error messages if Tor exits unexpectedly
      • Bug 12451: Add option to hide TBB's logo
      • Bug 11193: Change "Tor Browser Bundle" to "Tor Browser"
      • Bug 11471: Ensure text fits the initial configuration dialog
      • Bug 9516: Send Tor Launcher log messages to Browser Console
    • Bug 13027: Spoof window.navigator useragent values in JS WebWorker threads
    • Bug 13016: Hide CSS -moz-osx-font-smoothing values.
    • Bug 13356: Meek and other symlinks missing after complete update.
    • Bug 13025: Spoof screen orientation to landscape-primary.
    • Bug 13346: Disable Firefox "slow to start" warnings and recordkeeping.
    • Bug 13318: Minimize number of buttons on the browser toolbar.
    • Bug 10715: Enable WebGL on Windows (still click-to-play via NoScript)
    • Bug 13023: Disable the gamepad API.
    • Bug 13021: Prompt before allowing Canvas isPointIn*() calls.
    • Bug 12460: Several cross-compilation and gitian fixes (see child tickets)
    • Bug 13186: Disable DOM Performance timers
    • Bug 13028: Defense-in-depth checks for OCSP/Cert validation proxy usage
    • Bug 4234: Automatic Update support (off by default)
    • Bug 11641: Reorganize bundle directory structure to mimic Firefox
    • Bug 10819: Create a preference to enable/disable third party isolation
    • Bug 13416: Defend against new SSLv3 attack (poodle).
  • Windows:
    • Bug 10065: Enable DEP, ASLR, and SSP hardening options
  • Linux:
    • Bug 13031: Add full RELRO hardening protection.
    • Bug 10178: Make it easier to set an alternate Tor control port and password
    • Bug 11102: Set Window Class to "Tor Browser" to aid in Desktop navigation
    • Bug 12249: Don't create PT debug files anymore

The list of frequently encountered known issues is also available in our bug tracker.

Anonymous

October 16, 2014

Permalink

The gullible starstruck people of the Tor project trust (and worship) lying-spying google more and more each month.

Not really, they're just trying to use tools provided by google to circumvent other types of surveillance. Look, meek is designed to make it look like you're using google/amazon/microsoft instead of tor for your ISP/government. It's a trade off of letting google/amazon/microsoft known your using tor instead of your ISP/government. Depending on your threat model, that may or may not be a good idea. For example, it's probably a better idea for people in Iran than people in Germany.

ha-ha-ha "your improvisation is quite entertaining!"
google/etc==nsa;
so for sure tor sells entry guards to nsa, now nsa will have enough data for correlation analysis/researches and tor will have more funds.
local google sell data to local govs in accordance with there legislation. any corporation exists for getting profit.

If your traffic going through nsa to tor entry guard, and your exit traffic going to nsa watching site isn't it quite obvious to correlate tor user ip with access to suspected site?
Can tor _recommend_ somebody like Snowden to use this channel?
Does tor deny relations between google and nsa?
And as known common users are lazy and will use what is given it will create another pattern - "common users" and "suspicious users" who will not go through google.nsa .
It's understandable these two groups of tor users have different needs - one for security and the others . In right design others should significantly lower SNR for tor links. But mass switching them to google etc. will expose security concerned users!

I think you're right that meek has different anonymity characteristics than e.g. obfsproxy, which also has different characteristics than flashproxy.

First, I should reiterate that none of these transports are enabled by default. So we're not mass switching anybody to routing their traffic through Google or Amazon or Akamai or other centralized services. These are research prototypes that users can use if they want to.

But second, I agree with you that it's worth exploring and better understanding the anonymity vs reachability tradeoffs for these transports. I think that question falls under criteria #5 at
https://lists.torproject.org/pipermail/tor-dev/2013-September/005528.ht…
which I'm hoping we'll have time and attention to work on now that we're ramping up SponsorS:
https://trac.torproject.org/projects/tor/wiki/org/sponsors/SponsorS/Plu…

Anonymous

October 16, 2014

Permalink

This new version of the browser continually crashes on win64, is this a known issue?

Problem signature:
Problem Event Name: APPCRASH
Application Name: firefox.exe
Application Version: 31.2.0.0
Application Timestamp: 00000000
Fault Module Name: xul.dll
Fault Module Version: 31.2.0.0
Fault Module Timestamp: 00000000
Exception Code: 80000003
Exception Offset: 0105d1e4

And yes...!!! The Navy is watching as Tor sits back and does not inform you this activity is going on!!! Tor has been hack I am afraid..! when you do not get answers ..in reality the Tor guys do not even know of you posting issues ... it is going directly.. to echelon!

Your comment has been queued for moderation by site administrators and will be published after approval. ...........O/K !!!! But I already know who is the Moderator...!

Anonymous

October 16, 2014

Permalink

This may be a very dumb question, but why in the hell was the option in NoScript to "Cascade top document's permissions to third party scripts" turned on? That ENABLES a whole bunch of privacy nightmare stuff on a lot of websites like Twitter stuff, Facebook tracking, etc.
Whose....... braindead stupid idea was it to enable that setting by default?
Whoever it was, in my opinion, needs kicked off the TOR team if they did not realize how dumb it was to enable that setting.

I have always hated noscript because for the non geeky it is a nightmare to know how best to set the options for best security.

Someone else said "keep it simple". OK I appreciate the efforts the developers go to to keep us safe, but suspect there may be too many geeks involved who cannot avoid trying to fix things that don't need fixing.

No, they realized that people didn't know how dumb they were using it and expecting to be hard to track and fingerprint. Turning off scripting for trackers doesn't eliminate the ability to track you.

commit 1e64c52cbdf75863cc68f12431e6a3bb510ee695
Author: Mike Perry
Date: Thu Jun 26 18:27:48 2014 -0700

Set prefs for NoScript cascading permissions.

Also auto-reloading the current tab seems like a good plan.

Anonymous

October 16, 2014

Permalink

I can't get Tor 4.0 to function consistently. It downloads fine, I install to a new directory (no overwriting any old version). Everything unpacks OK.

I then click "Start Tor Browser"... it loads, well, something -- "firefox.exe" and "tor.exe" appear on my running processes list. But no actual browser window appears. Any help? This happening to anyone else?

Yes, I 'm using windows vista home premium (32bit) with service pack 2.

Have tried downloading and re-installing TBB afresh many times - can download and install, but when I click "start tor browser" nothing appears to happen. I can see Tor listed as running in windows task manager. After a little while I get Tor browser has stopped working, close program, windows is looking for a solution.

The earlier version worked fine. Currently unable to use Tor.

Anonymous

October 16, 2014

Permalink

To the Tor developers:

Please stop with making it more complex. This meek bullshit should not be forced on to all users by default. Make it an option people can turn on if they wish to involve Google/Amazon/Microsoft in their privacy. Now by involving the best friends of the NSA you are playing a very dangerous came with peoples live.

Again, KEEP IT SIMPLE !

By making things more complex you are creating more attack vectors which are or could get a problem in the future.

That said, your work is appreciated, one more thing i do donations to the project.

Anonymous

October 17, 2014

In reply to by Anonymous (not verified)

Permalink

Like all other pluggable transports, meek is optional and must be explicitly enabled. I'm not seeing what the problem is here.

Anonymous

October 16, 2014

Permalink

Thanks tor, I used tor for many year, it help me view internet directly, thanks a lot

Today I use Tor Browser 4.0 sign in Gmail, the browsers automatic close and win8.1 prompting tor have problem need to close.

This is my first time comment in site, so cool!

Anonymous

October 16, 2014

Permalink

So, does anyone know if TOR 4.0 took care of this issue:

https://www.eff.org/deeplinks/2014/05/mozilla-and-drm

If you don't want to check the link, it's about FireFox being the "last holdout" of Digital Rights Management and how F.F. folded.

It looks like no worries with the older TOR 3.x.x series, but now that TOR has shifted to the new F.F. ESR.....?

Thanks for the answer(s) if they are known.

Tor project compiles Firefox themselves so it's highly unlikely that it has digital restrictions management support included.

Mozilla to their credit did mange to get a relatively benign implementation into Firefox that is optional and doesn't stuff up the rest of the browser, but will it stay that way or will the DRM lovers demand that Mozilla become more like the others?

I certainly hope the pirates put their effort into cracking the DRM on the other browsers which is implemented in a way more to Hollywood's liking than the Firefox implementation.

Thanks for your knowledge and help. I'm not a computer guy/gal so I had no idea what the deal was since now FF has caved (although, not as bad as might seem according to your post).

Thanks again for your input! I'd be lost without so much giving so much in the web community.

Anonymous

October 16, 2014

Permalink

How about adding the github version of random-agent spoofer to Firefox to make more random of timezone and screen size and other information, it is possible I am too late to find this extension but I think many one have no notice so I'm share.

Anonymous

October 16, 2014

Permalink

My TBB keeps crashing every time I try to read my Gmail emails. No idea why. On Win 7, 32-bit. Everything worked perfectly before on the alphas 4.0 1,2, and 3. :(

Same here on Win XP:
TBB 4.0 alpha-3 works fine with gmail
TBB 4.0 crashes when loading gmail:
Dr. Watson Log (in Spanish) says:

  1. Excepción de aplicación ocurrida:<br />
  2. Aplicación: E:\...\Tor Browser\Browser\firefox.exe (pid=2220)<br />
  3. Fecha y hora: 17/10/2014 a las 22:24:00.484<br />
  4. Número de excepción: 80000003 (punto de interrupción codificado)<br />

Google translator (spanish to english):
"punto de interrupción codificado" = "coded breakpoint"

Workaround: disable javascript to force gmail "basic html view"

Anonymous

October 17, 2014

Permalink

Sorry, Roger & Mike & company, but the TBB version 4.0 is buggy as all hell on Windows 7 and possibly Windows 8.1 ... when the installer unpacks the files, I think the directory tree that's made is all screwed up compared to previous versions.

On Tor 3.x, the "Start Tor Browser" was an executable file that did some juju and loaded Tor flawlessly. With Tor 4.0, "Start Tor Browser" has been changed to a shortcut file that points towards "firefox.exe" in a subdirectory. The result: clicking on "Start Tor Browser" loads firefox.exe and tor.exe into memory, into the processes list, without any actual browser window opening. Attempting to click "Start Tor Browser" again at this point gives an error message, "Firefox is already running but appears to not be responding at this time". Huh?

Seriously, take a Win7 box and run the Tor 4.0 installer. You'll get it to work once. But once you close the browser down, good luck getting it to run properly again.

Sticking with 3.6.6 until this gets sorted out. I have found one way to run Tor 4.0 properly, and that's through the just-released TAILS 1.2... there it works fine as far as I can tell. But I don't feel like having to reboot to a USB stick every time I want to do some little thing on Tor.

Anonymous

October 17, 2014

Permalink

Two issues which have cropped up with the new version of TOR Browser 4.0:-

1) When attempting to login to a Gmail account, the browser stops working and closes. This only happens on this email account and not on others. The underlying OS is Windows 7 Pro 64-bit.

2) I have a number of installations across several machines, which are running either Windows 7 Pro 64-bit or Windows 8.1 and they all display the same characteristic, in that the browser frequently doesn't complete the start-up process. You get the little box in the corner whilst it is establishing a connection but no browser opens afterwards.

The worst issue with this second item is the fact that this error is not consistent, sometimes it works and sometimes it doesn't.

Yep, your second issue. Same thing here. Windows 7 Professional 64-bit. I'm the guy who posted the comment directly above yours coincidentally.

"The Tor Browser doesn't complete the start-up process". That's the most succinct way of putting it. It loads the browser into memory, but the actual window never opens. There have been like 10 people on this thread reporting similar issues -- how on Earth was this missed in testing?

As Kenan Thompson once said on SNL's Weekend Update, "FIX IT...! FIIIX IT!!! IT NEED TO BE FIXED!! NOW!" ;-)

I'm having the exact same issue on windows 7, I downloaded and installed and it opened first time no problem within, 5 minutes it crashed and it hasn't opened since. I've tried reinstalling and a system restore to no avail. I've emailed their help desk and awaiting a reply. It does seems strange that it hasn't been addressed here.

Anonymous

October 17, 2014

Permalink

The new interface is confusing, but overall the bundle works.

However, the browser seems to mess with some functions on sites like flickr.com, for example, the 'fav', 'share' and 'download' buttons on the album page are missing, changing no-script rules didn't help. Also when performing a search on this site, sometimes the search result page will get stuck in an infinite 'fetching more photos' loop, no matter how long you wait, no photos will be fetched.

The aforementioned issue is not present when using version 3.6 bundle.

Thanks for the tor team's effort in trying out new things, hope some day the problem will be addressed.

Anonymous

October 17, 2014

Permalink

TorBrowser 3.6 was lagging a lot it was barely usable, now TorBrowser 4.0 also lags but much less than 3.6, it's usable but the lag is visible and noticeable. What do you need to know and which public key should I use to send you what you need to know?

Anonymous

October 17, 2014

Permalink

On Windows XP, Tor Browser 4.0 seems to conflict with Trusteer Rapport, which my bank requires me to use. On my system, Tor Browser 4.0 crashes without exception if Trusteer Rapport is running when I launch it. Trusteer Rapport also goes crazy, jumping to using nearly 1 GB of memory and 50%+ CPU. If Trusteer Rapport is disabled, however, Tor Browser launches and runs normally.

Tor Browser 3.6.6 does not create any issues, nor does vanilla Firefox. I will try and test it on Windows 7 when I can to see if the problem also occurs there (I currently only have access to a Win XP machine).

To clarify: Trusteer Rapport is installed on my system, and the Rapport plugin is installed in vanilla Firefox. The plugin is NOT installed in Tor Browser. So it seems like something about the background process which Trusteer Rapport runs seems to conflict with something in Tor Browser. I'm happy to run specific tests, if it will help with debugging.

I had Trusteer Rapport on my comp. Just uninstalled and Tor working fine. The Trusteer programme was definately the reason Tor was not starting up. Thanks for this. Happy downloading :)