New Release: Tor Browser 8.5

[Update 5/22/2019 8:18 UTC: Added issue with saved passwords and logins that vanished to Known Issues section.]

Tor Browser 8.5 is now available from the Tor Browser download page and also from our distribution directory. The Android version is also available from Google Play and should be available from F-Droid within the next day.

This release features important security updates to Firefox.

After months of work and including feedback from our users, Tor Browser 8.5 includes our first stable release for Android plus many new features across platforms.

It's Official: Tor Browser is Stable on Android

Tor Browser 8.5 is the first stable release for Android. Since we released the first alpha version in September, we've been hard at work making sure we can provide the protections users are already enjoying on desktop to the Android platform. Mobile browsing is increasing around the world, and in some parts, it is commonly the only way people access the internet. In these same areas, there is often heavy surveillance and censorship online, so we made it a priority to reach these users.

Tor Browser for Android

We made sure there are no proxy bypasses, that first-party isolation is enabled to protect you from cross-site tracking, and that most of the fingerprinting defenses are working. While there are still feature gaps between the desktop and Android Tor Browser, we are confident that Tor Browser for Android provides essentially the same protections that can be found on desktop platforms.

Thanks to everyone working on getting our mobile experience into shape, in particular to Antonela, Matt, Igor, and Shane.

Note: Though we cannot bring an official Tor Browser to iOS due to restrictions by Apple, the only app we recommend is Onion Browser, developed by Mike Tigas with help from the Guardian Project.

Improved Security Slider Accessibility

Our security slider is an important tool for Tor Browser users, especially for those with sensitive security needs. However, its location behind the Torbutton menu made it hard to access.

Tor Browser Security

During the Tor Browser 8.5 development period, we revamped the experience so now the chosen security level appears on the toolbar. You can interact with the slider more easily now. For the fully planned changes check out proposal 101.

A Fresh Look

We made Tor Browser 8.5 compatible with Firefox's Photon UI and redesigned our logos and about:tor page across all the platforms we support to provide the same look and feel and improve accessibility.

Tor Browser icons

The new Tor Browser icon was chosen through a round of voting in our community.

We'd like to give a big thanks to everyone who helped make this release possible, including our users, who gave valuable feedback to our alpha versions.

Known Issues

Tor Browser 8.5 comes with a number of known issues. The most important ones are:

  1. While we improved accessibility support for Windows users during our 8.5 stabilization, it's still not perfect. We are in the process of finishing patches for inclusion in an 8.5 point release. We are close here.
  2. There are bug reports about WebGL related fingerprinting which we are investigating. We are currently testing a fix for the most problematic issue and will ship that in the next point release.
  3. The upgrade to Tor Browser 8.5 broke saved logins and passwords. We are investigating this bug and hope to provide a fix in an upcoming point release.

We already collected a number of unresolved bugs since releasing Tor Browser 8 and tagged them with our tbb-8.0-issues keyword to keep them on our radar. Check them out before reporting if you find a bug.

Give Feedback

In addition to the known issues, we are always looking for feedback about ways we can make our software better for you. If you find a bug or have a suggestion for how we could improve this release, please let us know.

Full Changelog

