New Release: Tor Browser 10

Update 1700 UTC 2020-09-24: After investigating the error seen by Windows users while playing videos on Youtube, a user helped us identify the cause. Until this is fixed in an upcoming release, a workaround is setting media.rdd-opus.enabled as false in about:config.

The new shiny Tor Browser 10 for Desktop is now available from the Tor Browser download page and also from our distribution directory!

Android Tor Browser 10 is under active development and we are supporting the current 9.5 series for Android until the new one is ready. We are informed by Mozilla of any issues they learn about affecting the 9.5 series. We expect to release the new Tor Browser for Android based on Fenix in the following weeks.

Tor Browser 10 ships with Firefox 78.3.0esr, updates NoScript to 11.0.44, and Tor to 0.4.4.5. This release includes important security updates to Firefox.

This new Tor Browser release is focused on stablizing Tor Browser based on a new extended support release of Mozilla Firefox. Tor Browser 10.0 is the first stable release of the 10.0 series based on Firefox 78esr.

Note: Tor Browser 10.0 is the final Tor Browser series supporting CentOS 6. Beginning with the 10.5 series, CentOS 6 is not supported.

Note: In this release JavaScript is controlled by NoScript again. JavaScript was completely disabled on the Safest security level beginning in Tor Browser 9.0.7. The Firefox preference javascript.enabled is reset to true in this release. You must re-set it as false if that is your preference.

Give Feedback

If you find a bug or have a suggestion for how we could improve this release, please let us know. Thanks to all of the teams across Tor, and the many volunteers, who contributed to this release.

Full Changelog

