Tor Browser 3.5.2 is released

The 3.5.2 release of the Tor Browser Bundle is now available on the Download page. You can also download the bundles directly from the distribution directory.

This release includes important security updates to Firefox.

Please see the TBB FAQ listing for any issues you may have before contacting support or filing tickets. In particular, the TBB 3.x section lists common issues specific to the Tor Browser 3.x series.

Here is the list of changes since 3.5.1. The 3.x ChangeLog is also available.

  • Rebase Tor Browser to Firefox 24.3.0ESR
  • Bug 10419: Block content window connections to localhost
  • Update Torbutton to 1.6.6.0
    • Bug 10800: Prevent findbox exception and popup in New Identity
    • Bug 10640: Fix about:tor's update pointer position for RTL languages.
    • Bug 10095: Fix some cases where resolution is not a multiple of 200x100
    • Bug 10374: Clear site permissions on New Identity
    • Bug 9738: Fix for auto-maximizing on browser start
    • Bug 10682: Workaround to really disable updates for Torbutton
    • Bug 10419: Don't allow connections to localhost if Torbutton is toggled
    • Bug 10140: Move Japanese to extra locales (not part of TBB dist)
    • Bug 10687: Add Basque (eu) to extra locales (not part of TBB dist)
  • Update Tor Launcher to 0.2.4.4
    • Bug 10682: Workaround to really disable updates for Tor Launcher
  • Update NoScript to 2.6.8.13
Anonymous

February 15, 2014

Permalink

Anyone else have this: I can start up tor, but all attempts to visit torproject.org, or check tor status instantly time out. Why is that?

Anonymous

February 17, 2014

Permalink

I always save bookmarks as HTML, delete the previous version of TBB before installing the latest version which I have already downloaded, and I have no problems. Just my twopennyworth, but I don't speak as a computer geek.

Anonymous

February 17, 2014

Permalink

https://www.torproject.org/docs/signing-keys.html.en

1.) EXPIRED Keys Still on Page:
Jacob Appelbaum: 0xE012B42D
Andrew Lewman: 0x31B0974B

2.) Fingerprint for Georg Koppen not on page yet.

(Linus Nordberg appears to be have been added only within last two days or so, despite the fact that according to said page, Nordberg's key expires "2014-04-23".)

Anonymous

February 24, 2014

Permalink

**Don't know what's wrong, it ran once and never worked afterwards**

2/24/2014 16:29:09 PM.136 [NOTICE] Opening Socks listener on 127.0.0.1:9150
2/24/2014 16:29:09 PM.391 [NOTICE] Bootstrapped 5%: Connecting to directory server.
2/24/2014 17:45:47 PM.565 [WARN] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Permission denied [WSAEACCES ]; RESOURCELIMIT; count 10; recommendation warn)
2/24/2014 17:45:47 PM.565 [WARN] 1 connections have failed:
2/24/2014 17:45:47 PM.565 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)
2/24/2014 19:39:43 PM.417 [WARN] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Permission denied [WSAEACCES ]; RESOURCELIMIT; count 11; recommendation warn)
2/24/2014 19:39:43 PM.417 [WARN] 1 connections have failed:
2/24/2014 19:39:43 PM.417 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)
2/24/2014 19:39:43 PM.418 [WARN] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Permission denied [WSAEACCES ]; RESOURCELIMIT; count 12; recommendation warn)
2/24/2014 19:39:43 PM.418 [WARN] 1 connections have failed:
2/24/2014 19:39:43 PM.418 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)
2/24/2014 19:39:43 PM.419 [WARN] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Permission denied [WSAEACCES ]; RESOURCELIMIT; count 13; recommendation warn)
2/24/2014 19:39:43 PM.419 [WARN] 1 connections have failed:
2/24/2014 19:39:43 PM.419 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)
2/24/2014 19:39:43 PM.419 [WARN] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Permission denied [WSAEACCES ]; RESOURCELIMIT; count 14; recommendation warn)
2/24/2014 19:39:43 PM.420 [WARN] 1 connections have failed:
2/24/2014 19:39:43 PM.420 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)
2/24/2014 19:39:43 PM.420 [WARN] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Permission denied [WSAEACCES ]; RESOURCELIMIT; count 15; recommendation warn)
2/24/2014 19:39:43 PM.420 [WARN] 1 connections have failed:
2/24/2014 19:39:43 PM.420 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)
2/24/2014 19:39:43 PM.421 [WARN] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Permission denied [WSAEACCES ]; RESOURCELIMIT; count 16; recommendation warn)
2/24/2014 19:39:43 PM.421 [WARN] 1 connections have failed:
2/24/2014 19:39:43 PM.421 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)
2/24/2014 19:39:43 PM.422 [WARN] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Permission denied [WSAEACCES ]; RESOURCELIMIT; count 17; recommendation warn)
2/24/2014 19:39:43 PM.422 [WARN] 1 connections have failed:
2/24/2014 19:39:43 PM.422 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)
2/24/2014 19:39:43 PM.422 [WARN] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Permission denied [WSAEACCES ]; RESOURCELIMIT; count 18; recommendation warn)
2/24/2014 19:39:43 PM.423 [WARN] 1 connections have failed:
2/24/2014 19:39:43 PM.423 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)
2/24/2014 19:39:43 PM.423 [WARN] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Permission denied [WSAEACCES ]; RESOURCELIMIT; count 19; recommendation warn)
2/24/2014 19:39:43 PM.423 [WARN] 1 connections have failed:
2/24/2014 19:39:43 PM.424 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)