The full changelog since Tor Browser 8.0.9 is:

  • All platforms
    • Update Firefox to 60.7.0esr
    • Update Torbutton to 2.1.8
      • Bug 25013: Integrate Torbutton into tor-browser for Android
      • Bug 27111: Update about:tor desktop version to work on mobile
      • Bug 22538+22513: Fix new circuit button for error pages
      • Bug 25145: Update circuit display when back button is pressed
      • Bug 27749: Opening about:config shows circuit from previous website
      • Bug 30115: Map browser+domain to credentials to fix circuit display
      • Bug 25702: Update Tor Browser icon to follow design guidelines
      • Bug 21805: Add click-to-play button for WebGL
      • Bug 28836: Links on about:tor are not clickable
      • Bug 30171: Don't sync cookie.cookieBehavior and firstparty.isolate
      • Bug 29825: Intelligently add new Security Level button to taskbar
      • Bug 29903: No WebGL click-to-play on the standard security level
      • Bug 27290: Remove WebGL pref for min capability mode
      • Bug 25658: Replace security slider with security level UI
      • Bug 28628: Change onboarding Security panel to open new Security Level panel
      • Bug 29440: Update about:tor when Tor Browser is updated
      • Bug 27478: Improved Torbutton icons for dark theme
      • Bug 29239: Don't ship the Torbutton .xpi on mobile
      • Bug 27484: Improve navigation within onboarding (strings)
      • Bug 29768: Introduce new features to users (strings)
      • Bug 28093: Update donation banner style to make it fit in small screens
      • Bug 28543: about:tor has scroll bar between widths 900px and 1000px
      • Bug 28039: Enable dump() if log method is 0
      • Bug 27701: Don't show App Blocker dialog on Android
      • Bug 28187: Change tor circuit icon to torbutton.svg
      • Bug 29943: Use locales in AB-CD scheme to match Mozilla
      • Bug 26498: Add locale: es-AR
      • Bug 28082: Add locales cs, el, hu, ka
      • Bug 29973: Remove remaining stopOpenSecuritySettingsObserver() pieces
      • Bug 28075: Tone down missing SOCKS credential warning
      • Bug 30425: Revert armagadd-on-2.0 changes
      • Bug 30497: Add Donate link to about:tor
      • Bug 30069: Use slider and about:tor localizations on mobile
      • Bug 21263: Remove outdated information from the README
      • Bug 28747: Remove NoScript (XPCOM) related unused code
      • Translations update
      • Code clean-up
    • Update HTTPS Everywhere to 2019.5.6.1
    • Bug 27290: Remove WebGL pref for min capability mode
    • Bug 29120: Enable media cache in memory
    • Bug 24622: Proper first-party isolation of s3.amazonaws.com
    • Bug 29082: Backport patches for bug 1469916
    • Bug 28711: Backport patches for bug 1474659
    • Bug 27828: "Check for Tor Browser update" doesn't seem to do anything
    • Bug 29028: Auto-decline most canvas warning prompts again
    • Bug 27919: Backport SSL status API
    • Bug 27597: Fix our debug builds
    • Bug 28082: Add locales cs, el, hu, ka
    • Bug 26498: Add locale: es-AR
    • Bug 29916: Make sure enterprise policies are disabled
    • Bug 29349: Remove network.http.spdy.* overrides from meek helper user.js
    • Bug 29327: TypeError: hostName is null on about:tor page
    • Bug 30425: Revert armagadd-on-2.0 changes
  • Windows + OS X + Linux
    • Update OpenSSL to 1.0.2r
    • Update Tor Launcher to 0.2.18.3
      • Bug 27994+25151: Use the new Tor Browser logo
      • Bug 29328: Account for Tor 0.4.0.x's revised bootstrap status reporting
      • Bug 22402: Improve "For assistance" link
      • Bug 27994: Use the new Tor Browser logo
      • Bug 25405: Cannot use Moat if a meek bridge is configured
      • Bug 27392: Update Moat URLs
      • Bug 28082: Add locales cs, el, hu, ka
      • Bug 26498: Add locale es-AR
      • Bug 28039: Enable dump() if log method is 0
      • Translations update
    • Bug 25702: Activity 1.1 Update Tor Browser icon to follow design guidelines
    • Bug 28111: Use Tor Browser icon in identity box
    • Bug 22343: Make 'Save Page As' obey first-party isolation
    • Bug 29768: Introduce new features to users
    • Bug 27484: Improve navigation within onboarding
    • Bug 25658+29554: Replace security slider with security level UI
    • Bug 25405: Cannot use Moat if a meek bridge is configured
    • Bug 28885: notify users that update is downloading
    • Bug 29180: MAR download stalls when about dialog is opened
    • Bug 27485: Users are not taught how to open security-slider dialog
    • Bug 27486: Avoid about:blank tabs when opening onboarding pages
    • Bug 29440: Update about:tor when Tor Browser is updated
    • Bug 23359: WebExtensions icons are not shown on first start
    • Bug 28628: Change onboarding Security panel to open new Security Level panel
    • Bug 27905: Fix many occurrences of "Firefox" in about:preferences
    • Bug 28369: Stop shipping pingsender executable
    • Bug 30457: Remove defunct default bridges
  • Windows
    • Bug 27503: Improve screen reader accessibility
    • Bug 27865: Tor Browser 8.5a2 is crashing on Windows
    • Bug 22654: Firefox icon is shown for Tor Browser on Windows 10 start menu
    • Bug 28874: Bump mingw-w64 commit to fix WebGL crash
    • Bug 12885: Windows Jump Lists fail for Tor Browser
    • Bug 28618: Set MOZILLA_OFFICIAL for Windows build
    • Bug 21704: Abort install if CPU is missing SSE2 support
  • OS X
    • Bug 27623: Use MOZILLA_OFFICIAL for our builds
  • Linux
    • Bug 28022: Use `/usr/bin/env bash` for bash invocation
    • Bug 27623: Use MOZILLA_OFFICIAL for our builds
  • Android
  • Build System
    • All platforms
      • Bug 25623: Disable network during build
      • Bug 25876: Generate source tarballs during build
      • Bug 28685: Set Build ID based on Tor Browser version
      • Bug 29194: Set DEBIAN_FRONTEND=noninteractive
      • Bug 29167: Upgrade go to 1.11.5
      • Bug 29158: Install updated apt packages (CVE-2019-3462)
      • Bug 29097: Don't try to install python3.6-lxml for HTTPS Everywhere
      • Bug 27061: Enable verification of langpacks checksums
    • Windows
    • OS X
    • Linux
      • Bug 26323+29812: Build 32bit Linux bundles on 64bit Debian Wheezy
      • Bug 26148: Update binutils to 2.31.1
      • Bug 29758: Build firefox debug symbols for linux-i686
      • Bug 29966: Use archive.debian.org for Wheezy images
      • Bug 29183: Use linux-x86_64 langpacks on linux-x86_64
    • Android
      • Bug 29981: Add option to build without using containers
