Tor Browser 7.0 is released

The Tor Browser Team is proud to announce the first stable release in the 7.0 series. This release is available from the Tor Browser Project page and also from our distribution directory.

This release brings us up to date with Firefox 52 ESR which contains progress in a number of areas:

Most notably we hope having Mozilla's multiprocess mode (e10s) and content sandbox enabled will be one of the major new features in the Tor Browser 7.0 series, both security- and performance-wise (Update (July 7, 12:40 UTC): While sandboxing is enabled in Tor Browser 7 it turns out that the long awaited content sandboxing did not make it into the Firefox ESR series as there were still stability issues with it. We try to backport the necessary patches to make it work for Tor Browser, though.). While we are still working on the sandboxing part for Windows (the e10s part is ready), both Linux and macOS have e10s and content sandboxing enabled by default in Tor Browser 7.0. In addition to that, Linux and macOS users have the option to further harden their Tor Browser setup by using only Unix Domain sockets for communication with tor. Update (June 8, 8:00 UTC): As the last point caused some confusion: enabling Unix Domain sockets alone does not harden Tor Browser. One needs that *and* additional sandboxing mechanisms that prevent communication over TCP/IP.

The highlights in our tracking and fingerprinting resistance improvements are: cookies, view-source requests and the Permissions API are isolated to the first party URL bar domain now to enhance our tracking related defenses. On the fingerprinting side we disabled and/or patched several new features, among them WebGL2, the WebAudio, Social, SpeechSynthesis, and Touch APIs, and the MediaError.message property.

WIth the switch to ESR 52 come new system requirements for Windows and macOS users: On Windows Tor Browser 7.0 won't run on non-SSE2 capable machines anymore. On Apple computers OS X 10.9 is now the minimum system requirement.

Besides new system requirements for Windows and macOS users, there are some known issues with Tor Browser 7.0 as well:

  • Mozilla stopped ALSA support in Firefox 52 for Linux users. This means without having PulseAudio available, sound will be broken in Tor Browser 7.0 on Linux.
  • The download button in the PDF viewer is currently broken. A workaround for this bug is right-clicking on the PDF file and choosing the "Save as" option.
  • Tor Browser has recently been freezing on some websites. This is related to a NoScript bug which will hopefully get addressed in a new NoScript version rather soon. If not then we'll ship a workaround for it in the planned Tor Browser 7.0.1 which will update Firefox to 52.2.0esr next week.

