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 06, 2018

Permalink

Hey, and when I open about:config, I can see many https: link to .mozilla.org.
Why you can't replace them to empty string?

Anonymous

September 06, 2018

Permalink

Sorry, though I see the effort you spent, I'm not happy with 8.0

Where is the am I on tor button?
Where is the change channel for this page button?
Where is it displayed which countries are used for my internet access?

My impression is that we loose control and anonymity with the latest version of tor.
I hope you will turn it back.

No. The latter two items moved into the URL bar, behind the "i" icon showing information about the currently visited URL. It feels much more natural having that information there than in a generic Torbutton menu that is for the whole browser and not just a particular tab.

The link to check.torproject.org got removed as in the past we got a bunch of false negative reports that scared users and Torbutton is automatically checking whether you are connected to Tor anyway and indicating if not. Thus, this check is redundant and error-prone.

Anonymous

September 06, 2018

Permalink

The Bing translation tool at https://www.bing.com/translator completely breaks under 8.0. I can get it working by disabling restrictions from the tab. Simply "trusting" each of the referenced domains is NOT enough to restore the function.

What are the additional permissions that disabling restrictions on the tab is enabling that trusting domains alone does not do?

Anonymous

September 06, 2018

Permalink

in older versions about:config listed 300+ configurable noscript options.
in v8.0 it does not list even one, and the options in in noscript itself have vastly been reduced.
more regression!

Anonymous

September 06, 2018

Permalink

152 bugs!
If the new Firefox looks like as stable and secure as Adobe Flash, what can we expect from Torbrowser then?
I really appreciate the hard work but will it be worth to try fix and fix over and over again this new mozilla colander style browser that is creating problems over and over again with new fashionable unnecessary functionality?
Modifying a bad product costs many ours of people working to make it work with no guarantee because of troublemaker mozilla, and that is sad, because Tordevelopers and their users deserve better.
However, given the situation, thank you for your hard work and efforts and hopefully this fashionable long term damage that mozilla is creating will not cost lives or will unnecessary fill jails with innocent people.

Anonymous

September 06, 2018

Permalink

SEVERE BUG.

about:preferences#privacy
Cookies and Site Data
Selected: "Block cookies and site data"

[ Exceptions... ] -> [https://example.com Allow for session]

But it seems Tor Browser is not eating cookies so I can't login to example.com!

HELP!

I tried to login to https://trac.torproject.org/projects/tor/newticket
with "https://trac.torproject.org Allow for session" settings, SAME RESULT.

WTF is going on!?
I had to use Firefox Extended Support Release version 60 with Tor
to login to example.com. I feel VERY insecure.

I was fine with TBB 52 era, but now this!?
Please fix TBB ASAP!

Anonymous

September 06, 2018

Permalink

It's not possible to start the navigator.
The error message is: "Tor unexpectedly exited.This might be due to a bug in Tor itself, another program on your system, or faulty hardware. Until you restart Tor, the Tor Browser will not able to reach any websites. If the problem persists, please send a copy of your Tor log to the support team"

Anonymous

September 06, 2018

Permalink

No more Vista support ????.
I do not want (or can afford) to upgrade to a more sophisticated version of Windows spyware.
Can I still use the old version of TOR ?
In my opinion you are moving backwards with TOR , too many "features"
But I must thank you whole heartedly for providing this program.

Anonymous

September 06, 2018

Permalink

Thanks for the new release. Apparently it is not compatible with the use of FireJail and Firetools for sandboxing it (always get a message: "Your tab crashed, restart...."). Too bad.

Otherwise, the experience is cool, so far.

Yes, we have https://trac.torproject.org/projects/tor/ticket/27407 for that. We actually think this is a Firefox bug as this got reproduced with a vanilla Firefox, too. Thus, we have https://bugzilla.mozilla.org/show_bug.cgi?id=1488078. They might have problems reproducing the bug. So, if you could help them with that, then that would be the first step getting it properly solved. :)

Anonymous

September 06, 2018

Permalink

Noscript does not save the whitelist settings(in `Per-site Permissions`), they only remain there for as long as the browser is running. If I restart the browser all entries I made there are gone.
Steps to reproduce:
- Download Tor Browser Bundle 8.0
- Run `./start-tor-browser.desktop` in the terminal
- Under `Per-site Permissions` in the noscript options, add any site and set it to trusted
- Close the browser
- Open it
- Go to `Per-site Permissions` in the noscript options
- The entry is not there anymore
I'm on fedora 28, 64 bit.

Anonymous

September 06, 2018

Permalink

First of all, I would encourage every one check Tor Browser "fingerprintability" before updating to 8.0 and after the update. For me, using Panopticlick, it went from non-unique (on 7.5.6) to nearly-unique (on 8.0). oO

Now, I got a couple of issues with 8.0:

  1. What happened to the canvas permissions pop-up? It seems to be gone and canvas access is allowed by default. Is there a way to get the permissions pop-up back and/or deny canvas by default?
  2. NoScript settings (including whitelisted sites) are reset after browser reload. Is it the plugin or browser issue?

Thanks for your efforts in making privacy available!
Thanks, in advance, for your answers!

First of all it's not surprising that Panopticlick is reporting that for you. I mean how many Tor Browser 8 versions does it have seen so far, compared to *all* the browser fingerprintings over the years? Right, essentially none, hence the result: Panopticlick is heavily biased and not a good test for measuring Tor Browser fingerprintability.

Regarding issue 1) canvas extraction is not allowed by default. You can test that on one of our test sites: https://people.torproject.org/~brade/tests/canvasTest.html. What we did though, is greatly reducing the "prompt-fatigue" by using a Mozilla patch https://bugzilla.mozilla.org/show_bug.cgi?id=967895 and sending white noise for all users.