Anonymous

May 24, 2019

Permalink

Hello - recently Microsoft published WSL2-subsystem - https://en.wikipedia.org/wiki/Windows_Subsystem_for_Linux

Is it possible to create special TBB-version-or-what for WSL2? It brings many advantages - for instance -
1) hiding UserAgent (till now this issue is not solved)
2) using Linux-TBB in Windows, as Linux version probably better (with no need of extra Virtual machine)

Is it possible? How much time will cost this effort, is it really expansive?

Please look into the wiki - "Firefox for Linux running on WSL" :-)
So there should be good chances for TBB.

Meanwhile have no access to win10 for experiments unfortunately but windows users - are the most sufficient group of TBB users (AFAIR from tor-IRC), thus if WSL brings the value for them it is reasonable for tor-core-people to verify.

This is probably unrealistic but I'd love to see a version of Tor which works on Raspberry Pi. Or else a similar device available in most countries for a similar small cost which works with one of the existing Tor versions.

Why? Not sure really but I suspect that having the ability to torify a small cheap device (which you can put on a good hobby drone for example) might be useful to endangered people.

Making Tor for Raspberry Pi would probably require that project to show enthusiasm and some kind of special grant from somewhere to run a Summer of Pi type thing.

"Tor Messenger NG" is probably more urgent.

Pi need a bulky keyboard, monitor/TV, mouse for starters, and they are harder to set up. A burner phone or used old phone supporting LineageOS costs a little more but contains everything in a small, lightweight, enclosed case. It would be great to see Pi support, but there are better alternatives for endangered or transient people imo.

