New Release: Tor Browser 10.0a6

by sysrqb | August 27, 2020

Tor Browser 10.0a6 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.

We are happy to announce the second alpha for desktop users based on Firefox 78 ESR. The Android version is under active development and will be available in the coming weeks.

We released the first alpha version based on ESR 78 one week ago.

Tor Browser 10.0a6 ships with Firefox 78.2.0esr, and updates NoScript to 11.0.39. Please report bugs with steps to reproduce, either here or on Gitlab, or essentially with any other means that would reach us. We are in particular interested in potential proxy bypasses which our proxy audit missed.

Also, this release features important security updates to Firefox.

Note: Android Tor Browser is still based on Firefox 68esr. As a result, Android and desktop packages were built separately, based on tag tbb-10.0a6-build1 and tbb-10.0a6-build2 respectively. The resulting sha256sums-unsigned-build.txt files were merged and signed before publishing.

Note: We encountered updater issues for all alpha users that have been auto-updating the alpha series for months. We changed the accepted MAR channel ID to torbrowser-torproject-alpha as we are on an alpha channel. The assumption was that enough time passed since we changed it last time to torbrowser-torproject-release,torbrowser-torproject-alpha but it turns out that change did not get applied. Workaround: change the torbrowser-torproject-release in your update-settings.ini (in the Browser's code directory, which depends on you operating system) file to torbrowser-torproject-alpha and the update should get applied successfully. Alternatively, downloading a fresh alpha copy of Tor Browser works as well. Sorry for the inconvenience.

The full changelog since Tor Browser 10.0a5 is:

  • Windows + OS X + Linux
    • Update Firefox to 78.2.0esr
    • Update Tor Launcher to 0.2.23
    • Translations update
    • Update NoScript to 11.0.39
    • Bug 21601: Remove unused media.webaudio.enabled pref
    • Bug 40002: Remove about:pioneer
    • 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
    • OS X
      • Bug 40015: Tor Browser broken on MacOS 11 Big Sur
    • Build System
      • Windows + OS X + Linux
        • Bump Go to 1.13.15
      • Linux
        • Bug 40053: Also create the langpacks tarball for non-release builds

The full changelog since (Android) Tor Browser 10.0a4 is:

  • Android
    • Update Firefox to 68.12.0esr
    • Update HTTPS Everywhere to 2020.08.13
    • Update NoScript to 11.0.38
    • Update Tor to 0.4.4.4-rc

Comments

Please note that the comment area below has been archived.

Anonymous (not verified) said:

August 26, 2020

Permalink

Bug 21601: Remove unused media.webaudio.enabled pref
Bug 21601: Remove unused media.webaudio.enabled pref [torbutton]

Anonymous (not verified) said:

August 26, 2020

Permalink

[08-27 06:38:09] Torbutton NOTE: Exception on control port [Exception... "Component returned failure code: 0x804b000e (NS_ERROR_NET_TIMEOUT) [nsIBinaryInputStream.readBytes]" nsresult: "0x804b000e (NS_ERROR_NET_TIMEOUT)" location: "JS frame :: chrome://torbutton/content/torbutton.js :: torbutton_socket_readline :: line 652" data: no]

Anonymous (not verified) said:

August 26, 2020

Permalink

TypeError: event.target.closest is not a function UrlbarInput.jsm:2172:26
_on_mousedown resource:///modules/UrlbarInput.jsm:2172
handleEvent resource:///modules/UrlbarInput.jsm:367

Anonymous (not verified) said:

August 26, 2020

Permalink

NS_ERROR_XPC_JAVASCRIPT_ERROR_WITH_DETAILS: [JavaScript Error: "Invalid autocomplete selectedIndex" {file: "resource://gre/actors/AutoCompleteChild.jsm" line: 208}]'[JavaScript Error: "Invalid autocomplete selectedIndex" {file: "resource://gre/actors/AutoCompleteChild.jsm" line: 208}]' when calling method: [nsIAutoCompletePopup::selectedIndex] LoginManagerChild.jsm:174
observe resource://gre/modules/LoginManagerChild.jsm:174
handleEvent resource://gre/actors/AutoCompleteChild.jsm:126

Anonymous (not verified) said:

August 27, 2020

Permalink

NS_ERROR_FAILURE: Should pass a non-null uri URIFixup.jsm:281
getFixupURIInfo resource://gre/modules/URIFixup.jsm:281
_getUrlMetaData resource:///modules/UrlbarValueFormatter.jsm:150
_ensureFormattedHostVisible resource:///modules/UrlbarValueFormatter.jsm:105

anon (not verified) said:

August 27, 2020

Permalink

I just saw devtools.onboarding.telemetry.logged in my 9.5.4 and 10.0a6 with a value of true. Is this a bug?

Anonymous (not verified) said:

August 28, 2020

Permalink

[Exception... "Component returned failure code: 0x8050000e (NS_ERROR_ILLEGAL_INPUT) [nsIConverterInputStream.readString]" nsresult: "0x8050000e (NS_ERROR_ILLEGAL_INPUT)" location: "JS frame :: resource://gre/modules/WebRequestUpload.jsm :: readString :: line 245" data: no] WebRequestUpload.jsm:245:12
readString resource://gre/modules/WebRequestUpload.jsm:245
readAllStrings resource://gre/modules/WebRequestUpload.jsm:277
next self-hosted:1099
getParts resource://gre/modules/WebRequestUpload.jsm:296
next self-hosted:1099
parseMultiPart resource://gre/modules/WebRequestUpload.jsm:322
parseFormData resource://gre/modules/WebRequestUpload.jsm:398
createFormData resource://gre/modules/WebRequestUpload.jsm:439
createRequestBody resource://gre/modules/WebRequestUpload.jsm:529
runChannelListener resource://gre/modules/WebRequest.jsm:888
forEach self-hosted:1174
runChannelListener resource://gre/modules/WebRequest.jsm:834
observe resource://gre/modules/WebRequest.jsm:666

Anonymous (not verified) said:

August 28, 2020

Permalink

I have a buglet to report. If I use Tor Browser to navigate the file system (e.g., if I want to view files in /tmp), the page does not load properly. Instead, it seems to keep stopping and starting to load the page but it never actually shows the directory listing. I ran into this on 10.0a6 on linux64.

Wishing You We… (not verified) said:

August 28, 2020

Permalink

Tor Browser goes crazy trying to load my plain old HTML file which I use as a home page. And another plain text file I tried. Here's what happens.

Activity Monitor on Mac shows an impressive 109% CPU consumption rate for the "Tor BrowserCP file:// Content" process with Tor Browser process around 80-90%.

The Tor Browser window shows the X and Reload icon changing very fast. The tab label text is likewise cycling back and forth as fast as it can.

It seems to have issues with loading local text files. Pages retrieved via http(s) are fine.
__________
Also, has the rqef5a5mebgq46y5.onion address gone away? It doesn't seem to load any more. I preferred that to the less secure domain name option. :-)

Anonymous (not verified) said:

September 09, 2020

Permalink

NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIWindowsRegKey.create] InstallerPrefs.jsm:140
_openRegKey resource:///modules/InstallerPrefs.jsm:140
observe resource:///modules/InstallerPrefs.jsm:80

