New Release: Tor Browser 8.0

 

Update (09/07 10:15 UTC): We received reports of Tor Browser 8.0 crashing during start-up on older (10.9.x) macOS systems. This is tracked in bug 27482. The current Tor stable version, 0.3.3.9, is missing a patch to make it compatible with that old and unsupported (by Apple) macOS version. This will be fixed in the planned Tor Browser 8.0.1 release. Meanwhile, users affected by this bug can try the almost identical alpha release, 8.5a1, which is shipping a newer Tor version with this bug fixed. Sorry for the inconvenience.

For the past year, we have been collecting feedback on how we can make Tor Browser work better for you.

Tor Browser 8.0, our first stable release based on Firefox 60 ESR, is now available from the Tor Browser Project page and also from our distribution directory. This release is all about users first.

Tor Browser 8.0 comes with a series of user experience improvements that address a set of long-term Tor Browser issues you’ve told us about. To meet our users' needs, Tor Browser has a new user onboarding experience; an updated landing page that follows our styleguide; additional language support; and new behaviors for bridge fetching, displaying a circuit, and visiting .onion sites.

New User Onboarding

For the most part, using Tor is like using any other browser (and it is based on Firefox), but there are some usage differences and cool things happening behind the scenes that users should be aware of. Our new onboarding experience aims to better let you know about unique aspects of Tor Browser and how to maximize those for your best browsing experience.

Improved Bridge Fetching

For users where Tor is blocked, we have previously offered a handful of bridges in the browser to bypass censorship. But to receive additional bridges, you had to send an email or visit a website, which posed a set of problems. To simplify how you request bridges, we now have a new bridge configuration flow when you when you launch Tor. Now all you have to do is solve a captcha in Tor Launcher, and you’ll get a bridge IP. We hope this simplification will allow more people to bypass censorship and browse the internet freely and privately.

Better Language Support

Millions of people around the world use Tor, but not everyone has been able to use Tor in their language. In Tor Browser 8, we’ve added resources and support for nine previously unsupported languages: Catalan, Irish, Indonesian, Icelandic, Norwegian, Danish, Hebrew, Swedish, and Traditional Chinese.

Apart from those highlights, a number of other component and toolchains got an update for this major release. In particular, we now ship Tor 0.3.3.9 with OpenSSL 1.0.2p and Libevent 2.1.8. Moreover, we switched to the pure WebExtension version of NoScript (version 10.1.9.1) which we still need to provide the security slider functionality. Additionally, we start shipping 64bit builds for Windows users which should enhance Tor Browser stability compared to the 32bit bundles.

Providing this many improvements for our users could only be possible with collaboration between the Tor Browser team and Tor's UX team, Community team, Services Admin team, and our volunteers. We would like to thank everyone for working hard over the past year to bring all these new features to our users.

Known Issues

We already collected a number of unresolved bugs since Tor Browser 7.5.6 and tagged them with our ff60-esr keyword to keep them on our radar. The most important ones are listed below:

  • WebGL is broken right now.
  • We disable Stylo on macOS due to reproducibility issues we need to investigate and fix. This will likely not get fixed for Tor Browser 8, as we need some baking time on our nightly/alpha channel before we are sure there are no reproducibility/stability regressions. The tentative plan is to get it ready for Tor Browser 8.5.

 

Note: This release is signed with a new GPG subkey as the old one expired a couple of days ago. You might need to refresh your copy of the public part of the Tor Browser signing key before doing the verification. The fingerprint of the new subkey is 1107 75B5 D101 FB36 BC6C 911B EB77 4491 D9FF 06E2.

Give Feedback

This is only the beginning of our efforts to put users first. If you find a bug or have a suggestion for how we could improve this release, please let us know.

Changelog

