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 09, 2017


Yet another quite annoying change:
If I right click on a link, the popup menu
is positioned below the cursor, so immediately
releasing the button activates the Open in new
window menu, which is not even the first.
Earlier the menu was a little bit to the right,
so after right clicking I could move my mouse
calmly to a menu item, and could choose it
with a left click. Now I have to drag.


June 09, 2017


New version is causing overlapping items on the YouTube website like the video control / play button and the masthead to flicker (macOS).


June 09, 2017


I sometimes wondered to myself if Tor devs would be that dumb to auto update Tor Browser to a version no longer compatible with the operating system itself. Well done. You were that stupid.

Did it not occur to you that it would have been better NOT to have updated if: System OS X version < new minimum and maybe displayed a warning message ? It's so obvious. But to just disable software that way, that people rely on causes a whole lot of inconvenience. Stupid, stupid, stupid.

Versions for older OSes expire in a week. And use of vulnerable browsers is really

Stupid, stupid, stupid.

FWIW, this is fixed now. You should be able to use 6.5.2 again without getting any updates and it is still up-to-date for the next two days until we finally switch to ESR52. Sorry for the inconvenience.

Cert for this page, has no mention of domain.


Look at the Subject Alt Name.

When 1 TBB browserwindow is open, i see 2 firefox.exe*32 with 2 different PIDs.
That's new.
What's the reason for?

Firefox is using different processes for content and the browser user interface now. Thus, for instance crashing tabs won't shut down your whole browser anymore.

When trying to install Torbrowser for Ubuntu 16.04 from the Ubuntu store, an error occurs "signature verification failed" This issue was also noted in Ubuntu forum as a outdated key "…"

This prevents installation

Please contact the torbrowser-launcher maintainer to fix that. We are not distributing this tool.

Is the documentation on gpg key validation that the torbrowser presents valid?

I tried verifying a key and it did not work