Regarding issue 2) This is https://trac.torproject.org/projects/tor/ticket/27175 and we are looking into it.

Thanks for your answers, I've got a couple new questions though:

  1. How would I enable canvas extraction if it is needed by some site functionality (e.g. avatar uploading)?
  2. Which tools would you advise as a replacement of Panopticlick for measuring Tor Browser fingerprintability?

You should get a popup (see the tests I linked above) which should allow you to enable canvas.
Regarding 2) there are, alas, no good tools for that yet. We try to make our FPCentral Google Summer of Code project into such one (a beta can be found at: http://ngp5wfw5z6ms3ynx.onion/) but we did not have as much time to maintain and develop it as necessary yet. :(

— Platform macOS, Tor Browser 8.0 —
Regarding 2)...In Tor Browser 7.5.6 and earlier versions, fingerprint tests consistently revealed screen resolution '1000X1000'. FPCentral Google Summer of Code project: http://ngp5wfw5z6ms3ynx.onion/tor shows 'SCREEN RESOLUTION 1000X998. Your Tor browser is not at the recommended size. It should be either at 1000x1000 or at a multiple of 200x100.' With Tor Browser 8.0, this issue, '1000X998', or '1000x998x24' persists in all other fingerprint test results, including Panopticlick, whoer.net, amiunique.org, more... Please fix this issue so that when Tor Browser opens, the screen resolution is 1000x1000, and not 1000X998. Thanks

Anonymous

September 06, 2018

Permalink

1) Can you please add an extension to the Tor browser that has the same features as Self-Destructing Cookies with it enabled by default on all sites. This would go a long way to prevent unintentional tracking along with it being officially added to the browser we don't have to worry about the extension suddenly becoming malicious, harvesting user data or making people less anonymous by having to install it themselves.

2) Please put a priority on fixing User Agent issue this can have detrimental consequences for people who need it.

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.

Anonymous

September 06, 2018

Permalink

On Linux, the "see my path" button in the new onboarding wizard opens a new tab with the ddg onion, and then opens the box that normally opens when the site name is clicked on (the box that says "secure connection" and "permissions" etc). I assume it is trying to open the Tor Button circuit display but finding the wrong ui element? I thought it was because i'd reordered my toolbar, but changing the order of the widgets doesn't seem to change the behavior: i always get to the site info box from the wizard's "see my path" button.

Anonymous

September 06, 2018

Permalink

Bedroom Chinese users, built-in meek-azure has been blocked by China, the next is the log

9/6/18, 14:51:02.531 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
9/6/18, 14:51:02.531 [NOTICE] Opening Socks listener on 127.0.0.1:9150
9/6/18, 14:51:04.743 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150
9/6/18, 14:51:04.743 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
9/6/18, 14:51:04.743 [NOTICE] Closing old Socks listener on 127.0.0.1:9150
9/6/18, 14:51:22.314 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
9/6/18, 14:51:22.315 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
9/6/18, 14:51:22.315 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
9/6/18, 14:51:22.315 [NOTICE] Opening Socks listener on 127.0.0.1:9150
9/6/18, 14:51:26.127 [NOTICE] Bootstrapped 5%: Connecting to directory server
9/6/18, 14:51:26.129 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server
9/6/18, 14:52:26.148 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 1; recommendation warn; host 97700DFE9F483596DDA6264C4D7DF7641E1E39CE at 0.0.2.0:2)
9/6/18, 14:52:26.149 [WARN] 1 connections have failed:
9/6/18, 14:52:26.151 [WARN] 1 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE
9/6/18, 14:52:26.191 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150
9/6/18, 14:52:26.191 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
9/6/18, 14:52:26.191 [NOTICE] Closing old Socks listener on 127.0.0.1:9150
9/6/18, 14:52:27.111 [NOTICE] Delaying directory fetches: DisableNetwork is set.