That would be dangerous because so many serious bugs have been published for versions earlier than 8.5.

I suppose you want to do that because something you are accustomed to doing appears to have broken with 8.5? If you explain the problem here, maybe someone can help you solve it.

Yes, if you accept the risk of not receiving security updates. You have to install the old version to a separate folder and immediately prevent it from checking for updates.
https://dist.torproject.org/torbrowser/
https://archive.torproject.org/tor-package-archive/torbrowser/
Hamburger menu -> Preferences -> Tor Browser Updates

Run only one instance at a time. Or so you don't accidentally do something unsafe, backup any personal files and delete the other tor-browser folders except for the version you want.

Tor Browser 8.5
Tor exits on startup (seen twice)

  1. <br />
  2. Unable to update the static FcBlanks: 0x0600<br />
  3. Unable to update the static FcBlanks: 0x0601<br />
  4. Unable to update the static FcBlanks: 0x0602<br />
  5. Unable to update the static FcBlanks: 0x0603<br />
  6. Unable to update the static FcBlanks: 0x06dd<br />
  7. Unable to update the static FcBlanks: 0x070f<br />
  8. Unable to update the static FcBlanks: 0x2028<br />
  9. Unable to update the static FcBlanks: 0x2029<br />
  10. Unable to update the static FcBlanks: 0xfff9<br />
  11. Unable to update the static FcBlanks: 0xfffa<br />
  12. Unable to update the static FcBlanks: 0xfffb</p>
  13. <p>(firefox:2071): Gtk-WARNING **: Theme parsing error: <data>:1:34: Expected ')' in color definition</p>
  14. <p>(firefox:2071): Gtk-WARNING **: Theme parsing error: <data>:1:77: Expected ')' in color definition<br />
  15. alloc factor 0,900000 0,900000<br />
  16. alloc factor 0,900000 0,900000<br />
  17. May 24 09:27:28.421 [notice] Tor 0.3.5.8 (git-5030edfb534245ed) running on Linux with Libevent 2.1.8-stable, OpenSSL 1.0.2r, Zlib 1.2.8, Liblzma N/A, and Libzstd N/A.<br />
  18. May 24 09:27:28.455 [notice] Tor can't help you if you use it wrong! Learn how to be safe at <a href="https://www.torproject.org/download/download#warning
  19. May" rel="nofollow">https://www.torproject.org/download/download#warning<br />
  20. May</a> 24 09:27:28.486 [notice] Read configuration file "/home/hurtta/.tor-browser/tor-browser_en-US/Browser/TorBrowser/Data/Tor/torrc-defaults".<br />
  21. May 24 09:27:28.526 [notice] Read configuration file "/home/hurtta/.tor-browser/tor-browser_en-US/Browser/TorBrowser/Data/Tor/torrc".<br />
  22. May 24 09:27:28.856 [notice] Opening Socks listener on 127.0.0.1:9150<br />
  23. May 24 09:27:28.857 [notice] Opened Socks listener on 127.0.0.1:9150<br />
  24. May 24 09:27:28.857 [notice] Opening Control listener on 127.0.0.1:9151<br />
  25. May 24 09:27:28.858 [notice] Opened Control listener on 127.0.0.1:9151<br />
  26. May 24 09:27:28.000 [notice] Parsing GEOIP IPv4 file /home/hurtta/.tor-browser/tor-browser_en-US/Browser/TorBrowser/Data/Tor/geoip.<br />
  27. May 24 09:27:31.000 [notice] Parsing GEOIP IPv6 file /home/hurtta/.tor-browser/tor-browser_en-US/Browser/TorBrowser/Data/Tor/geoip6.<br />
  28. May 24 09:27:33.000 [notice] Bootstrapped 0%: Starting<br />
  29. May 24 09:27:44.000 [notice] Starting with guard context "default"<br />
  30. May 24 09:27:44.000 [notice] New control connection opened from 127.0.0.1.<br />
  31. May 24 09:27:44.000 [notice] Bootstrapped 5%: Connecting to directory server<br />
  32. May 24 09:27:44.000 [notice] New control connection opened from 127.0.0.1.<br />
  33. May 24 09:27:45.000 [notice] Bootstrapped 10%: Finishing handshake with directory server<br />
  34. May 24 09:27:45.000 [notice] Bootstrapped 80%: Connecting to the Tor network<br />
  35. May 24 09:27:45.000 [notice] Bootstrapped 85%: Finishing handshake with first hop<br />
  36. May 24 09:27:45.000 [notice] New control connection opened from 127.0.0.1.<br />
  37. May 24 09:27:45.000 [notice] Bootstrapped 90%: Establishing a Tor circuit<br />
  38. May 24 09:27:46.000 [notice] Bootstrapped 100%: Done<br />
  39. May 24 09:28:12.000 [notice] New control connection opened from 127.0.0.1.<br />
  40. May 24 09:28:12.000 [notice] Owning controller connection has closed -- exiting now.<br />
  41. May 24 09:28:12.000 [notice] Catching signal TERM, exiting cleanly.<br />