Anonymous

February 28, 2014

Permalink

Having finally changed to the new 3.5.2.1 I am encountering a number of issues with the new release that make it almost impossible for me to use:

1. Stability problems
I am getting the impression that every new release is becoming more unstable than the previous. On some java script websites crashes in a matter mouse klicks now.

2. Lost Vidalia features
Most annoying among them is the whole browser being closed every time you need "new identity" thingie. Since browser history isn't used for obvious reasons, all research will be lost, logins as well. Many sites ban Tor exit nodes so new idenitity without closed tabs is a must for continuous surfing.
Using the workaround with stand-alone vidalia now.

3. Process naming in windows
The old tor browser bundle used to be called tbb.exe + vidalia.exe in windows task manager. Now only firefox.exe is being used, making it impossible to dinstinguish from regular firefox versions. Very unfortunate choice!

1) Sounds like a Firefox issue. I haven't heard from many people with this issue. Perhaps you can describe steps to repeat?

2) I'm glad the standalone Vidalia is working for you.

3) I think this is also a choice made by the more recent Firefox. But that's a good point -- I'll mention it to the TBB developers and see what they think.

Also, I deleted your duplicate comment on the earlier blog post -- please don't spam the same thing onto multiple blog posts.

No.1 happens especially when opening multiple js-based tabs in a short time on the same website. Makes Tor browser freeze until the process is killed from the task manager. No issues in that regard with earlier versions of Tor. Got the newest js-update, but still no improvement.

Unfortunately using standalone Vidalia didn't solve my problems with the new Tor browser, probably a Firefox issue as well:

'Clearing all current history' with everything crossed from the Tools/Options menu doesn't seem to work to its full extent. When I do that and get 'new identity' from Vidalia to work around login problems, websites still recognize the login-name, although browser cache including cookies has been deleted and the ip address is new (I verified that with whatismyip). So anonymity is corrupted - very alarming!
I have never experienced such a thing before with older versions of Tor.

Also I am being refused access to AOL-webmail since switching to Tor 3.5.2.1. I already found entries online with people encountering the very same problem with the newest Tor. When switching back to an older version of Tor, everything worked fine again. So it's definitely a problem with version 3.5.2.1. :-(
I also tried AOL basic mail, which I think doesn't use js, however, I still do get the following error message: 'BLERK! ERROR 1 C0FE170E'.

Thank you for deleting my redundant blog post. I didn't receive any automated feedback on whether I had successfully posted or not, instead my entry just disappeared completely after hitting 'post comment'. So it looked as if I had to write it again.

Anonymous

March 01, 2014

Permalink

At about:config, why does the variable extensions.torbutton.useragent_override says it's Firefox 17 instead of 24?
The variable general_useragent.override shows it correctly.

Anonymous

March 02, 2014

Permalink

flash proxy Not works any more, I need old version........

bridge flashproxy 0.0.1.0:1

Anonymous

March 05, 2014

Permalink

you cannot deactivate cookies completely ...why is that? tor is not anonymous anymore.

Anonymous

March 07, 2014

Permalink

I have a problem with mozilla addon foxyproxy. Patterns don't work.

Through the usual firfefox all works, but not through the torus assembly. Setting in the expansion of the torus (in your browser assembly) does nothing. What could be wrong?