Stop touching the registry!

Anonymous (not verified) said:

September 14, 2020

Permalink

When I use a bridge, the circuit diagram in the "site information" menu on the URL bar displays the bridge's IP address. Isn't it dangerous to display a bridge's IP address in the main interface that is frequently visible to shoulder-surfers? You make it necessary to reveal it to reach the New Circuit button. Wouldn't it be safer to display the bridge's hashed fingerprint or a link to open the Tor preferences tab to view details?

Anonymous (not verified) said:

September 14, 2020

Permalink

Sorry, I don't know which post to write this in.

Dear web team, update the name "OS X" to "macOS" on the download page.

Anonymous (not verified) said:

September 15, 2020

Permalink

Double click on the video will switch it to full screen, does the video site get my real screen resolution?

Anonymous (not verified) said:

September 15, 2020

Permalink

14:48:00.212 NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIWebNavigation.goForward] 4 WebNavigationChild.jsm:57
goForward resource://gre/actors/WebNavigationChild.jsm:57
_wrapURIChangeCall resource://gre/actors/WebNavigationChild.jsm:36
goForward resource://gre/actors/WebNavigationChild.jsm:57
receiveMessage resource://gre/actors/WebNavigationChild.jsm:20

why? (not verified) said:

September 16, 2020

Permalink

Discussion for new alpha
https://blog.torproject.org/new-release-tor-browser-100a7
is closed, i try it here:

Why extensions-/storage-directory will be mixed again?
https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/320…
Switch back extensions.webextensions.ExtensionStorageIDB.enabled = true

Super idea? No, it was a bad idea and is a bad idea.
For programmers, ...i don't know. For me, for the user mixing is a useless, a not so good thing.
Separate the directory for extensions and storage, clearly laid out, is really better and there is no need to mess up this? I really see no need for this. No offense.