New Release: Tor Browser 10.5a15

Tor Browser 10.5a15 is now available from the Tor Browser 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 version updates Firefox to 78.10esr and Fenix to 88.1.1. In addition, Tor Browser 10.5a15 updates Tor to 0.4.6.2-alpha. This version includes important security updates to Firefox for Desktop and security updates for Android.

Warning:
Tor Browser Alpha does not support version 2 onion services. Tor Browser (Stable) will stop supporting version 2 onion services later this year. Please see the previously published deprecation timeline regarding Tor version 0.4.6. Migrate your services and update your bookmarks to version 3 onion services as soon as possible.

Note: This version is not completely reproducible. We are investigating non-determinism in the Android Tor Browser build. Tor Browser for Windows, macOS and Linux are reproducible.

The full changelog since Tor Browser 10.5a14:

  • All Platforms
    • Update Tor to 0.4.6.2-alpha
  • Windows + OS X + Linux
    • Update Firefox to 78.10.0esr
    • Bug 40408: Disallow SVG Context Paint in all web content
  • Android
    • Update Fenix to 88.1.1
    • Bug 40051: Rebase android-components patches for Fenix 88
    • Bug 40158: Rebase Fenix patches to Fenix 88.1.1
    • Bug 40399: Rebase 10.5 patches on 88.0
  • Build System
    • All Platforms
      • Update Go to 1.15.11
    • Android
      • Bug 40259: Update components for mozilla88-based Fenix
Anonymous

April 27, 2021

Permalink

Windows + OS X + Linux

Bug 40259: Update components for mozilla88-based Fenix

That's Android only.

Anonymous

April 27, 2021

Permalink

4/27/21, 15:57:42.781 [WARN] Not attempting connection to [scrubbed]:8443 because the network would reject it. Are you trying to send Tor traffic over Tor? This traffic can be harmful to the Tor network. If you really need it, try using a bridge as a workaround.
plse help you !!!

I'm cli tor is BridgeRelay, I'm Try 'cli tor' Socks5Proxy 127.0.0.1:9150 -> Tor Browser->internet.
error:
5/24/21, 03:50:07.824 [WARN] Not attempting connection to [scrubbed]:9001 because the network would reject it. Are you trying to send Tor traffic over Tor? This traffic can be harmful to the Tor network. If you really need it, try using a bridge as a workaround.
why? help me
sould my what to do ?

Anonymous

April 27, 2021

Permalink

Attention Android users:

If you experience regular or repeated crashes, please install Scoop from f-droid. Scoop monitors app crashes and captures a stack trace, which contains information that can be extremely helpful for developers. If Scoop detects a crash, please file a bug report and include a copy of the stack trace with it.

As per the instructions, non-root users must run the following command on the device in order to enable Scoop. You do this from a desktop using the adb shell command, or from the device itself using a terminal emulator app such as Termux or many others. Neither method requires root.

pm grant taco.scoop android.permission.READ_LOGS

Great information. Your comment about Scoop and/or instructions to use logcat ought to be made into a bug ticket to get the instructions added to Tor Project's support answer for how to view the log but for Tor Browser Android.

Here are some older questions about logs on Android, etc.

https://blog.torproject.org/comment/291452#comment-291452
https://blog.torproject.org/comment/291586#comment-291586

  1. Error: Permission denied to access property "call" js:171:1963<br />
  2. TypeError: window.Foundation is undefined js:1:770<br />
  3. TypeError: $(...).foundation is not a function commit_browser:1389:21

NoScript rewrote/refactored something about nested permissions...

Anonymous

June 04, 2021

Permalink

> Tor Browser Alpha does not support version 2 onion services.

It's working for me...? I was trying to see if an Onion-Location header pointing to a v2 address would be followed by a version that doesn't support v2, but lo and behold, it redirects and v2 comes right up. Also tried manually entering a v2 address and it works. What gives? 10.5a15, Linux, installed from tarball.