New Release: Tor Browser 10.5a4

by gk | November 18, 2020

Tor Browser 10.5a4 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 for desktop or Android instead.

This release updates Firefox to 78.5.0esr for desktop and Fenix to 83.0 for Android. Additionally, we update Tor to 0.4.5.1-alpha. This release includes important security updates both for desktop and Android users.

Note: Tor Browser 10.5 does not support CentOS 6.

The full changelog since Tor Browser 10.5a3 is:

  • All Platforms
    • Update Tor to 0.4.5.1-alpha
    • Bug 40212: Add new default bridge "PraxedisGuerrero"
  • Windows + OS X + Linux
    • Update Firefox to 78.5.0esr
  • Android
    • Update Fenix to 83.1.0
    • Bug 27002: (Mozilla 1673237) Always allow SVGs on about: pages
    • Bug 40137: Built-in https-everywhere storage is not migrated to idb
    • Bug 40152: Top Crash: android.database.sqlite.SQLiteConstraintException
    • Bug 40205: Replace occurrence of EmptyCString with 0-length _ns literal
    • Bug 40206: Disable the /etc/hosts parser
    • Translations update
  • Build System
    • OS X
    • Android
      • Bug 40211: Lower required build-tools version to 29.0.2
      • Bug 40126: Bump Node to 10.22.1 for mozilla83
      • Bug 40127: Update components for switch to mozilla83-based Fenix
Tags
tor-browser
tbb
tbb-10.5
Anonymous

Anonymous (not verified) said:

November 18, 2020

Permalink

Tor NOTICE: Bridge 'dktoke' has both an IPv4 and an IPv6 address. Will prefer using its IPv6 address ([2a0c:4d80:42:702::1]:27015) based on the configured Bridge address.

Anonymous

Anonymous (not verified) said:

November 18, 2020

Permalink

meek-azure is not working:
[11-18 19:36:27] Torbutton INFO: controlPort >> 650 STREAM 211 FAILED 0 0.0.2.0.$97700DFE9F483596DDA6264C4D7DF7641E1E39CE.exit:2 REASON=TIMEOUT CLIENT_PROTOCOL=UNKNOWN NYM_EPOCH=0 SESSION_GROUP=-2 ISO_FIELDS=SESSION_GROUP

Anonymous

Anonymous (not verified) said:

November 20, 2020

Permalink

I installed the Snowflake add-on in Firefox and when I click it it says it's enabled but how do I know that it's actually doing anything? I see this.

Anonymous

Anonymous (not verified) said:

November 22, 2020

Permalink

This update set Firefox.exe (Tor) to zero size, therefore I can't start Tor Browser. Updater.exe does nothing.

Is there any way to restore/extract Firefox.exe from update archive? Unless just reinstalling the whole bowser.

First, note this version is an alpha/development release (10.5a4, "a" for "alpha"). Most people are better off using the standard stable release.

It might be possible to extract the exe from the installer. Open the installer in an archive (zip) program. Firefox.exe is in the installer at /tor-browser_xx-XX/Browser/. Or you could reinstall the whole browser. Export/backup any customized bookmarks, settings, and bridges before reinstalling.

Don't bother digging into the update archives (mar file extension). First, they are deleted automatically after updating. Second, mar (Mozilla ARchive) is a custom file type:

1. https://wiki.mozilla.org/Software_Update:MAR#Why_not_use_ZIP_or_some_ot…
2. https://wiki.mozilla.org/Software_Update:Manually_Installing_a_MAR_file

Anonymous

Billy the kid (not verified) said:

November 28, 2020

Permalink

Anonymouse.org shows TOR HTTPS is broken when using email

When i use other browsers with anonymouse.org, it shows the https is fine. (A broken lock shows up when using tor)

Anonymous

Pete (not verified) said:

November 29, 2020

Permalink

This year I've started getting the "Something Went Wrong! Tor is not working in this browser." page. It started as a rare event, but is happening every day now.
It feels like the frequency is increasing with each update, but ...

Today I tried to open an .onion, after receiving the red page, and it actually worked. Checked the circuits for a few pages, and everything seems fine.

So if Tor is working properly, what is causing TorBrowser to display the red page (with increasing frequency)? Since nothing is really broken, I doubt it is related to updates, right?