New Release: Tor Browser 9.0a7

Tor Browser 9.0a7 is now available from the Tor Browser Alpha download page and also from our distribution directory.

Note: this is an alpha release, an experimental version for users who want to help us test new features. For everyone else, we recommend downloading the latest stable release instead.

This is the second alpha release based on Firefox ESR68. This new release contains various improvements and bug fixes. Among them, the Snowflake pluggable transport is now available on Windows too, the issue with non-reproducible builds for the 32bit Linux and Windows bundles have been fixed (we are still working on fixing the issue with the Android ones), and we added support for the x86_64 target on Android (fulfiling Google Play's new requirement for 64bit versions, allowing us to provide an x86 version again). This release also updates Tor to on desktop and on Android. Finally, this alpha release is the first one that is compatible with the upcoming new macOS version (10.15).

Known issues:

  • The build of Tor Browser 9.0a7 for Android is not reproducible right now. We plan to fix this in the next alpha release, to give the usual guarantees reproducible builds aim to provide.
  • New Identity and the bridge configuration in the browser are not easily accessible anymore as we removed the onion button. We are currently working on a replacement for both: New Identity will be exposed directly in the toolbar and the bridge configuration gets integrated in the Firefox settings. For New Identity please use the shortcut (Ctrl+Shift+U) for now or the item in the hamburger menu.
  • Tor Browser on macOS can't get closed from the app menu anymore and other app menu items are not working either.
  • We already have a number of known tickets we need to work on in the coming weeks. The most important ones are tagged with the tbb-9.0-must-alpha keyword. Moreover, we have accumulated Firefox 68 ESR related issues over the time that can easily be queried with our ff68-esr keyword.

If you find any issue with this release, please help us by reporting them so we can fix as much as we can before the first stable release based on ESR68, which is planned for October 22.

The full changelog since Tor Browser 9.0a6 is:

  • All platforms
    • Bug 30304: Browser locale can be obtained via DTD strings
    • Bug 31065: Set network.proxy.allow_hijacking_localhost to true
    • Bug 24653: Merge into torbutton.dtd
    • Bug 31725: Pick up mk in Torbutton properly
    • Bug 31164: Set up default bridge at Karlstad University
    • Bug 15563: Disable ServiceWorkers on all platforms
    • Translations update
  • Windows + OS X + Linux
    • Update Tor to
    • Update OpenSSL to 1.1.1d
      • Bug 31844: OpenSSL 1.1.1d fails to compile for some platforms/architectures
    • Update Tor Launcher to
      • Bug 31303: Do not launch tor in browser toolbox
      • Bug 31491: Clean up the old meek http helper browser profiles
      • Translations update
    • Bug 31598: Disable warning on window resize if letterboxing is enabled
    • Bug 31562: Fix circuit display for error pages
    • Bug 31575: Firefox is phoning home during start-up
    • Bug 31491: Clean up the old meek http helper browser profiles
    • Bug 26345: Hide tracking protection UI
    • Bug 31601: Disable recommended extensions again
    • Bug 30662: Don't show Firefox Home when opening new tabs
    • Bug 31457: disable per-installation profiles
    • Bug 28822: Re-implement desktop onboarding for ESR 68
    • Bug 25483: Provide Snowflake based on Pion for Windows, macOS, and Linux
  • Windows
    • Bug 30800: ftp:// on Windows can be used to leak the system time zone
  • OS X
    • Bug 30126: Make Tor Browser on macOS compatible with Apple's notarization
    • Bug 31702: Backport Mozilla's bug 1578075
  • Linux
    • Bug 31646: Update abicheck to require newer
    • Bug 31380: Snowflake does not start on older Linux systems
  • Android
    • Update Tor to
    • Bug 31192: Support x86_64 target on Android
    • Bug 30380: Cancel dormant by startup
    • Bug 30943: Show version number on mobile
    • Bug 31720: Enable website suggestions in address bar
  • Build System
    • All platforms
      • Bug 31621: Fix node bug that makes large writes to stdout fail
      • Bug 27493: Clean up mozconfig options
      • Bug 31308: Sync mozconfig files used in tor-browser over to tor-browser-build for esr68
    • Windows
      • Bug 30384: Use 64bit containers to build 32bit Windows Tor Browser
      • Bug 31538: Windows bundles based on ESR 68 are not built reproducibly
      • Bug 31584: Clean up mingw-w64 project
      • Bug 31596: Bump mingw-w64 version to pick up fix for #31567
      • Bug 29187: Bump NSIS version to 3.04
      • Bug 31732: Windows nightly builds are busted due to mingw-w64 commit bump
    • Linux
      • Bug 31448: gold and lld break linking 32bit Linux bundles
      • Bug 31618: linux32 builds of Tor Browser 9.0a6 are not matching
      • Bug 31450: Still use GCC for our ASan builds

October 01, 2019


> Among them, the Snowflake pluggable transport is now available on Windows too...

I downloaded the alpha for my Windows box but I don't see Snowflake extension either on Customize or Add-Ons page (there are only NoScript and HTTPS Everywhere). Where is it?

Speaking of Snowflake, reading about it Snowflake uses WebRTC to function. Yet WebRTC can leak real IP Address, and as far as I know TBB disabled them by default. So how does it work when it's included in TBB?

There is no extension shipped. The extension is for helping other people by *offering* to route their traffic to your system. However, the pluggable transport we ship is for helping people that are censored and need to find someone (who might be running the snowflake extension in the browser). You can select it like any other bridge/pluggable transport during start-up.

Yes, WebRTC is disabled in Tor Browser. The snowflake pluggable transport is provided by a separate binary which is running outside of the browser context but is bundled with it.

It seems users can't distinguish Snowflake PT and Snowflake. It needs some action. And, please, don't scary users with bundled WebRTC. It's a highly restricted version that has no relevance to what users call WebRTC.

Error: TelemetryStopwatch: key "WEBEXT_CONTENT_SCRIPT_INJECTION_MS" was already initialized ExtensionTelemetry.jsm:109:31
Error: TelemetryStopwatch: key "WEBEXT_CONTENT_SCRIPT_INJECTION_MS_BY_ADDONID" was already initialized ExtensionTelemetry.jsm:113:41

How can I reproduce those errors?

New NoScript RC is a disaster :(

> Tor Browser 9.0a7 is now available from the Tor Browser Alpha download page and also from our distribution directory.
And Google Play?

Yes, the mobile version should be on Google Play as well and F-Droid is coming soon, too.

Oh, you don't want to advertise Google Play in your blog no more. Makes sense.

x86_64 target on Android?

Crash Guard Disabled Features
Failure Log
(#0) Error WMF VPX video decoding is disabled due to a previous crash.
(#1) CP+[GFX1-]: WMF VPX video decoding is disabled due to a previous crash.

How can I reproduce that crash? On which operating system is this happening?

WMF on which operating system? Nice joke. That's an expected crash. No fingerprinting vector except performance. Nothing to worry about.

It could be Windows 7 or 10 maybe and that could make a difference. That said without more context it's hard to say what is going on. Maybe something like

It is how they test for HW VPX currently. Seems not fingerprintable.

partial update is not clean; logs:
NS_main: unable to remove directory: tobedeleted, err: 41

Where/when do you have this error?

Win 10 x64

I created to track this issue. Please direct follow up comments there.

Snowflake LICENSE file is in Docs\snowflake, while others are in Docs\Licenses\PluggableTransports

Snowflake file has:
- [x] Can browse using Tor over Snowflake.
- [ ] Reproducible build with TBB.

Thanks, that part of the README was somewhat obsolete. I removed it in….

[10-02 09:53:52] Torbutton INFO: New window
[10-02 09:53:52] Torbutton INFO: called init()
[10-02 09:53:52] Torbutton INFO: This is a Tor Browser
[10-02 09:53:52] Torbutton INFO: Initializing the Torbutton button.
[10-02 09:53:52] Torbutton INFO: get_toolbutton(): did not find torbutton-button 3
[10-02 09:53:52] Torbutton INFO: init completed

Do you have any details that can help reproduce this issue?

Doesn't "Torbutton INFO: New window" sound for you?
You removed torbutton-button. Needs a cleanup.

Plugins is empty

Yes, there should be no plugins there.

There should be `Enable plugins` button. See stable.

Bug 39187: Bump NSIS version to 3.04

Error: Invalid ticket number
Ticket 39187 does not exist.

Thanks, fixed.

Bug 31450: Use still GCC for our ASan builds

Still use GCC

Thanks, fixed.

could tor add an snowflake switch in TTB for server? i don't think who want be a volunteer will run another browser in using TTB , but if it is a button in TTB, they will. an add-on for webrtc may cause privacy problem, just a switch for standlone snowflake program, but in TTB.

The problem is that Tor Browser has no WebRTC support for anonymity and privacy reasons.

TypeError: win is null ExtensionUtils.jsm:104:3

Do you have steps to reproduce the error?

CSS Exfil Vulnerability Tester.

The technique can also be used to de-anonymize users on dark nets like Tor. Defense methods are discussed for both website operators as well as web users, and a pair of browser extensions are offered which guard against this class of attack.

Introducing CSS Exfil
Several months ago I began tinkering with Chrome's XSS auditor looking for bypasses. One remote injection method which reliably got through Chrome's filter was CSS injection. By utilizing injected CSS, an attacker essentially has complete control over the look-and-feel of a page. I also discovered an attacker can leverage CSS to steal form data. By utilizing CSS alone, browser protections like NoScript can't block the egress of data (although NoScript's XSS auditor is more effective than Chrome at blocking some of the injection Proof of Concept attacks detailed below).

While CSS injection is not a new vulnerability, using CSS as the sole attack vector to reliably exfiltrate data - to my knowledge - has never been presented. I am also not aware of any effective method previously documented to guard end users against such attack - other than to block CSS, which is not a practical solution.

I understand that installing other extensions is not advised; that being said, DTA has finally been re-released :) as a WebExtension, which generally works as expected in Firefox, but I'm having trouble with it in TorBrowser. Any idea why I might be experiencing issues?

Again, I realize that those of you working on TB are not involved in any way with DTA (which is still working out the kinks), but I'm trying to find out why I'm having problems since ESR 68 reportedly works.

Basic functionality like adding a targeted file to the Download Manager does not even show up, therefore a d/l never runs, completes, or even appears. This still happens while enabling only DTA, even after restarting.

I'm not attempting to d/l large files or anything (always mindful of others' needs on the network). Most are much smaller than 1mb. I also don't leave the extension enabled, even in my FF browser; I only enable it after pages have finished loading, if I need it multiple (smaller) files.

Thank you for any help you could provide.

Secure Connection Failed

An error occurred during a connection to ****.com. PR_END_OF_FILE_ERROR

Unexpectedly encountered end of file (Mac OS only).

but that's on Win 10!

[10-05 05:09:49] Torbutton INFO: New domain isolation for --unknown--: 891f840bfd9f26cfae3623da63e4701b
[10-05 05:09:49] Torbutton INFO: tor SOCKS: https://****.org/.../avatars/35d.png via

Join the discussion...

We encourage respectful, on-topic comments. Comments that violate our Code of Conduct will be deleted. Off-topic comments may be deleted at the discretion of the post moderator. Please do not comment as a way to receive support or report bugs on a post unrelated to a release. If you are looking for support, please see our support portal or ways to get in touch with us.

This question is for testing whether or not you are a human visitor and to prevent automated spam submissions.

13 + 4 =
Solve this simple math problem and enter the result. E.g. for 1+3, enter 4.