gpg --keyserver --recv-keys 0x4E2C6E8793298290
gpg: keyring `/home/macneal/.gnupg/secring.gpg' created
gpg: requesting key 93298290 from hkp server
?: Host not found
gpgkeys: HTTP fetch error 7: couldn't connect: Connection timed out
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0
gpg: keyserver communications error: keyserver unreachable
gpg: keyserver communications error: public key not found
gpg: keyserver receive failed: public key not found
macneal@RALF2:~/Downloads$ gpg --fingerprint 0x4E2C6E8793298290
gpg: error reading key: public key not found

We love TOR and as a security team we do appreciate it. How ever more journalists are using it world wide for fear of abductions. We salute them for their stories.. Please use Linux any version to help freedom and democracy
around globe. Thanks a lot to

How would someone know if the new machine they're buying is SSE2-capable?

On Windows Tor Browser 7.0 won't run on non-SSE2 capable machines anymore.

Unless the new machine is using an exotic embedded x86 processor, or predates either the Pentium 4 (2000) or Athlon 64 (2003) it will support SSE2. If it can run a 64 bit operating system, it also will support SSE2, because the extension is a mandatory part of x86_64.

Thank you. So with Windows, basically anything 32-bit and 64-bit Vista to 10? I'm trying to refurbish an extra Vista 32-bit and it's working fine.

Microsoft began requiring SSE2 in Windows 8, but what operating system you use isn't that meaningful in this context. Really, unless your computer dates back to the early 2000s, this shouldn't be an issue for anyone.

If you are buying a new machine it is for sure SSE2-capable. This affects only PCs that are manufactured before ca 2001.

Tor Browser 7.0 problem: No matter how many times I click on "new tor circuit" the first node in the network remain the same. only the 2nd and 3rd nodes change.
What's up with this?
I deleted and reinstalled several times but the problem persists.

yes, thanks to cia for this new tor version, since cia added a lot of tor server relay to spy users, tor doesn't have the option to easily made your installation of tor becoming a relay !!

I have downloaded and installed this version at least a dozen times. I keep getting the error "Could not connect to Tor control port."

I have made sure I am not using any bridges. I have checked there are no firewall problems.

I am using Windows 7 Enterprise.

Any assistance is appreciated.

Do you have some antivirus software installed? If so you can uninstall it and your firewall software for testing purposes (disabling is often not enough). We hear this issue quite often if we ship a new Tor version which is usually caused by antivirus/firewall software being wrong in "thinking" this new Tor version is malicious.

From the IP address they are able to block OBFS4,OBFS3 meek-amazon. This site is a Canadian public WIFI site used in City Brampton.

Does the new version works simultaneously in the browser and as a socks proxy? I have it working this way, using "SocksPort" in a torrc config file.

What happened with the "ControlPort" parameter? Tor no longer accepts it. And when "SocksPort" enabled, is control port always 9151? (i have it working). How to change control port now?

"ExitNodes" parameters act the same as before, if interesting.

Tor Launcher is now responsible for setting the proper parameters for the default socks and control port. For the latter there is a preference now, extensions.torlauncher.control_port, which you might help you. Plus there are environment variable you could set: TOR_CONTROL_HOST and TOR_CONTROL_PORT.
suddenly states (differing from Tor Browser 6.5.2):
"You are using Tor, but your browser profile differs from the recommended `Tor Browser Bundle` default profile."
Furthermore, "Authentication" and "User-Agent" now show up as red on both Tor Browser 7.0 for Windows and Linux 64-bit, others we have not checked.

Yes, the test needs to get updated (both for the User Agent check and the Authentication test; for the latter see:

ТОР не работает На OS X Макбук. Окно выскакивает с надписью: "надо обновиться до версии 10.9"

Yes, Tor Browser 7 (as Firefox 52 which it is based on) won't work on OS X < 10.9 anymore. This is the new minimum system requirement Mozilla imposed on its browser.

Just upgraded from 6.5.1 to 7.0 (on win10 64) and Tor does not even start. Rebooted PC still nothing. Until 10 min ago 6.5.1 worked perfectly. Luckily I still have the 6.5.1 exe file, so got rid of 7.0 reinstalled 6.5.1 and it works fine...

Do you have an antivirus/firewall program on your computer? If so, you could uninstall it and see if that solves the problem (disabling is often not enough). We see this issue often if we ship new Tor versions which is caused by antivirus/firewall software "thinking" this new Tor version is harmful (which it is not).

same issue, error persists, and it doesnt copy a log, tried without the firewall and the antivirus same error, should i return to the older version?

Does it work if you install 7.0.1 to a different location starting over with a clean, new Tor Browser?

In this new Tor version, the web page has incorrect visualization. Any configuration needed? Thanks

Huh, indeed. I've opened to investigate this problem. You should not need any configuration at all (that way it works in Tor Browser 6.5.2 at least).

Until now, downloading executables with TB leaked info (including download metadata)?

Why does TB 7.0 need access to:

/dev/shm/org.chromium.* rw,
@{PROC}/[0-9]*/net/route r,
@{PROC}/[0-9]*/net/arp r,

I run torbrowser in chrooted environment (CentOS 6.5). After upgrade to version 7.0 torbrowser doesn't render content of html pages. Only titles are shown, but white space instead of text and pictures in the main area. The following messages are displayed in the terminal

Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: Failed 2 buffer db=0 dw=0 for 0, 0, 1000, 800 (t=6.19759) [GFX1-]: Failed 2 buffer db=0 dw=0 for 0, 0, 1000, 800

When torbrowser is running in normal environment it works correctly. However I prefer to run it in chrooted (restricted) environment for better security. It's been working nice for the last several years until now. What can be the cause of this issue?

Good question. This sounds like a Firefox bug to me. Could you test whether a normal Firefox 52 ESR version works in your environment? See:

There are two firefox versions available on you link. Firefox 45.9.0 ESR works in my environment. Firefox 52.2.0 ESR doesn't work even in normal environment because requires new GTK 3 that isn't provided with CentOS 6.5 packet management. So it involves compiling GTK and dependencies from source. Maybe I will do it later and then comment it here.

Oh, indeed I forgot about that. Hm, I wonder how to track that issue down. If you could help us with that that would be great. I've filed, thanks.

One idea we had on the bug was that maybe in your chroot some necessary packages are missing. Not sure how easy it is for you to figure that out, though.

It's quite easy if chroot to root directory '/'.

I figured out the cause of the issue. Version 7 of torbrowser requires filesystem /dev/shm. So adding it to chroot directory resolves the problem. Thanks for your attention.