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
Anonymous

September 05, 2018

Permalink

I know the User-Agent spoofing is imperfect, but an imperfect mask is better than no mask! The actual OS in the User-Agent string will only further distinguish and deanonymize the user-base.
Otherwise thanks for your work!

I'm glad the first comment notes about the UA change, which is actually a privacy *regression* since for users with JS disabled the real OS will be leaked vs. the situation in the previous Tor releases (7.x). Also not everyone does JS based OS detection (only a few do it) but *most* do log the UA. One can imagine that the UA is all it takes to correlate between two users with similar traits in a low volume site (example writing patterns, social graph, ...) [and even a high volume one like Twitter with some more work].

Please Tor Browser devs fix this issue since it's really the only bad thing in an otherwise almost perfect stable release.

Here's a real life example: Leaker 1 uses securedrop to send a leak from an organization A where he work and his Mac user agent leaks. Organization A finds everyone has access to the leaked docs and finds the ones who have a Mac. Depending on the situation they may actually narrow it down to a few people or just one, all because the browser doesn't even try to spoof the OS.

Hi,
Agree.
In addition: not masking the UA also has big usability implications on sites that mistakenly or over-cautiously believe they only supports Windows, MAC, iOS and Android. On *many* such sites a TorBrowser that pretends it is running on Windows works just fine. If you reveal another rare OS in the UA the site says that it only support iOS and Android or other such nonsense. They just do not know that Firefox on a rare OS is a Firefox.

If one is to enter a fake UA in TorBrowser 8.0 so that the site accepts one as running on a popular Windows OS, which string should one currently use?

Thanx for the great work!

I just checked my UserAgent and it seems fine, the current one is:

Mozilla/5.0 (Windows NT 6.1; rv:60.0) Gecko/20100101 Firefox/60.0

Back in version 7.5.6 it was:

Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Firefox/52.0

I believe it shows your system as being Windows NT 6.1 regardless of what system you're using. Correct me if I am wrong.

Anonymous

September 05, 2018

Permalink

Happy to finally see a TAILS announcement on the Blog!

However, unlike most other entries, I notice the TAILS announcements here are not open for comments. Why not? What a shame.

Congrats on Tor Browser 8.0! Thanks for posting the changelog here. <3

> I notice the TAILS announcements here are not open for comments.

Yes.

> Why not?

Speculation:

1. Years ago, Tails, which is mostly based in Western Europe, had its own blog. But Tails Project is a small org and over time the blog became too hard to moderate. It was discontinued when some posters tried to describe specific abuses by intelligence agencies of Western Europe and USA. (Later confirmed in all respects by the Snowden leaks.)

2. Tails Project is separate from Tor Project, although closely allied, and for security reasons it may be best not to try to have them respond to comments on their posts here, whereas for clarity it is clearly best that Tor Project people not try to respond to questions asking about Tails.

> What a shame

Yes.

But compared to USG attempts to "kill" (their word) UNCHR and ICC (and maybe also Riseup, Boum, Tails Project, Tor Project, HRW, Amnesty, RSF, CPJ, ACLU, EFF...) "by any means necessary" (thus the reliably revolting John Bolton), this is a minor issue.

Anonymous

September 05, 2018

Permalink

After applying the update to version 8, the browser will not start anymore...