Tor Browser then complain that "Tor unexpectly exited".
Then need presess Restart tor
(This starts tor with disabled network set. So it does not directly work then. So then cancel and then connect.)

Is this running on Linux? Can you provide more information about your operating system?

Is this running on Linux?

I think that quoted log said that it is linux ...

There was: -------

May 24 09:27:28.421 [notice] Tor 0.3.5.8 (git-5030edfb534245ed) running on Linux with Libevent 2.1.8-stable, OpenSSL 1.0.2r, Zlib 1.2.8, Liblzma N/A, and Libzstd N/A.

------

This is

Ubuntu 16.04.6 LTS

Linux 4.4.0-148-generic i686
(or 4.4.0-145-generic )

MemTotal: 1013224 kB

Happened third time.

This time I pressed quit after "Tor unexpectly exited" message
and started again.

Yes, is Linux as it is very cleary visible on log:

May 25 12:09:53.889 [notice] Tor 0.3.5.8 (git-5030edfb534245ed) running on Linux with Libevent 2.1.8-stable, OpenSSL 1.0.2r, Zlib 1.2.8, Liblzma N/A, and Libzstd N/A.

Probably happens on first time after boot. Timing related?

Ubuntu 16.04.6 LTS

On previous version of Tor Browser I got sometimes "Something
went wrong" -message to Tor Browser startup screen, but
it worked however.

[Edit: cut the post a bit, GK]

So, this is not your first version of Tor Browser where this is happening? Do you know when this started? If not, could you test older versions downloaded from: https://archive.torproject.org/tor-package-archive/torbrowser/ and figure out what the first version is where Tor is crashing for you?

Tor Browser 8.5 is first which wrote "tor unexpectly exited" on startup.
Some other Tor Browsers some times on browser Windows wrote "Something went wrong" or similar but when I wrote address to URL bar it worked so there was tor running.

Tor Browser 8.5 does not come with a new Tor version, so I suspect this happened already with previous Tor Browser versions. Could you figure out when this started (see the above link to older Tor Browser versions)?

> Some other Tor Browsers some times on browser Windows wrote
> "Something went wrong" or similar but when I wrote address to URL bar it
> worked so there was tor running.

OK. Now this (Tor Browser 8.5) said

----
Something Went Wrong!

Tor is not working in this browser.
-----

I type https://blog.torproject.org/ to url bar. This works normally. Tor is not exited or crashed.

Yes. This is not new behaviour. I have seen this earlier (with other Tor Browsers, not this).

----

And https://check.torproject.org/ says

Congratulations. This browser is configured to use Tor.

Your IP address appears to be: 51.15.117.50

> first version is where Tor is crashing for you?
Are you absolutely sure that its tor which is cashing here?

