The Tor Browser Team is proud to announce the first stable release in the 7.0 series. This release is available from the Tor Browser Project page and also from our distribution directory.

This release brings us up to date with Firefox 52 ESR which contains progress in a number of areas:

Most notably we hope having Mozilla's multiprocess mode (e10s) and content sandbox enabled will be one of the major new features in the Tor Browser 7.0 series, both security- and performance-wise. While we are still working on the sandboxing part for Windows (the e10s part is ready), both Linux and macOS have e10s and content sandboxing enabled by default in Tor Browser 7.0. In addition to that, Linux and macOS users have the option to further harden their Tor Browser setup by using only Unix Domain sockets for communication with tor. Update (June 8, 8:00 UTC): As the last point caused some confusion: enabling Unix Domain sockets alone does not harden Tor Browser. One needs that *and* additional sandboxing mechanisms that prevent communication over TCP/IP.

The highlights in our tracking and fingerprinting resistance improvements are: cookies, view-source requests and the Permissions API are isolated to the first party URL bar domain now to enhance our tracking related defenses. On the fingerprinting side we disabled and/or patched several new features, among them WebGL2, the WebAudio, Social, SpeechSynthesis, and Touch APIs, and the MediaError.message property.

WIth the switch to ESR 52 come new system requirements for Windows and macOS users: On Windows Tor Browser 7.0 won't run on non-SSE2 capable machines anymore. On Apple computers OS X 10.9 is now the minimum system requirement.

Besides new system requirements for Windows and macOS users, there are some known issues with Tor Browser 7.0 as well:

Apart from switching to the new Firefox ESR and dealing with related issues we included a new Tor stable version (0.3.0.7) and updated our NoScript (5.0.5) and HTTPS-Everywhere versions (5.2.17).

We updated our toolchains during the ESR transition as well. In particular we retired the old GCC-based one for our macOS cross-compilation and rely solely on clang/cctools now.

The full changelog since Tor Browser 6.5.2 is:

Today is 7th of July but I still cannot see new tor version in official tor repository for Debian. Issue with ALSA is very sad, too sad. Pulseaudio, like systemd, are the things which were always avoided on system-critical OSes.

When I open youtube popup says me that I must install pulseaudio to het sound working, button with help redirects me on the page: link. However, there is no this page. You should fix the link.

P.S. Preview in commenting in tor-blog with enabled JS is not working. It doesn't show formatted text, only its source.

Thank guys, great job!

Quite often when I opened Tor Browser, there was a warning sign of a yellow triangle with an exclamation mark in the "Open Settings" button on the connecting dialog box. When clicking on that, it showed a "Copy to clipboard" button.

May anyone tell me a little bit about this warning? I'm wondering if my connection was compromised and no longer anonymous in these cases. This time, for example, the content I got from the "Copy to clipboard" was:

06/07/2017 12:58:58.500 [NOTICE] Bootstrapped 5%: Connecting to directory server 06/07/2017 12:58:58.500 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server 06/07/2017 12:58:59.200 [WARN] Proxy Client: unable to connect to 68.45.52.117:40365 ("general SOCKS server failure") 06/07/2017 12:59:00.100 [NOTICE] Bootstrapped 15%: Establishing an encrypted directory connection 06/07/2017 12:59:00.100 [WARN] Proxy Client: unable to connect to 68.45.52.117:40365 ("general SOCKS server failure") 06/07/2017 12:59:00.300 [NOTICE] Bootstrapped 20%: Asking for networkstatus consensus 06/07/2017 12:59:01.200 [NOTICE] Bootstrapped 25%: Loading networkstatus consensus 06/07/2017 12:59:08.900 [NOTICE] Bootstrapped 80%: Connecting to the Tor network 06/07/2017 12:59:08.900 [NOTICE] Bootstrapped 90%: Establishing a Tor circuit 06/07/2017 12:59:10.100 [NOTICE] Tor has successfully opened a circuit. Looks like client functionality is working. 06/07/2017 12:59:10.100 [NOTICE] Bootstrapped 100%: Done 06/07/2017 12:59:11.600 [NOTICE] New control connection opened from 127.0.0.1. 06/07/2017 12:59:11.700 [NOTICE] New control connection opened from 127.0.0.1. 06/07/2017 13:00:18.400 [WARN] Proxy Client: unable to connect to 178.62.29.226:9443 ("general SOCKS server failure") 06/07/2017 13:00:19.700 [WARN] Proxy Client: unable to connect to 178.62.29.226:9443 ("general SOCKS server failure") 06/07/2017 13:00:19.800 [NOTICE] new bridge descriptor 'Unnamed' (fresh): $958ACD25DACDDE1CF6FE463FBFA28BFEB8BFF82B~Unnamed at 194.132.209.61 06/07/2017 13:01:06.100 [WARN] Proxy Client: unable to connect to 108.61.191.37:9443 ("general SOCKS server failure") 06/07/2017 13:01:06.100 [WARN] Proxy Client: unable to connect to 5.35.86.79:39563 ("general SOCKS server failure") 06/07/2017 13:01:06.100 [WARN] Proxy Client: unable to connect to 35.185.60.254:9443 ("general SOCKS server failure") 06/07/2017 13:01:06.100 [WARN] Proxy Client: unable to connect to 139.59.147.112:36715 ("general SOCKS server failure") 06/07/2017 13:01:06.100 [WARN] Proxy Client: unable to connect to 104.153.209.217:25447 ("general SOCKS server failure") 06/07/2017 13:01:06.100 [WARN] Proxy Client: unable to connect to 185.163.45.19:57339 ("general SOCKS server failure")

If you are using Add-ons with filter lists in Tor Browser 7.0, for example uBlock Origin, Adblock Plus etc. ,it takes extremely long to start the browser In Tor Browser 6.5 and previous this was not really an issue. It was only a small delay barely noticeable. This problem is new to version 7.0. I hope you can look into that.

How to reproduce: - Use a newely installed Tor Browser v. 7.0 - Install uBlock Origin - See how the browser will freeze for some seconds. - Restart the Browser and see how it will take extremely long to startup

I'm still hoping for 64-bit versions of Tor and the Tor Browser for Windows; maybe they'll show up alongside the ESR59-based Tor Browser, because Firefox 53+ no longer supports Vista, and most installations of Windows 7+ are 64-bit, so they will be able to benefit from 64-bit software.

my system is not supported.. meanwhile what can I do? updating only TOR instead of tor browser, but how do it? help please 😀

Go here to read the rest:

Tor Browser 7.0 is released | The Tor Blog