Apart from switching to the new Firefox ESR and dealing with related issues we included a new Tor stable version ( and updated our NoScript (5.0.5) and HTTPS-Everywhere versions (5.2.17).

We updated our toolchains during the ESR transition as well. In particular we retired the old GCC-based one for our macOS cross-compilation and rely solely on clang/cctools now.

The full changelog since Tor Browser 6.5.2 is:

  • All Platforms
    • Update Firefox to 52.1.2esr
    • Update Tor to
    • Update Torbutton to
      • Bug 22104: Adjust our content policy whitelist for ff52-esr
      • Bug 22457: Allow resources loaded by view-source://
      • Bug 21627: Ignore HTTP 304 responses when checking redirects
      • Bug 22459: Adapt our use of the nsIContentPolicy to e10s mode
      • Bug 21865: Update our JIT preferences in the security slider
      • Bug 21747: Make 'New Tor Circuit for this Site' work in ESR52
      • Bug 21745: Fix handling of catch-all circuit
      • Bug 21547: Fix circuit display under e10s
      • Bug 21268: e10s compatibility for New Identity
      • Bug 21267: Remove window resize implementation for now
      • Bug 21201: Make Torbutton multiprocess compatible
      • Translations update
    • Update Tor Launcher to
      • Bug 22283: Linux 7.0a4 broken after update due to unix: lines in torrc
      • Bug 20761: Don't ignore additional SocksPorts
      • Bug 21920: Don't show locale selection dialog
      • Bug 21546: Mark Tor Launcher as multiprocess compatible
      • Bug 21264: Add a README file
      • Translations update
    • Update HTTPS-Everywhere to 5.2.17
    • Update NoScript to 5.0.5
    • Update Go to 1.8.3 (bug 22398)
    • Bug 21962: Fix crash on about:addons page
    • Bug 21766: Fix crash when the external application helper dialog is invoked
    • Bug 21886: Download is stalled in non-e10s mode
    • Bug 21778: Canvas prompt is not shown in Tor Browser based on ESR52
    • Bug 21569: Add first-party domain to Permissions key
    • Bug 22165: Don't allow collection of local IP addresses
    • Bug 13017: Work around audio fingerprinting by disabling the Web Audio API
    • Bug 10286: Disable Touch API and add fingerprinting resistance as fallback
    • Bug 13612: Disable Social API
    • Bug 10283: Disable SpeechSynthesis API
    • Bug 22333: Disable WebGL2 API for now
    • Bug 21861: Disable additional mDNS code to avoid proxy bypasses
    • Bug 21684: Don't expose navigator.AddonManager to content
    • Bug 21431: Clean-up system extensions shipped in Firefox 52
    • Bug 22320: Use preference name 'referer.hideOnionSource' everywhere
    • Bug 16285: Don't ship ClearKey EME system and update EME preferences
    • Bug 21675: Spoof window.navigator.hardwareConcurrency
    • Bug 21792: Suppress MediaError.message
    • Bug 16337: Round times exposed by Animation API to nearest 100ms
    • Bug 21972: about:support is partially broken
    • Bug 21726: Keep Graphite support disabled
    • Bug 21323: Enable Mixed Content Blocking
    • Bug 21685: Disable remote new tab pages
    • Bug 21790: Disable captive portal detection
    • Bug 21686: Disable Microsoft Family Safety support
    • Bug 22073: Make sure Mozilla's experiments are disabled
    • Bug 21683: Disable newly added Safebrowsing capabilities
    • Bug 22071: Disable Kinto-based blocklist update mechanism
    • Bug 22415: Fix format error in our pipeline patch
    • Bug 22072: Hide TLS error reporting checkbox
    • Bug 20761: Don't ignore additional SocksPorts
    • Bug 21862: Rip out potentially unsafe Rust code
    • Bug 16485: Improve about:cache page
    • Bug 22462: Backport of patch for bug 1329521 to fix assertion failure
    • Bug 21340: Identify and backport new patches from Firefox
    • Bug 22153: Fix broken feeds on higher security levels
    • Bug 22025: Fix broken certificate error pages on higher security levels
    • Bug 21887: Fix broken error pages on higher security levels
    • Bug 22458: Fix broken `about:cache` page on higher security levels
    • Bug 21876: Enable e10s by default on all supported platforms
    • Bug 21876: Always use esr policies for e10s
    • Bug 20905: Fix resizing issues after moving to a direct Firefox patch
    • Bug 21875: Modal dialogs are maximized in ESR52 nightly builds
    • Bug 21885: SVG is not disabled in Tor Browser based on ESR52
    • Bug 17334: Hide Referer when leaving a .onion domain (improved patch)
    • Bug 18531: Uncaught exception when opening
    • Bug 18574: Uncaught exception when clicking items in Library
    • Bug 22327: Isolate Page Info media previews to first party domain
    • Bug 22452: Isolate tab list menuitem favicons to first party domain
    • Bug 15555: View-source requests are not isolated by first party domain
    • Bug 3246: Double-key cookies
    • Bug 8842: Fix XML parsing error
    • Bug 5293: Neuter fingerprinting with Battery API
    • Bug 16886: 16886: "Add-on compatibility check dialog" contains Firefox logo
    • Bug 19645: TBB zooms text when resizing browser window
    • Bug 19192: Untrust Blue Coat CA
    • Bug 19955: Avoid confusing warning that favicon load request got cancelled
    • Bug 20005: Backport fixes for memory leaks investigation
    • Bug 20755: is broken in Tor Browser
    • Bug 21896: Commenting on website is broken due to CAPTCHA not being displayed
    • Bug 20680: Rebase Tor Browser patches to 52 ESR
    • Bug 22429: Add IPv6 address for Lisbeth:443 obfs4 bridge
    • Bug 22468: Add default obfs4 bridges frosty and dragon
  • Windows
    • Bug 22419: Prevent access to file://
    • Bug 12426: Make use of HeapEnableTerminationOnCorruption
    • Bug 19316: Make sure our Windows updates can deal with the SSE2 requirement
    • Bug 21868: Fix build bustage with FIREFOX_52_0_2esr_RELEASE for Windows
  • OS X
    • Bug 21940: Don't allow privilege escalation during update
    • Bug 22044: Fix broken default search engine on macOS
    • Bug 21879: Use our default bookmarks on OSX
    • Bug 21779: Non-admin users can't access Tor Browser on macOS
    • Bug 21723: Fix inconsistent generation of MOZ_MACBUNDLE_ID
    • Bug 21724: Make Firefox and Tor Browser distinct macOS apps
    • Bug 21931: Backport OSX SetupMacCommandLine updater fixes
    • Bug 15910: Don't download GMPs via the local fallback
  • Linux
    • Bug 16285: Remove ClearKey related library stripping
    • Bug 22041: Fix update error during update to 7.0a3
    • Bug 22238: Fix use of hardened wrapper for Firefox build
    • Bug 21907: Fix runtime error on CentOS 6
    • Bug 15910: Don't download GMPs via the local fallback
  • Android
    • Bug 19078: Disable RtspMediaResource stuff in Orfox
  • Build system
    • Windows
      • Bug 21837: Fix reproducibility of accessibility code for Windows
      • Bug 21240: Create patches to fix mingw-w64 compilation of Firefox ESR 52
      • Bug 21904: Bump mingw-w64 commit to help with sandbox compilation
      • Bug 18831: Use own Yasm for Firefox cross-compilation
    • OS X
      • Bug 21328: Updating to clang 3.8.0
      • Bug 21754: Remove old GCC toolchain and macOS SDK
      • Bug 19783: Remove unused macOS helper scripts
      • Bug 10369: Don't use old GCC toolchain anymore for utils
      • Bug 21753: Replace our old GCC toolchain in PT descriptor
      • Bug 18530: ESR52 based Tor Browser only runs on macOS 10.9+
      • Bug 22328: Remove clang PIE wrappers
    • Linux
      • Bug 21930: NSS libraries are missing from mar-tools archive
      • Bug 21239: Adapt Linux Firefox descriptor to ESR52 (use GTK2)
      • Bug 21960: Linux bundles based on ESR 52 are not reproducible anymore
      • Bug 21629: Fix broken ASan builds when switching to ESR 52
      • Bug 22444: Use hardening-wrapper when building GCC
      • Bug 22361: Fix hardening of libraries built in linux/gitian-utils.yml

June 13, 2017


Tor Browser 7.0 won't start! When I try to start Tor Browser 7.0, the process appears on the task manager, but that disappears in a moment. So I am using Tor Browser 6.5.


June 15, 2017


Any for Tor Browser to change back "Highlight All" keyboard shortcut to "Alt+A", instead of Mozilla's change to "Alt+L".

The change now affect TBB, after the move to Firefox 52 ESR.
Mozilla apparently made the change to accommodate Mac users, but made change to all distributions.
"Alt+L" is very annoying, for it is no longer a simple one-handed operation as "Alt+A".

The change can be found here:

The resources that have the change are apparently:
* view-source:resource://gre/chrome/en-US/locale/en-US/global/findbar.dtd
* view-source:chrome://global/locale/findbar.dtd

If this is the best place to post this, could someone please refer me where to go, thanks.


June 15, 2017


" Since the update, Tor does not save my adjustment to the network setting and about:config, meaning I have to re-do at each browser launch. Anyone have any idea what happened?

Submitted by toruser39284 (not verified) on June 08, 2017

" Could you give us steps how to reproduce your problem? What exactly did you do which worked in the past but does not do so now anymore? "
Submitted by gk on June 09, 2017

In reply to Since the update, Tor does… by toruser39284

" I’m just using the Tor browser without the Tor network by going into network settings and selecting “No Proxy”. Then in “about:config” going to “network.proxy.socks_remote_dns” and Toggling. These settings do not save after I quit the browser and must re-do each time I launch the browser. Previous versions saved these configuration changes and would not require me to do this every time on browser launch.

I have been awaiting an answer on this. Latest update did not address this problem. Please let me know.


June 16, 2017


Sorry to bother you guys, but Tor browser 7.x doesn't work for me, no matter what OS I use.

To cut it short, I have Tor browser 6.5.2 running fine on my windows 7 desktop computer, a few day ago it automatically downloaded 7.0 update, the next time I try to run it, the progress bar stuck at 'retrieving network status' stage, waiting overnight and nothing happens.

Suspecting a corrupted update, I deleted that installation, rolled back to a clean 6.5.2 browser, and downloaded a fresh 7.0 installation file, loaded the same set of obfs4 bridges to the newly installed Tor browser7.0, and it didn't help, when I run it, the progress bar still stuck at 'retrieving network status'.

Alarmed, I checked the log file, and witnessing a crapload of ''Ignoring directory request, since no bridge nodes are available yet." warning, also the exact place where the bootstrap process is '25% asking for network consensus'.

Since I also have a flashdisk loaded with tails 2.12, I decided to do a signature verification, both 6.5.2 binary file and 7.0 turned out ok.

To rule out any antivirus false-positive or network hardware/driver based failures, I booted from tails 2.12, and downloaded a fresh image of tails 3.0 through Tor browser, and burned it to a DVD disk, when I booted from the tails 3.0 DVD, and try to connect to tor network, again using the same set of obfs4 bridges, the same symptom happens, the progress bar won't go past 'retrieving network status' stage. A quick look through the log created again revealing a series of 'Ignoring directory request, since no bridge nodes are available yet.' warning, occasionally, 'I learned some more directory information, but not enough to build a circuit: We have no usable consensus. ' appears. Waiting for hours doesn't make any differences.

From those symptoms, I can only draw the conclusion that either this particular version of Tor browser has some pluggable transport related coding issue, or the country I live in has come up with some particular effective measure to attack the bootstrapping process of tor browser 7.0.

I'm at a total loss here, can anyone share their experience with TBB7.0 or tails 3.0?

BTW my ISP is China telecom.


June 17, 2017


I have had Tor on two of my Macs (OS X10.6.8 & 10.8.5) for only a few months, and have generally enjoyed using it without really understanding it. I do, however understand and completely agree with the need for anonymous browsing for ordinary citizens.
This morning the browser on the 10.8.5 mac wouldn't boot-- giving me the following error msg in a Finder Window: " have OSX 10.8.5. the Application requires OSX 10.9 or later."
I do not recall installing or approving an install of an updated version or Tor in the last several days.
I tried rebooting & re-loading the Tor Browser but got the same results. I cannot use Tor on my 10.8.5 machine, nor can I find any workarounds on your site. (I am writing this from my 10.6.8 machine, by the way.)

Now I have two Qs:
1- How can I retrieve the earlier version of Tor Browser to restore the Tor connection to my 10.8.5 machine?
2- How can I prevent this from happening to my to.6.8 machine?

I must honestly admit that I am computer-challenged, and don't understand much of computer-speak. I am not qualified to mess with my Terminal nor have I even seen this thing called the Registry on any of my computers.
Layman-speak, insofar as it is possible, will be appreciated.
Thanks. Andy 6/17/17

Generally speaking: Tor Browser now requires OS X 10.9 as the minimum on Apple computers. That is a new requirement that came with the switch to Firefox 52. That you got it on your 10.8.5 system is probably due to a bug we recently fixed (, it should not happen again. Now, if you just use your 10.6.8 machine you won't get Tor Browser 7 with all the important security updates. You will stay on the unsecure 6.5.2. The same will happen on your 10.8.5 machine once you have an older Tor Browser version there as well. All the released versions can be found on


July 03, 2017


This new version of TBB is going to take some getting used to. I'm no computer guru by any stretch of the imagination and have no technical skill in computer sciences/IT etc but I do love exploring around in the deep. It's really quite fascinating what kind of stuff is in those depths - many times very interesting and of course at other times rather morbid to say the least. I love the feeling I get when I'm just about to open an onion link (however risky it may be and I am aware of that - I do so at my own risk ) that I've not seen, don't recognize and have no indication of what it might be and no idea of what I'm about to enter into. That little rush that comes over me like sitting in a horror movie waiting for the main character to do this or that and it's all suspenseful and I'm all on the edge of my seat. I love it, can't beat it.

I'm curious to know where the visual feedback offered up by the last version of TBB disappeared to??? For example, in the most recent version of TBB, at the top left of the browser's URL I could change my session, I could change my identity or (sad but true, most intriguing part to me) I could pull down a drop list where I could see the various hops that my data would travel across.

Would someone, anyone be so kind as to direct me to where I can either see this information or explain which add-ons or modifications I might need to make so that I can enable this information once more - or perhaps it's just under my nose and I'm overlooking it entirely. Yes, I know never to modify the browser for security reasons (and I never have). I just can't imagine this would be OK to do now but I'll sure look forward to having that information again.

Thanks in advance@


July 08, 2017


An important change that you should have pointed out in the release announcement for 7.0.

If TBB refuses to start, and exits with errors like Could not bind to Address already in use, you should check your torrc configuration file and remove any lines starting with SocksPort or ControlPort left over from older TBB releases.

At least, this fixed the problem for me. Corrections and more details are appreciated.

That depends. Are you running Windows on it? Then it should not. However it is not clear what happens in this case. Could you give it a try and report back what is happening in that case?

Assuming it is not working for you, could you do us an additional favor and test a build that is supposed to warn users when installing Tor Browser on Windows on a non-SSE2 machine? We did not find such a machine yet and could therefore not verify whether our patch behaves correctly. The bundle can be found on:……



March 08, 2018


How about you people quit making this security shit so god damn hard to install. Seriously, I just downloaded the Linux Tor browser "sandbox". But it's not really a sandbox because it keeps asking for some fucking binary file that is not with it. I thought you people were suppose to be smart? Make it where you can just download all the fucking shit that's required in one package. Stop making life complicated.