The full changelog since Tor Browser 9.5.4 is:

  • Windows + OS X + Linux
    • Update Firefox to 78.3.0esr
    • Update Tor to 0.4.4.5
    • Update Tor Launcher to 0.2.25
      • Bug 32174: Replace XUL <textbox> with <html:input></html:input></textbox>
      • Bug 33890: Rename XUL files to XHTML
      • Bug 33862: Fix usages of createTransport API
      • Bug 33906: Fix Tor-Launcher issues for Firefox 75
      • Bug 33998: Use CSS grid instead of XUL grid
      • Bug 34164: Tor Launcher deadlocks during startup (Firefox 77)
      • Bug 34206: Tor Launcher button labels are missing (Firefox 76)
      • Bug 40002: After rebasing to 80.0b2 moat is broken
      • Translations update
    • Update NoScript to 11.0.44
      • Bug 40093: Youtube videos on safer produce an error
    • Translations update
    • Bug 10394: Let Tor Browser update HTTPS Everywhere
    • Bug 11154: Disable TLS 1.0 (and 1.1) by default
    • Bug 16931: Sanitize the add-on blocklist update URL
    • Bug 17374: Disable 1024-DH Encryption by default
    • Bug 21601: Remove unused media.webaudio.enabled pref
    • Bug 30682: Disable Intermediate CA Preloading
    • Bug 30812: Exempt about: pages from Resist Fingerprinting
    • Bug 31918+33533+40024+40037: Rebase Tor Browser esr68 patches for ESR 78
    • Bug 32612: Update MAR_CHANNEL_ID for the alpha
    • Bug 32886: Separate treatment of @media interaction features for desktop and android
    • Bug 33534: Review FF release notes from FF69 to latest (FF78)
    • Bug 33697: Use old search config based on list.json
    • Bug 33721: PDF Viewer is not working in the safest security level
    • Bug 33734: Set MOZ_NORMANDY to False
    • Bug 33737: Fix aboutDialog.js error for Firefox nightlies
    • Bug 33848: Disable Enhanced Tracking Protection
    • Bug 33851: Patch out Parental Controls detection and logging
    • Bug 33852: Clean up about:logins to not mention Sync
    • Bug 33856: Set browser.privatebrowsing.forceMediaMemoryCache to True
    • Bug 33862: Fix usages of createTransport API
    • Bug 33867: Disable password manager and password generation
    • Bug 33890: Rename XUL files to XHTML
    • Bug 33892: Add brandProductName to brand.dtd and brand.properties
    • Bug 33962: Uplift patch for bug 5741 (dns leak protection)
    • Bug 34125: API change in protocolProxyService.registerChannelFilter
    • Bug 40001: Generate tor-browser-brand.ftl when importing translations
    • Bug 40002: Remove about:pioneer
    • Bug 40002: Fix generateNSGetFactory being moved to ComponentUtils
    • Bug 40003: Adapt code for L10nRegistry API changes
    • Bug 40005: Initialize the identity UI before setting up the circuit display
    • Bug 40006: Fix new identity for 81
    • Bug 40007: Move SecurityPrefs initialization to the StartupObserver component
    • Bug 40008: Style fixes for 78
    • Bug 40017: Audit Firefox 68-78 diff for proxy issues
    • Bug 40022: Update new icons in Tor Browser branding
    • Bug 40025: Revert add-on permissions due to Mozilla's 1560059
    • Bug 40036: Remove product version/update channel from #13379 patch
    • Bug 40038: Review RemoteSettings for ESR 78
    • Bug 40048: Disable various ESR78 features via prefs
    • Bug 40059: Verify our external helper patch is still working
    • Bug 40066: Update existing prefs for ESR 78
    • Bug 40066: Remove default bridge 37.218.240.34
    • Bug 40073: Disable remote Public Suffix List fetching
    • Bug 40073: Repack omni.ja to include builtin HTTPS Everywhere
    • Bug 40078: Backport patches for bug 1651680 for now
    • Bug 40082: Let JavaScript on safest setting handled by NoScript again
    • Bug 40088: Moat "Submit" button does not work
    • Bug 40090: Disable v3 add-on blocklist for now
    • Bug 40091: Load HTTPS Everywhere as a builtin addon
    • Bug 40102: Fix UI bugs in Tor Browser 10.0 alpha
    • Bug 40106: Cannot install addons in full screen mode
    • Bug 40109: Playing video breaks after reloading pages
    • Bug 40119: Enable v3 extension blocklisting again
  • Windows
    • Bug 33855: Don't use site's icon as window icon in Windows in private mode
    • Bug 40061: Omit the Windows default browser agent from the build
  • OS X
    • Bug 32252: Tor Browser does not display correctly in VMWare Fusion on macOS (mojave)
  • Build System
    • Windows + OS X + Linux
      • Bump Go to 1.14.7
      • Bug 31845: Bump GCC version to 9.3.0
      • Bug 34011: Bump clang to 9.0.1
      • Bug 34014: Enable sqlite3 support in Python
      • Bug 34390: Don't copy DBM libraries anymore
      • Bug 34391: Remove unused --enable-signmar option
      • Bug 40004: Adapt Rust project for Firefox 78 ESR
      • Bug 40005: Adapt Node project for Firefox 78 ESR
      • Bug 40006: Adapt cbindgen for Firefox 78 ESR
      • Bug 40037: Move projects over to clang-source
      • Bug 40026: Fix full .mar creation for esr78
      • Bug 40027: Fix incremental .mar creation for esr78
      • Bug 40028: Do not reference unset env variables
      • Bug 40031: Add licenses for kcp-go and smux.
      • Bug 40045: Fix complete .mar file creation for dmg2mar
      • Bug 40065: Bump debootstrap-image ubuntu_version to 20.04.1
      • Bug 40087: Deterministically add HTTPS Everywhere into omni.ja
    • Windows
      • Bug 34230: Update Windows toolchain for Firefox 78 ESR
      • Bug 40015: Use only 64bit fxc2
      • Bug 40017: Enable stripping again on Windows
      • Bug 40052: Bump NSIS to 3.06.1
      • Bug 40061: Omit the Windows default browser agent from the build
      • Bug 40071: Be explicit about no SEH with mingw-w64 on 32bit systems
      • Bug 40077: Don't pass --no-insert-timestamp when building Firefox
      • Bug 40090: NSIS 3.06.1 based builds are not reproducible anymore
    • OS X
      • Bug 34229: Update macOS toolchain for Firefox 78 ESR
      • Bug 40003: Update cctools version for Firefox 78 ESR
      • Bug 40018: Add libtapi project for cctools
      • Bug 40019: Ship our own runtime library for macOS
    • Linux
      • Bug 34359: Adapt abicheck.cc to deal with newer GCC version
      • Bug 34386: Fix up clang compilation on Linux
      • Bug 40053: Also create the langpacks tarball for non-release builds
Anonymous

September 24, 2020

Permalink

17:47:20.059 [Exception... "Component returned failure code: 0x80520001 (NS_ERROR_FILE_UNRECOGNIZED_PATH) [nsIXPCComponents_Utils.readUTF8URI]" nsresult: "0x80520001 (NS_ERROR_FILE_UNRECOGNIZED_PATH)" location: "JS frame :: resource://gre/modules/L10nRegistry.jsm :: L10nRegistry.loadSync :: line 661" data: no] 2 L10nRegistry.jsm:661:19

Anonymous

September 24, 2020

Permalink

Thank you for writing those notes and the update workaround in the original blog post!! Good management right there.

Anonymous

September 24, 2020

Permalink

