New Release: Tor Browser 8.5a6

Tor Browser 8.5a6 is now available from the Tor Browser Project page and also from our distribution directory.

This release features important security updates to Firefox and updates OpenSSL to 1.0.2q for our desktop platforms.

The most exciting news, however, compared to the alpha release early last week, comes from progress we made on our mobile builds. Tor Browser 8.5a6 is the first version that is built reproducibly for Android devices and is localized in all locales the desktop platforms support.

Moreover, we added an updated donation banner for our year-end donation campaign.

Known Issues:

  1. This release is only supported on armv7 devices (most Android phones and tablets), but x86 devices are not supported yet (such as Chromebooks), even if the Google Playstore is suggesting different things.
  2. Downloading files on newer Android devices crashes Tor Browser. We are currently reviewing a potential fix.

The full changelog since Tor Browser 8.5a5 is:

  • All Platforms
  • Update Firefox to 60.4.0esr
    • Update Torbutton to 2.1.3
      • Bug 28540: Use new text for 2018 donation banner
      • Bug 27290: Remove WebGL pref for min capability mode
      • Bug 28075: Tone down missing SOCKS credential warning
      • Bug 28747: Remove NoScript (XPCOM) related unused code
      • Translations update
    • Bug 28608: Disable background HTTP response throttling
    • Bug 28695: Set default security.pki.name_matching_mode to enforce (3)
    • Bug 27290: Remove WebGL pref for min capability mode
    • Bug 27919: Backport SSL status API
    • Bug 25794: Disable pointer events
  • Windows
    • Update OpenSSL to 1.0.2q
    • Bug 28740: Adapt Windows navigator.platform value on 64-bit systems
  • OS X
    • Update OpenSSL to 1.0.2q
  • Linux
    • Update OpenSSL to 1.0.2q
  • Android
    • Bug 26843: Multi-locale support for Tor Browser on Android
  • Build System
    • Android
      • Bug 25164: Add .apk to our sha256sums unsigned build file
      • Bug 28696: Make path to Gradle dependencies reproducible
      • Bug 28697: Use pregenerated keystore and fix timestamp issues

December 12, 2018



December 12, 2018


Is stilling Orbot integrated no showing expand menu no ips etc.The rest is working well.

December 12, 2018


I've downloaded Tor Browser 64b, for windows 10, and my Mcafee Total Protection keeps telling me that has blocked a virus detected in it, called Real.Protection. Is that normal or could this be effectively a virus? Could this problem be a consequence of a man in the middle or something like this? How can i download a secure file from Tor to install? It seems that the virus is associated with the file firefox.exe . But is activated just when I reinstall Tor. Thank you very much.

December 13, 2018


Is it safe security-wise that Tor Browser allows js in https resources on http webpages?

03:20:37.883 gBrowser.getTabForBrowser is not a function 1 ext-browser.js:74
emit resource://gre/modules/ExtensionUtils.jsm:227:40
shutdown resource://gre/modules/ExtensionParent.jsm:545:5
shutdownExtension resource://gre/modules/ExtensionParent.jsm:664:9
_shutdown resource://gre/modules/Extension.jsm:1855:5
next self-hosted:1214:9
shutdown resource://gre/modules/Extension.jsm:1776:19
next self-hosted:1214:9
shutdown resource://gre/modules/Extension.jsm:1178:5
callBootstrapMethod resource://gre/modules/addons/XPIProvider.jsm:4521:20
updateAddonDisabledState resource://gre/modules/addons/XPIProvider.jsm:4661:13
set userDisabled resource://gre/modules/addons/XPIProvider.jsm:5659:9
doCommand chrome://mozapps/content/extensions/extensions.js:1280:9
doCommand chrome://mozapps/content/extensions/extensions.js:1546:5
initialize/< chrome://mozapps/content/extensions/extensions.js:132:5

Stupid HTTPSE doesn't update its rulesets on browser update, but updates the last update date, thus delaying further updates.

addons.update-checker WARN Request failed: - [Exception... "Certificate issuer is not built-in." nsresult: "0x80004004 (NS_ERROR_ABORT)" location: "JS frame :: resource://gre/modules/CertUtils.jsm :: checkCert :: line 163" data: no]

Tor Browser is still sometimes hangs at exit on Windows 7 (32-bit) and then suicides in a minute with 0xC0000005 error.

Does that happen both with a 64bit and the 32bit Tor Browser version?

Windows 7 (32-bit) can't run 64-bit.