Anonymous

September 06, 2018

Permalink

Hello, i have a question regarding the renaming of the Tor Browser folder.

I like to have older TBB versions and i rename the folders with an added version number. Before this new version 8.0, i was able to rename the folders after each update (for example from "Tor Browser 7.2" to "Tor Browser 7.3" and then after starting the shortcut "Start Tor Browser", it still worked.

Now after i updated to 8.0 and then changing my folder name from "Tor Browser 7.5" to "Tor Browser 8.0" it doesn't work anymore. After clicking the shortcut "Start Tor Browser", it opens the firefox.exe, but Tor itself is not loaded before that and also the onion symbol in the toolbar is not there. Also no site seems to work. Renaming it back to "Tor Browser 7.5" is making it work again.

Is there a workaround to rename the folder while functionality is still given? Thanks in advance.

Anonymous

September 06, 2018

Permalink

Hi,

is it only me or is NoScript no longer saving any changed presets? I normally start with "Default - everything off (nothing is allowed)". But the changes made in the add-on setting page is gone after every start of the browser.

Anonymous

September 06, 2018

Permalink

With the release of 8.0 i have issues with HTML5 video playback. To reproduce the issue and rule out an error in the settings, i used a fresh install, with default settings.

Videos are no longer click-to-play. With Security Level on Standard videos automatically start to play. With Security Levels on Safer and Safest videos don't play at all. To play videos with the higher Security Levels the site needs to be trusted in NoScript. Trusted sites however play videos automatically.

This should not happen, especially since Safer and Safest clearly say "Audio and video (HTML5 media) are click-to-play."

Anonymous

September 06, 2018

Permalink

In 8.0 new version..
Where is java button enable/disable?? diaspear?? It was very useful.

Why there is no ne Tor for Windows Xp and vista..still many using!!
also 32 bit version is necessery too.

Anonymous

September 06, 2018

Permalink

HOW CAN I DOWNGRADE TO 7 PLEASE ?
THE 8 DESTROYED MY CLASSIC DISPLAY, MY FLASH, MY DOWNLOADS FROM YOUTUBE, EVERYTHING

I HATE THIS INTERMINABLE COURSE TO FALSE IMPROVING'S, AGAINST FALSE ENEMY'S, ETC.,
AFTER SO MANY YEARS WHEN WILL YOU UNDERSTAND THAT YOUR EXTRAORDINARY WORK, UNFORTUNATELY REMAINS A TOOL FOR US HELPING FOR SOME OTHER ACTIVITY
ITS A TOOL FOR US, NOT A MUST BE "IN", A LETS CHANGE THE TOOLBAR IN AN INAPPROPRIATE PLACE :

EXAMPLE OF STUPIDITY :
1)
THE NAVIGATION BAR IS STATIC, DOES NOT CONTAIN THE INFORMATION WE USE TOR FOR. WE DON'T EAT ADRESSES, BUT CONTENTS.
2)
THE BOOKMARKS EITHER. THOSE ARE STATIC THINGS WE DO NOT USE TOT TO READ BOOKMARKS BUT CONTENTS
3)
THE ONLY THING IN TOUCH WITH THE CONTENTS IS THE TAB CONTAINING THE NECESSARY, THE GOAL OF TOR, THE CONTENT.

OR, SOME IDIOT HAS SEPARATE THE TAB FROM THE CONTENT. INCREDIBLE. STUPID.
ITS COMPLETELY CRAZY

THE REALTIME WORK

Anonymous

September 06, 2018

Permalink

I stopped using Firefox because the new version had a lot of addons-related efficiency problems. Now I see this Tor is the same but I can't stop it from updating, I try to install the older version without any success.
I wish you could let the user decide which version they want to use at their own risk. For some of us, this update means we have to stop using Tor altogether.

Join the discussion...

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

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