After all (as you seen) tor was telling that control connection is closed.

May 25 12:10:06.000 [notice] Bootstrapped 90%: Establishing a Tor circuit
May 25 12:10:07.000 [notice] Bootstrapped 100%: Done
May 25 12:10:28.000 [notice] New control connection opened from 127.0.0.1.
May 25 12:10:29.000 [notice] Owning controller connection has closed -- exiting now.
May 25 12:10:29.000 [notice] Catching signal TERM, exiting cleanly.

What is causing

May 25 12:10:29.000 [notice] Owning controller connection has closed -- exiting now.
May 25 12:10:29.000 [notice] Catching signal TERM, exiting cleanly.

?

That said, yes, if you get the notice that Tor unexpectedly exited I'd assume it is crashing. But I am still not sure I understand what is happening on your side. Thus, I might have this wrong.

This closing of control connection seems happen just before something (launcer?) prepares open tor Browsers initial window (about:tor).
At least one time there was some other error message on (launcer?) screen before it was replaced with message that tor is exited unexpectly. Message was visible so short time that I didn't read it.

( I answered once, but it is not visible. )

Window shows some message

Unable ....

which is replaced with

Tor unexpectedly exited.

Verbose logging shows

Jun 01 16:02:40.000 [notice] Bootstrapped 5%: Connecting to directory server
Jun 01 16:02:40.000 [notice] Bootstrapped 10%: Finishing handshake with directory server
Jun 01 16:02:40.000 [notice] Bootstrapped 80%: Connecting to the Tor network
Jun 01 16:02:40.000 [notice] Bootstrapped 85%: Finishing handshake with first hop
Jun 01 16:02:40.000 [notice] New control connection opened from 127.0.0.1.
Jun 01 16:02:40.000 [notice] Bootstrapped 90%: Establishing a Tor circuit
Jun 01 16:02:41.000 [notice] Bootstrapped 100%: Done
Jun 01 16:03:03.000 [notice] New control connection opened from 127.0.0.1.
Jun 01 16:03:03.000 [notice] Owning controller connection has closed -- exiting now.
Jun 01 16:03:03.000 [notice] Catching signal TERM, exiting cleanly.

So tor was exited because controller connection was closed.

There was some other message on window before tor was exited.
I guess that was related to that why controller connection was closed.

Yes, probably. I wonder if you could get us the problematic message as that would help us diagnose the issue further.

. I wonder if you could get us the problematic message as that would help us diagnose the issue further.

On https://blog.torproject.org/new-release-tor-browser-853 I wrote

Tor launcer(?) probably told

Unable to retrieve settings.

And then it was replaced with

Tor unexpectedly exited. ...

Control connection was closed:

Jul 04 05:31:17.000 [notice] Bootstrapped 100%: Done
Jul 04 05:31:35.000 [notice] New control connection opened from 127.0.0.1.
Jul 04 05:31:35.000 [notice] Owning controller connection has closed -- exiting now.
Jul 04 05:31:35.000 [notice] Catching signal TERM, exiting cleanly.

This is

Tor Browser 8.5.3

and

Tor browser 8.5.

Tor launcer: (Window title: Connect to Tor)

Unable to retrieve tor settings.

Immediately replaced with

Tor unexpectedly exited....

Restarting Tor will not close your browser tabs.

There is now yet browser window or tabs opened.

Console tells:

Jul 06 16:07:59.000 [notice] Bootstrapped 100%: Done
Jul 06 16:07:59.000 [notice] New control connection opened from 127.0.0.1.
Jul 06 16:07:59.000 [notice] Owning controller connection has closed -- exiting now.
Jul 06 16:07:59.000 [notice] Catching signal TERM, exiting cleanly.

Do you know when this started?

Tor Browser 8.5

If not, could you test older versions downloaded from: https://archive.torproject.org/tor-package-archive/torbrowser/ and figure out what the first version is where Tor is crashing for you?