reCAPTCHA protected sites are failing in an infinite loop of "you are wrong!" lately

I guess tor is getting too good at preventing tracking

GPU process can't be recovered after crash. Is it by design?

How would a recovered crash look like? If you mean recovering the old session state in a new one after restarting, then, yes, this is by design.

DDG from about:tor
400 Bad Request

Yes, I already requested it once. But it got not accepted.

Ask Tom.

Boy, you've gotta come up with a simpler way of verifying file signatures. None of the methods work for me. Always get "Data not verified" message no matter what I try or what instructions I follow, which means that, as far as I'm concerned, I got a dodgy file, even if I ain't. I have no idea how the damn things work. What's wrong with a simple Torbrowser plugin that verifies downloaded file signatures automatically? No non-nerdy tech dude has ever verified a file signature except by fluke! And even then, they've no idea whether it's worked or not. That means there are a hell of a lot of unverified Torbrowsers out there, coz nobody can be figure out how to verify them properly...

fuckingfox attacks my gpu! and this is a one tab only! why the fuck it has access to gpu when it was moved to gpu process?! stop this crap! it drains my new laptop's batteries in an hour!

What happens? Do you get error messages? On which platform are you on? Does this happen only with particular sites open or any website(s)?

Lags, 100% gpu for one content process. No. win 10 x64. one shitty site.

it appears to be a fucking animation banner! one banner fucks everything! nonsense!

logs have only that
Got a mutation for an unexpected actor: server1.conn1.child1/domnode80, please file a bug on! inspector.js:307:11
console.trace(): inspector.js:309

Are you able to share that site so that we could investigate?

unfortunately no. it reveals my location.

When I saved a webpage and then clicked it in Downloads tab, it opened in system web browser, and my link leaked!!!

what have you done with performance on windows? how to use it now?

What is the issue? And this started with Tor Browser 8.5a6? Or which was the first one that is not working for you as expected?

??? 100% cpu! 8.x probably.

Integrating Tor core (Orbot) and browser (Orfox) into one Tor Browser .apk is completely unsecure feauture! I use Tor with AFwall+ on Android and I only allow Tor Core (Orbot) and block Orfox so if there is a leak in the browser, then firewall won't let leaked trafiic go.

Can I download a Tor Browser (without tor core) as a separate .apk like it was before? - here I found only old versions.

Nope, the plan is to provide a desktop-like experience which will include some kind of Tor bundled. Orbot was easiest for now but won't be the final solution. However, we won't go back to a non-bundled version until that future arrives (which will be soon anyway, hopefully).

I recently got a new computer with Windows 10. I downloaded the newest Tor about 2-3 weeks ago. It did not open. It downloaded fine, but when I went to launch (either by shortcut or manually by looking through the folder) the round blue circle on my cursor lit up as if something was being executed, but then ... nothing. My task manager did not show Tor running or stalling or anything. I tried a bunch of things, but eventually found Tor 6.6 online. I downloaded that, and it opened fine. I used that for about two days, and then it kept giving me a message to update to Tor 8, which I did. It still continued to work on the updated one.

I didn't use Tor for about a week and a half. Then today I went to launch, and ... nothing, just like before. So I deleted it and reinstalled Tor 6.6, 8.4, and 8.4 with 32bits. For all of these, I received a message that "Tor failed to launch", which would then open a window that said "Tor unexpectedly quit. This may be due to blah blah..." I've googled it, and many people online have had the same problem, but have fixed it in various ways. I've tried opening Tor manually, checking my app security, doing a compatibility troubleshooting and turning off my virus protection. It still shows the same message.

Please may I have some advice to launch Tor?

What antivirus/firewall tool are you using? Did you completely uninstall it (disabling is often not enough)?

Another idea I have: What happens if you run the debug build in (Note it crashes on first start, that's kind of expected due to Interesting things to look for are any Assertions you see in the debug output or `MOZ_CRASH` lines. (The bundles might require a second/third start due to a bug in Tor dev code (see:

Could you file bugs with the same request as in for svg and other features?

One page to destroy the browser!!!

Does that happen on every shutdown? What Windows version are you using? What happens if you run the debug build in (Note it crashes on first start, that's kind of expected due to Interesting things to look for are any Assertions you see in the debug output or `MOZ_CRASH` lines. (The bundles might require a second/third start due to a bug in Tor dev code (see:

No. Windows 7 Pro 32-bit. It doesn't run.