I was more or less expecting this could happen (same problem with an alpha version; don't remember witch one), so I made a backup of the last version 7.
It is of course unsafe to continue using that one...

System:
Linux Mint 17.3, 64bit
16GB RAM
Kernel 4.4.0.134

I restarted when prompted, and nothing happened after that, not even an error message.

I tried with a new tarball (tor-browser-linux64-8.0_nl.tar.xz); clicked on the setup icon and that changed into an icon named "tor browser" that looked like a sheet of paper...
Clicking on that one did nothing at all.

Short answer: You need to install "libgtk3". Please ask in a Mint forum for exact package name and how to install it.

Long answer: I had the same issue on a different Linux distribution. Starting the embedded Firefox browser manually, I got this error message:

  1. <br />
  2. XPCOMGlueLoad error for file /tmp/ksocket-pepo/Browser/libmozgtk.so:<br />
  3. libgtk-3.so.0: cannot open shared object file: No such file or directory<br />
  4. Couldn't load XPCOM.<br />

After installing the package that offers the libgtk-3.so.0 file, Tor browser worked as expected.

I actually have libgtk-3-0 (3.10.8-0ubuntu1.6) installed...

Could it be that I have a wrong version of libstdc (libstdc++.so.6.0.24)?
(See my other reply, that is still awaiting moderation)

[Edit]
Opening a terminal in the "Browser" directory and give the command:
./start-tor-browser --verbose
throws this error:
./firefox.real: relocation error: ./firefox.real: symbol _ZTTNSt7__cxx1119basic_ostringstreamIcSt11char_traitsIcESaIcEEE, version GLIBCXX_3.4.21 not defined in file libstdc++.so.6 with link time reference

Worked for me in ubuntu 14.
1 open file /Browser/firefox
2 comment line 10,12( if and fi) to use custom libstdc++
#if [ $? -ne 0 ]; then
LD_LIBRARY_PATH="$LD_LIBRARY_PATH:$basedir/TorBrowser/Tor/libstdc++/"
#fi

All should work.

Yes, on Ubuntu 14.04.5 LTS same problem.

The problem is in reloc functions. To check use this:
$ ldd -r firefox.real
linux-vdso.so.1 => (0x00007ffe30ffb000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fb7454bb000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fb7452b7000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fb7450af000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007fb744d9b000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fb744a95000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fb74487e000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fb7444b4000)
/lib64/ld-linux-x86-64.so.2 (0x0000560938ac7000)
symbol _ZTTNSt7__cxx1119basic_ostringstreamIcSt11char_traitsIcESaIcEEE, version GLIBCXX_3.4.21 not defined in file libstdc++.so.6 with link time reference (./firefox.real)
symbol _ZTVNSt7__cxx1119basic_ostringstreamIcSt11char_traitsIcESaIcEEE, version GLIBCXX_3.4.21 not defined in file libstdc++.so.6 with link time reference (./firefox.real)
symbol _ZTVNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEEE, version GLIBCXX_3.4.21 not defined in file libstdc++.so.6 with link time reference (./firefox.real)
symbol _ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE9_M_createERmm, version GLIBCXX_3.4.21 not defined in file libstdc++.so.6 with link time reference (./firefox.real)
symbol _ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE9_M_assignERKS4_, version GLIBCXX_3.4.21 not defined in file libstdc++.so.6 with link time reference (./firefox.real)
symbol _ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE9_M_mutateEmmPKcm, version GLIBCXX_3.4.21 not defined in file libstdc++.so.6 with link time reference (./firefox.real)
symbol _ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE9_M_appendEPKcm, version GLIBCXX_3.4.21 not defined in file libstdc++.so.6 with link time reference (./firefox.real)
symbol _ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE9push_backEc, version GLIBCXX_3.4.21 not defined in file libstdc++.so.6 with link time reference (./firefox.real)
symbol _ZNKSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE4copyEPcmm, version GLIBCXX_3.4.21 not defined in file libstdc++.so.6 with link time reference (./firefox.real)

I presume you asked me?
The layout of this blog makes it rather difficult to see...

The output is :

  1. ~/Downloads/tor-browser_nl/Browser $ ./abicheck<br />
  2. Exception thrown<br />
  3. ~Foo() called during stack unwinding<br />
  4. Exception caught: test exception<br />
  5. ~Foo() called normally

This is the same with or without the unofficial patch of the "firefox" shell script.

  1. <br />
  2. $ ./abicheck<br />
  3. Exception thrown<br />
  4. ~Foo() called during stack unwinding<br />
  5. Exception caught: test exception<br />
  6. ~Foo() called normally</p>
  7. <p>$ ldd ./abicheck<br />
  8. linux-vdso.so.1 => (0x00007ffcf93c3000)<br />
  9. libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f42d4ed1000)<br />
  10. libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f42d4bcb000)<br />
  11. libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f42d49b4000)<br />
  12. libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f42d45ea000)<br />
  13. /lib64/ld-linux-x86-64.so.2 (0x0000563606bef000)<br />