" Owning controller connection has closed -- exiting now." so far is NOT happened with Tor Browser 8.0.9

Okay, can you test which of the 8.5aX alpha versions is the first where you see it?

Okay, can you test which of the 8.5aX alpha versions is the first where you see it?

Happens with tor-browser-linux32-8.5a10_en-US.tar.xz

XXXXXXXXXX:~$ torbrowser-8.5a10 --verbose
...
Jun 23 09:54:47.814 [notice] Tor 0.4.0.2-alpha (git-feb744f0d488a0e5) running on Linux with Libevent 2.1.8-stable, OpenSSL 1.0.2r, Zlib 1.2.8, Liblzma N/A, and Libzstd N/A.
...
Jun 23 09:54:58.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
Jun 23 09:55:17.000 [notice] Bootstrapped 100% (done): Done
Jun 23 09:55:17.000 [notice] New control connection opened from 127.0.0.1.
Jun 23 09:55:17.000 [notice] Owning controller connection has closed -- exiting now.
Jun 23 09:55:17.000 [notice] Catching signal TERM, exiting cleanly.

I try figure which is best to catch this. It is slow to test that this happens and much more slow to test that this does not happen.

binary search perhaps is not best

8.5a10 is the first release for that bug? Hm. It contains only a new NoScript version and a security update from Firefox with two critical fixes. Those do not seem to be related with your problem, though...

I'm still testing tor browser 8.5a7

so far I have not seen "Owning controller connection has closed -- exiting now."

when starting tor browser 8.5a7

but that is slow test that something does NOT happen.

That have happened several times with tor browser 8.5.3 on same time period.

Okay, can you test which of the 8.5aX alpha versions is the first where you see it?

"Owning controller connection has closed" on startup is not seen on tor browser 8.5a7 so far.

Okay, can you test which of the 8.5aX alpha versions is the first where you see it?

Update:

"Owning controller connection has closed" on startup seen now with tor-browser-linux32-8.5a9_en-US.tar.xz

Jul 03 10:30:03.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
Jul 03 10:30:04.000 [notice] Bootstrapped 100% (done): Done
Jul 03 10:30:21.000 [notice] New control connection opened from 127.0.0.1.
Jul 03 10:30:21.000 [notice] Owning controller connection has closed -- exiting now.
Jul 03 10:30:21.000 [notice] Catching signal TERM, exiting cleanly.

I tried tor-browser-linux32-8.5a7_en-US.tar.xz before that and have not seen
"Owning controller connection has closed" on startup with that version.

can you test which of the 8.5aX alpha versions is the first where you see it?

"Owning controller connection has closed" on startup NOT seen so far with Tor Browser 8.5a8.

Why in new version dont working certificats from previous version?

Could you provide some more information about the issue you're experiencing?

Maybe you hit https://trac.torproject.org/projects/tor/ticket/30565? Does flipping security.nocertdb to false in your about:config (and restarting) help?

It took me all week to find time just to READ the list of bug fixes incorporated into 8.5. Everyone should try to do this once in a while just to get some impression of how much hard work goes into each release. And wow, oh my gosh, web browsers certainly are complex things! As such inherently they tend to collect bugs, all of which need to be found and fixed. Which involves a lot of work. And you guys are absolutely the finest most hard working people EVER!

Thanks so much for everything you do! 8> 8>

I have been thinking about the big picture and despite the shock of the recent Mozilla NoScript fiasco things are just at this moment actually moving our way, I think. Imagine that!

Considering how tiny Tor Project and Tails Project are, and how powerful and well-funded and monomaniacally aggressive our many political and technical adversaries are, it is easy for the FUD-sayers to create the impression that "Tor is hopelessly broken" [sic] or that "Tails cannot possibly protect whistle-blowers" [sic].

But look at all the huge positive developments just in the past few months:

o Tor Android is here and appears to be working in the real world,