The full changelog since Tor Browser 7.5.6 is:

  • All platforms
    • Update Firefox to 60.2.0esr
    • Update Tor to 0.3.3.9
    • Update OpenSSL to 1.0.2p
    • Update Libevent to 2.1.8
    • Update Torbutton to 2.0.6
      • Bug 26960: Implement new about:tor start page
      • Bug 26961: Implement new user onboarding
      • Bug 26962: Circuit display onboarding
      • Bug 27301: Improve about:tor behavior and appearance
      • Bug 27214: Improve the onboarding text
      • Bug 26321: Move 'New Identity', 'New Circuit' to File, hamburger menus
      • Bug 26100: Adapt Torbutton to Firefox 60 ESR
      • Bug 26520: Fix sec slider/NoScript for TOR_SKIP_LAUNCH=1
      • Bug 27401: Start listening for NoScript before it loads
      • Bug 26430: New Torbutton icon
      • Bug 24309: Move circuit display to the identity popup
      • Bug 26884: Use Torbutton to provide security slider on mobile
      • Bug 26128: Adapt security slider to the WebExtensions version of NoScript
      • Bug 27276: Adapt to new NoScript messaging protocol
      • Bug 23247: Show security state of .onions
      • Bug 26129: Show our about:tor page on startup
      • Bug 26235: Hide new unusable items from help menu
      • Bug 26058: Remove workaround for hiding 'sign in to sync' button
      • Bug 26590: Use new svg.disabled pref in security slider
      • Bug 26655: Adjust color and size of onion button
      • Bug 26500: Reposition circuit display relay icon for RTL locales
      • Bug 26409: Remove spoofed locale implementation
      • Bug 26189: Remove content-policy.js
      • Bug 26490: Remove the security slider notification
      • Bug 25126: Make about:tor layout responsive
      • Bug 27097: Add text for Tor News signup widget
      • Bug 21245: Add da translation to Torbutton and keep track of it
      • Bug 27129+20628: Add locales ca, ga, id, is, nb, da, he, sv, and zh-TW
      • Translations update
    • Update Tor Launcher to 0.2.16.3
      • Bug 23136: Moat integration (fetch bridges for the user)
      • Bug 25750: Update Tor Launcher to make it compatible with Firefox 60 ESR
      • Bug 26985: Help button icons missing
      • Bug 25509: Improve the proxy help text
      • Bug 26466: Remove sv-SE from tracking for releases
      • Bug 27129+20628: Add locales ca, ga, id, is, nb, da, he, sv, and zh-TW
      • Translations update
    • Update HTTPS Everywhere to 2018.8.22
    • Update NoScript to 10.1.9.1
    • Update meek to 0.31
      • Bug 26477: Make meek extension compatible with ESR 60
    • Update obfs4proxy to v0.0.7 (bug 25356)
    • Bug 27082: Enable a limited UITour for user onboarding
    • Bug 26961: New user onboarding
    • Bug 26962: New feature onboarding
    • Bug 27403: The onboarding bubble is not always displayed
    • Bug 27283: Fix first-party isolation for UI tour
    • Bug 27213: Update about:tbupdate to new (about:tor) layout
    • Bug 14952+24553: Enable HTTP2 and AltSvc
      • Bug 25735: Tor Browser stalls while loading Facebook login page
    • Bug 17252: Enable TLS session identifiers with first-party isolation
    • Bug 26353: Prevent speculative connects that violate first-party isolation
    • Bug 26670: Make canvas permission prompt respect first-party isolation
    • Bug 24056: Use en-US strings in HTML forms if locale is spoofed to english
    • Bug 26456: HTTP .onion sites inherit previous page's certificate information
    • Bug 26561: .onion images are not displayed
    • Bug 26321: Move 'New Identity', 'New Circuit' to File, hamburger menus
    • Bug 26833: Backport Mozilla's bug 1473247
    • Bug 26628: Backport Mozilla's bug 1470156
    • Bug 26237: Clean up toolbar for ESR60-based Tor Browser
    • Bug 26519: Avoid Firefox icons in ESR60
    • Bug 26039: Load our preferences that modify extensions (fixup)
    • Bug 26515: Update Tor Browser blog post URLs
    • Bug 26216: Fix broken MAR file generation
    • Bug 26409: Remove spoofed locale implementation
    • Bug 25543: Rebase Tor Browser patches for ESR60
    • Bug 23247: Show security state of .onions
    • Bug 26039: Load our preferences that modify extensions
    • Bug 17965: Isolate HPKP and HSTS to URL bar domain
    • Bug 21787: Spoof en-US for date picker
    • Bug 21607: Disable WebVR for now until it is properly audited
    • Bug 21549: Disable wasm for now until it is properly audited
    • Bug 26614: Disable Web Authentication API until it is properly audited
    • Bug 27281: Enable Reader View mode again
    • Bug 26114: Don't expose navigator.mozAddonManager to websites
    • Bug 21850: Update about:tbupdate handling for e10s
    • Bug 26048: Fix potentially confusing "restart to update" message
    • Bug 27221: Purge startup cache if Tor Browser version changed
    • Bug 26049: Reduce delay for showing update prompt to 1 hour
    • Bug 26365: Add potential AltSvc support
    • Bug 9145: Fix broken hardware acceleration on Windows and enable it
    • Bug 26045: Add new MAR signing keys
    • Bug 25215: Revert bug 18619 (we are not disabling IndexedDB any longer)
    • Bug 19910: Rip out optimistic data socks handshake variant (#3875)
    • Bug 22564: Hide Firefox Sync
    • Bug 25090: Disable updater telemetry
    • Bug 26127: Make sure Torbutton and Tor Launcher are not treated as legacy extensions
    • Bug 13575: Disable randomised Firefox HTTP cache decay user tests
    • Bug 22548: Firefox downgrades VP9 videos to VP8 for some users
    • Bug 24995: Include git hash in tor --version
    • Bug 27268+27257+27262+26603 : Preferences clean-up
    • Bug 26073: Migrate general.useragent.locale to intl.locale.requested
    • Bug 27129+20628: Make Tor Browser available in ca, ga, id, is, nb, da, he, sv, and zh-TW
      • Bug 12927: Include Hebrew translation into Tor Browser
      • Bug 21245: Add danish (da) translation
  • Windows
    • Bug 20636+10026: Create 64bit Tor Browser for Windows
      • Bug 26239+24197: Enable content sandboxing for 64bit Windows builds
      • Bug 26514: Fix intermittent updater failures on Win64 (Error 19)
      • Bug 26874: Fix UNC path restrictions failure in Tor Browser 8.0a9
      • Bug 12968: Enable HEASLR in Windows x86_64 builds
    • Bug 26381: Work around endless loop during page load and about:tor not loading
    • Bug 27411: Fix broken security slider and NoScript interaction on Windows
    • Bug 22581: Fix shutdown crash
    • Bug 25266: PT config should include full names of executable files
    • Bug 26304: Update zlib to version 1.2.11
    • Update tbb-windows-installer to 0.4
      • Bug 26355: Update tbb-windows-installer to check for Windows7+
    • Bug 26355: Require Windows7+ for updates to Tor Browser 8
  • OS X
    • Bug 24136: After loading file:// URLs clicking on links is broken on OS X
    • Bug 24243: Tor Browser only renders HTML for local pages via file://
    • Bug 24263: Tor Browser does not run extension scripts if loaded via about:debugging
    • Bug 22794: Don't open AF_INET/AF_INET6 sockets when AF_LOCAL is configured
  • Linux
    • Bug 22794: Don't open AF_INET/AF_INET6 sockets when AF_LOCAL is configured
    • Bug 25485: Unbreak Tor Browser on systems with newer libstdc++
    • Bug 20866: Fix OpenGL software rendering on systems with newer libstdc++
    • Bug 26951+18022: Fix execdesktop argument passing
    • Bug 24136: After loading file:// URLs clicking on links is broken on Linux
    • Bug 24243: Tor Browser only renders HTML for local pages via file://
    • Bug 24263: Tor Browser does not run extension scripts if loaded via about:debugging
    • Bug 20283: Tor Browser should run without a `/proc` filesystem.
    • Bug 26354: Set SSE2 support as minimal requirement for Tor Browser 8
  • Build System
    • All
      • Bug 26362+26410: Use old MAR format for first ESR60-based stable
      • Bug 27020: RBM build fails with runc version 1.0.1
      • Bug 26949: Use GitHub repository for STIX
      • Bug 26773: Add --verbose to the ./mach build flag for firefox
      • Bug 26319: Don't package up Tor Browser in the `mach package` step
      • Bug 27178: add support for xz compression in mar files
      • Clean up
    • Windows
      • Bug 26203: Adapt tor-browser-build/tor-browser for Windows
      • Bug 26204: Bundle d3dcompiler_47.dll for Tor Browser 8
      • Bug 26205: Don't build the uninstaller for Windows during Firefox compilation
      • Bug 26206: Ship pthread related dll where needed
      • Bug 26396: Build libwinpthread reproducible
      • Bug 25837: Integrate fxc2 into our build setup for Windows builds
      • Bug 27152: Use mozilla/fxc2.git for the fxc2 repository
      • Bug 25894: Get a rust cross-compiler for Windows
      • Bug 25554: Bump mingw-w64 version for ESR 60
      • Bug 23561: Fix nsis builds for Windows 64
        • Bug 13469: Windows installer is missing many languages from NSIS file
      • Bug 23231: Remove our STL Wrappers workaround for Windows 64bit
      • Bug 26370: Don't copy msvcr100.dll and libssp-0.dll twice
      • Bug 26476: Work around Tor Browser crashes due to fix for bug 1467041
      • Bug 18287: Use SHA-2 signature for Tor Browser setup executables
      • Bug 25420: Update GCC to 6.4.0
      • Bug 16472: Update Binutils to 2.26.1
      • Bug 20302: Fix FTE compilation for Windows with GCC 6.4.0
      • Bug 25111: Don't compile Yasm on our own anymore for Windows Tor Browser
      • Bug 18691: Switch Windows builds from precise to jessie
    • OS X
      • Bug 24632: Update macOS toolchain for ESR 60
      • Bug 9711: Build our own cctools for macOS cross-compilation
      • Bug 25548: Update macOS SDK for Tor Browser builds to 10.11
      • Bug 26003: Clean up our mozconfig-osx-x86_64 file
      • Bug 26195: Use new cctools in our macosx-toolchain project
      • Bug 25975: Get a rust cross-compiler for macOS
      • Bug 26475: Disable Stylo to make macOS build reproducible
      • Bug 26489: Fix .app directory name in tools/dmg2mar
    • Linux

I suggest that the Exec Director assign someone to update anything having to do with signing keys used by users to verify the latest release of TB, including

o checking certificates used at TP websites and generating new ones before they expire

o extending lifetime of signing subkeys or generating new subkeys

o updating the webpage listing the signing keys used by TP

o sending latest key information to keyservers (recommended keyservers would be a good item to add to the webpage, but might need to be updated regularly).

TP should not perform these critical tasks in such a haphazard manner, which tends to suggest TP doesn't think it matters because TP knows something users do not (yet), probably related to FBI's "Going Dark" monomania.

khled.8@hotmai.com

September 12, 2018

Permalink

How would I go about disabling connection though Tor network, while preserving other browser features? On Tor Browser 7.5.6 it was done by setting about:config => network.proxy.socks_remote_dns to false and setting Options => Advanced tab => Network to No Proxy (the recipe is borrowed from here), now it doesn't seem to work (Tor Browser simply looses network connection). Is it at all possible to achieve in Tor Browser 8?

Hm, this works for me. Just loading that page should trigger the problem, right? Which exact Windows bundle are you using (32bit? 64bit? locale?)? Does it work for you if you install the 64bit version of Tor Browser downloaded from our website to a different location?

Yeah, trying to load the page and the error pop-up. Iam using Windows 7/ 32 bit. Tried to install the 64 bit version as for tor........not possible, wont let me do that since i have a 32bit operating system.....unless there is a way to do that, which i dont know..............thanks in advance

Hm. Do you have some Antivirus/Firewall software installed that could be interfering here? If so, which and could you uninstall it for the time being to test whether that solves your problem? (disabling is often not enough)

someone stated it clearly, so i'm only going to echo his words. this version of Tor should have never been released yet, it's just not ready at all. you're putting a lot of users at risk for no good reason

NoScript has an icon for 'Reload' but NoScript does this
automatically!
How can one prevent this?

I want to know this too

I'm unable to run TBB 8.0 on my system apparently because it's based on FF Quantum. Is there a way to at least update only Tor in TBB 7.5.6? Simply overwriting the files from unzipped 8.0 didn't work.

Thats a good question,
are you running XP?

maybe open a ticket, thanks

Nem jó! Remeg a képernyő! Ledobál email írásnál, összeömlik, újraindul!
Gmail.hu nem jó! És ugyna olyan lassú!

How do you change tor identities on this version of Tor Browser?

Go to File-new identity

Why the option from onion drop-down menu for making new session has been gone?

That moved to the main menu (click on the three horizontal bar icon).

Bug 26321: Move 'New Identity', 'New Circuit' to File, hamburger menus....

No, it looks like sandwich not hamburger at first glance at the icon, it's the main menu of FireFox.

Is browserleaks dot com a useful website to check how your browser performs in terms of privacy and security?

when I click on the HTML5 Canvas Fingerprinting it knows I am using Torbrowser?

Uniqueness × False (Tor Browser signature)

We don't hide the fact that Tor Browser users are Tor Browser users. So, it's okay if any site is saying "You are a Tor Browser user". I don't think that website is a good one regarding the security track record of your browser. Nor do I think it is a good one for showing how you fare with respect to your privacy. I don't have a good one for recommendation right now, though, alas.

I am sad that you no longer support windows XP. After years of using it I know where every storage file is located which I can wipe after use. I find linux a pain up the butt to setup due to its constant need for your setup passwords. Now it seems I can't use any onion sites and I am not going to pay all that money for a new windows OS. So good luck and farewell.

I suspect the developers are using the latest computers and software and have forgotten half the world are still using older stuff. I just got an error message "your system is short on virtual memory please shut down and restart". I keep the paging file disabled and never have problems as I have at least 2gb RAM. Seems like many are having problems with this newest version.

You should be pushed to new hardware so you can be more easily tracked.

So, why is DDG still being used as the default search engine?
It seems to track searches done by users, which is bad from a privacy point of view.
https://www.stoutner.com/new-default-homepage-and-search-engine/

There' re probably other options available for a default engine, right?
Or does it come down to financial support (which is an understandable reason)?

Previously I was able to comment on news websites using my fake Facebook account if I allowed third party cookies in the Tor browser but now even if I allow third party cookies websites don't know I am logged in to Facebook and I am not able to comment on the news articles.

Warning:
For me the recent upgrade from TB7.x to 8.0 broke noscript.
Noscript says it was working but it clearly was not when a (luckily non malicious) website managed to run a jacascript.
I looked and the default setting in Noscript was Trust All
Check your settings and visit a safe site to test them.
Developers: Please make sure the package installs without compromising security.

"I looked and the default setting in Noscript was Trust All", yes, that's right. NoScript's default setting is "Trust All". See: https://support.torproject.org/tbb/tbb-34/ for some reasoning behind that.

bing translator doesn't work any more on this version of Tor Browser

That's https://trac.torproject.org/projects/tor/ticket/26624 and will be fixed in the upcoming 8.0.1 release.

20180915

Tor Browser 8.0 issue report:
don't wanna all blahs? go to "The issue" bellow

Had just downloaded and used today.

DISTRO: torbrowser-install-8.0_en-US.exe win32
MD5: acb44ca853c1c4a7359a53e6486cf723
TARGET PLAT: a very dodgy[1] windows 7 install

======

The issue:

It's openning SOME pdf files with the internal pdf
applet instead of downloading it - EVEN AFTER manually
configuring the Options-Apps-PDF-download option.

Dunno if it's FF or TB issue. PLS let FF team know!

I'm guessing it's failing when the target file have
a dodgy fname extension on it.
Those "fname templates" used to be downloaded normally
in the previous version.

======

[1] everybody putting their hands on, leaking through all
it's pores - evil forces sanctuary - (but TOR networking
seemed fine - no leaks).