Anonymous

September 05, 2018

Permalink

Questions:

1. NoScript on Tor Browser 7.5.6 can block javascript (and other resources) in "file:" URLs. Can NoScript in Tor Browser 8 do that as well?

2. On Firefox, NoScript 10 treats some Mozilla-owned domains as "privileged" and is unable to disable javascript (or other resources) in those URLs. Firefox ESR 52 and Tor Browser 7.5.6 do not have that problem. What's the status in Tor Browser 8? See "src/noscript/upstream/src/lib/restricted.js" in NoScript's source tree and https://bugzilla.mozilla.org/show_bug.cgi?id=1415644.

3. This is an important regression in Firefox ESR 60: https://bugzilla.mozilla.org/show_bug.cgi?id=1487856. What's the status in Tor Browser 8?

2. On Firefox, NoScript 10 treats some Mozilla-owned domains as "privileged" and is unable to disable javascript (or other resources) in those URLs. Firefox ESR 52 and Tor Browser 7.5.6 do not have that problem. What's the status in Tor Browser 8? See "src/noscript/upstream/src/lib/restricted.js" in NoScript's source tree and https://bugzilla.mozilla.org/show_bug.cgi?id=1415644.

I only went through the bug report superficially but isn't Firefox Account disabled in Tor Browser and thus this doesn't apply?

Nevertheless, I guess it should be made harder to install extension. The FAQ already states that extensions should not be installed but I doubt many read that.

3. This is an important regression in Firefox ESR 60: https://bugzilla.mozilla.org/show_bug.cgi?id=1487856. What's the status in Tor Browser 8?

Looking at the bug report, I don't understand how that's an issue for Tor Browser. Perhaps I just don't get the connection somehow. Does this introduce a privacy or security issue or something like that?

I only went through the bug report superficially but isn't Firefox Account disabled in Tor Browser and thus this doesn't apply?

You're missing the point, which was clearly stated:

...NoScript 10 treats some Mozilla-owned domains as "privileged" and is unable to disable javascript (or other resources) in those URLs.

Does this introduce a privacy or security issue or something like that?

It is an important usability issue, especially for those who disable javascript.

You're missing the point, which was clearly stated:

...NoScript 10 treats some Mozilla-owned domains as "privileged" and is unable to disable javascript (or other resources) in those URLs.

Guess I got a bit distracted by the bug report you linked. Just to clarify, you talking about an arbitrary page being able to execute any JavaScript hosted on these domains, right? I definitely see how that could be an issue.

I recommend you open a ticket on https://ticket.torproject.org (if there is none yet) to have this looked into.

Does this introduce a privacy or security issue or something like that?

It is an important usability issue, especially for those who disable javascript

I see, opening a ticket would seem the right way to go then. Perhaps you could add an example in the ticket that shows how this bug in combination with JS being disabled leads to an unusable page. In my experience bug reports that clearly show that they are a real-world issue are fixed faster.

And NoScript in TBB7.5.6 has had a ....very strange bug, can't block JSON .Bug was sold from zerodium to governments. *WTF*
It's good to have stong nerves and don't believe in conspiracy theories(-:

Anonymous

September 05, 2018

Permalink

thank for this huge update! but how can you see your entry/exit node (IP). before update it was tor button, but now...?

Anonymous

September 05, 2018

Permalink

haven't checked on a non-Linux OS, but the user agent reported by this new Tor Browser is actually Linux, and not Windows, as on previous versions. Is this intended?

So why releasing now? It's months late anyway. If security vulnerabilities were the concern it should have gone out together with ESR 60,

Have ESR 52 vulnerabilities been observed being exploited in the wild now?

Join the discussion...

This question is for testing whether or not you are a human visitor and to prevent automated spam submissions.

6 + 2 =
Solve this simple math problem and enter the result. E.g. for 1+3, enter 4.