o Mozilla is seriously interested in helping Tor to make it feasible to incorporate Tor into FF by default, which would grow our user base by two or more orders of magnitude,

o Tails has quickly incorporated changes addressing the latest attacks exploiting speculative execution,

o Tails (based on Debian) has already successfully incorporated Buster (Debian newstable); contrast the painful transition to Squeeze a few years ago,

o Tor Project and Mozilla have been successfully coordinating FF ESR and TB releases,

o the general population is suddenly waking up to the dangers posed by entities like Cambridge Analytica, Facebook, Amazon, Google (yes, I just bit a hand which sometimes feed us),

o most human rights workers now appreciate (I think) the danger posed by companies such as NSO Group to their personal safety, and are eager to adopt tools like Tails to keep themselves and their associates safer,

o the workforce at Google and Amazon and even Microsoft are in serious revolt against some of the worst abuses by these predatory monopolistic juggernauts (is it too much to hope for a revolt among NSA contractors? or at least a boycott of NSA by US universities?),

o Tor Project has new leadership but has shown excellent continuity in its stated goals and in geographical diversification and working toward a grassroots support funding model.

The one really big thing which is still missing, I think, is starting over with "Tor Messenger NG". The first attempt got written into a corner, as I understand, but that's how we learn to do it right, and I think that if TP can offer a chat which is fairly device independent and fairly secure and anonymous, that would be just about the biggest positive development since Tor Browser itself.

Re:https://blog.torproject.org/comment/281910#comment-281910
I had multiple tabs open and one tab a search engine DuckDuckGo onion had no routing information. Using tails. This version of TB. Also when I looked in my bookmarks folder it's Icon was visible there when usually they are not.

Where do the bookmarks come into play? You have the onion search engine link bookmarked? And had that bookmarked link open in a new tab?

All password and login are gone please solve the problem.. thank you so much

See the blog update I posted a couple of days above: It's likely you hit https://trac.torproject.org/projects/tor/ticket/30565 and we'll have a fix for that in the upcoming release. Meanwhile you can get everything back by flipping security.nocertdb to false in your about:config and restart. Sorry for the inconvenience.

Re: https://blog.torproject.org/comment/282011#comment-282011

I have previously installed the TBB on Windows Subsystem For Linux but Windows did something to it now so it doesn't work anymore. I tried to install apt-transport-tor and use tor to download my programs but not working. Too many secrets I guess---Windows don't like that.

RE: https://blog.torproject.org/comment/282022#comment-282022
It still works to run Tor Browser in Windows Subsystem for Linux. This post is from Debian on WSL.
Regards.

And that is good! BTW Did you checked UserAgent (from JS and from browser)? I hope information about OS now is not leaked.

In any case this WSL can be valuable and thus - interesting for TBB users. So information about should be published!

The only serious concern probably is about Win10 telemetry and screenshots (Win10 doing such) that Microsoft may send to itself :-)

I now see a vertical scroll bar in about:tor.

Where? Do you have a screenshot showing the issue, maybe?

Okay, yes. That's nothing to worry about and probably caused by the additional "Donate Now" item on that page.

Blind or the security slider is gone and "Security Level" is accessible only
in about:preferences#privacy?1

Not blind, that's the new way of doing things. See: https://gitweb.torproject.org/tor-browser-spec.git/tree/proposals/101-s… for an in-depth explanation of the security settings redesign idea.

I have been enjoying the security settings redesign quite a lot. Its so handy to just glance at the upper right hand corner of the browser and immediately check the security level without dropping open the menu. Depending on the site I will connect with, I frequently change the security level. Its easy to forget to reset it to safest. I liked the former slider, but I like your new design best. Thank you.

> Depending on the site I will connect with, I frequently change the security level. Its easy to forget to reset it to safest. I liked the former slider, but I like your new design best.

Me too. One important thing to remember when you do this is that security level changes affect all open tabs, so it is a good idea to get in the habit of choosing new identity just before you change the security level (especially if downgrading it).