The internal Tor Browser circuit viewer has never worked for me. I assume it has something to do with my usage of Qubes-Whonix (and perhaps it doesn't work on regular Whonix either). Is this a Tor Browser bug or a Whonix bug most likely? Exactly how does the circuit viewer work? Getting a new circuit works fine so it has some access.

I am inclined to say this is a Whonix bug but I am not very familiar with it, so it is hard to say. The circuit display works by keeping track of circuits per domain: Tor in Tor Browser uses different circuits for different domains and is asking via the control port about their status. On getting that back from Tor it constructs the display for the currently visible domain in the URL bar.

I tried to get my higih sierra mac to send data through the TOR browser. I used sock proxy server with 127.0.0.1 with port 9150. It works but the DNS used is the DNS picked up from my computer or entered manually on my computer. Can I use the TOR browser to sent my DNS request through.

Will the next stable release have the latest OpenSSL 1.1.1 and TLS 1.3?

I'm sorry but the new UI is really bad. I have no idea how to do anything now. And now I'm afraid I'm going to end up messing up something. However, I'm very pleased that Tor Browser is based on a newer and more secure Firefox base but I highly recommend that newer Tor Browser versions go through more rigorous UI review to prevent users from inadvertendly hurting themselves due to infamiliarity with the UI.

It works very well in my Fedora 25.Thanks!

Usually Tor browser blocked the images, but you could allow them ("allow in the future") clicking in the "palette" icon in the left of the navigation bar which appears when some image was first blocked.
Now I dont find this option anymore, and sites like whatsapp.web cant load the QR code image...
Like in my office where I need Tor to access this sites for proxy blocking reasons, I cant find a solution for this issue.
Someone?

До обновления было всё хорошо, работало без нареканий. После обновы стал висеть как фанера над парижем. Как откатить обнову? Бесит. Работала в 8-11 вкладках, сейчас тянет только 1 и то со скрипом!

Does this happen as well with the 64bit version of Tor Browser (assuming you were using the 32bit one on Windows)?

Can you please push my most dearest Mozilla Inc. to set
media.gmp-eme-adobe.enabled;false
media.gmp-manager.updateEnabled;false
in Firefox, too?
Would be very very nice.

I don't like ...unasked phone-home.

It looks like that the desktop icon for Tor Browser is missing on Linux.

I only use Relays and Guards that run current version of Tor and do not have the flag "Not Recommended". New version 8.0 allows for a new circuit but binds you to the same guard...that often is "Not Recommended". You guys don't need me to tell you that ALL things must be correct when establishing a secure connection. If we can not change the Guard when necessary it renders Tor useless as a (best of) security option. ----- hate to say this but the new design makes it difficult for new users to get Relay Information and as someone who pays attention to UI it seems intentional! Hard to check relay, no way to change Guard...this could conjure up conspiracy theories or resurrect old established ones. PLEASE advise as best way to change a complete circuit, including the Guard. -- Thank you

This seems like a rather pressing issue. I think i'm not alone in feeling like this should at least be addressed with a comment from the team..

Greetings,

I downloaded:
Tor Browser for Windows (64 bit)
from:
https://www.torproject.org/download/download-easy.html.en

I also downloaded the "sig".

gpg is not able to confirm the "sig", without the public key.

Whose public key do I need to find?
From where do I get the public key?

Thank you.