I updated, but it says "The bookmarks and history system will not be functional because one of Tor Browser's files is in use by another application. Some security software can cause this problem." I also can't browse on Tor anymore, and it always says "Secure Connection Failed An error occurred during a connection to [site]. security library failure. Error code: SEC_ERROR_LIBRARY_FAILURE"
i rebooted pc but nothing .. does not work.

Anonymous

September 24, 2020

Permalink

On upgrading to Tor 10, using Tor browser in transparent mode (i.e. TOR_TRANSPROXY=1) doesn't work.

I have a linux system that connects to the internet via a gateway running on a VM, so I don't use the tor proxy on the client VM. This client VM can no longer connect to the internet after the upgrade. Note that non-Tor browsers on this client machine CAN connect to the internet.

I tried re-installing Tor 10 with the same result. I re-installed Tor 9.5 and everything works ok. I have disabled upgrades because Tor 10 is currently unusable for me.

Anonymous

September 25, 2020

Permalink

I am confused, in this post you say "Bug 40016: Update Snowflake to discover NAT type", but Snowflake is still not available in the stable release?

Anonymous

September 26, 2020

Permalink

how to turn off animations/effects like it was with toolkit.cosmeticAnimations.enabled;false in previous version of firefox?

Anonymous

September 26, 2020

Permalink

browser.tabs.maxOpenBeforeWarn

Seems to be broken.

Anonymous

September 26, 2020

Permalink

Recently switched from Windows 10 to Ubuntu 20.04. Was able to download and use tor with just a minimal learning curve thing.

Tor updated. So did Ubuntu, to 20.04 LTS. Somewhere along the way, I can't access tor any longer. I have spent 4 days that I will never get back doing every damn trick that is out there in the blogs to make tor functional. I get bupkis.

Am I the only schlepp on the planet going through this? Or are there others just not bothering and using clearnet instead.

I'm new to Linux, to be sure. I also have buddies in the tor world that are really tech savvy and need to use little words for me. That said... I'm NOT imagining this. I've tried both Ubuntu and Linux mint 20.04 LTS. I've done simple and not so simple things in terminal.

I want to say again... before the TBB update, I had NO such hoops to jump through. It was super easy to get tor to work. Really. Now? Damn near impossible. Help needed. If you send me to blog posts already posted? I've tried them. It's not working.

Somewhere between the latest updates that collided TBB and Linux vs 20.04 LTS? Hell came to my breakfast table.

Help appreciated.

Thanks.

FML

Anonymous

September 27, 2020

Permalink

It seems letterboxing doesn't work properly when HiDPI scaling enabled on GNOME.
Previous version works good.

Anonymous

September 28, 2020

Permalink

I do love Tor Browser, but the list of "popular" websites blocking/censoring Tor seem to be growing by the day:

https://www.macys.com/
https://www.merriam-webster.com/
https://www.quora.com/ (Partial block)
https://www.snopes.com/

These are just four websites that are either difficult to access natively in Tor Browser—i.e., clicking the "New Circuit for this Site" button enough times will eventually provide access—or impossible to access natively in Tor Browser—i.e., clicking the "New Circuit for this Site" button umpteen times won't give you access.

You've successfully implemented solutions to deal with blocks/censorship on a country level, but can anything be done to mitigate/circumvent the blocking/censorship that's happening more and more on a website level?

An official up-to-date list of websites currently blocking Tor would be a good start!

Anonymous

October 01, 2020

Permalink

> Bug 33856: Set browser.privatebrowsing.forceMediaMemoryCache to True
Playing video is fully broken in 32-bit Windows!

Anonymous

October 01, 2020

Permalink

Hello! TBB10 is fine!
Here some regressions since TBB9.5.4 however:
- open https://vc.ru - you may see the site-icon at browser-tab is BROKEN. I had observed such kind of icon-corruption at some other sites too - do not remember the urls.

Anonymous

October 01, 2020

Permalink

This version of Tor Browser ignores window manager settings like "do nothing" on title bar double click, and will maximize when double clicked.

Previous version honored this setting and would not maximize. Regular firefox continues to honor this. This is unique to TB 10.0.

Anonymous

October 02, 2020

Permalink

What happened to the blinking yellow exclamation point when an update is available? I just realized one of my VMs was still on 9.5.1, and must have missed several updates due to insufficient disk space. I only noticed it was still an old version because the URL bar looks slightly different in 10.

Anonymous

October 05, 2020

Permalink

AmIUnique.org says my browser is unique because of canvas. Is canvas now being deliberately randomized? I thought Tor Project always argued than uniformity is better than randomization, so why this change in strategy now?

Anonymous

October 13, 2020

Permalink

The picture-in-picture button appears on videos now. Clicking it does nothing, but right-clicking a video and clicking "Picture-in-Picture" in the menu activates picture-in-picture.