New Release: Tor Browser 8.5a1

Tor Browser 8.5a1 is now available from the Tor Browser Project page and also from our distribution directory.

This release features important security updates to Firefox.

Tor Browser 8.5a1 is the first alpha release in the 8.5 series. It contains all the improvements from the new 8.0 release. In addition, we updated Tor to 0.3.4.7-rc and fixed an issue with Moat when a meek bridge has been configured.

The full changelog since Tor Browser 8.0a10 is:

  • All platforms
    • Update Firefox to 60.2.0esr
    • Update Tor to 0.3.4.7-rc
    • Update OpenSSL to 1.0.2p
    • Update Torbutton to 2.0.6
      • Bug 27401: Start listening for NoScript before it loads
      • Bug 27276: Adapt to new NoScript messaging protocol
      • Bug 26884: Use Torbutton to provide security slider on mobile
      • Bug 26962: Circuit display onboarding
      • Bug 26520: Fix sec slider/NoScript for TOR_SKIP_LAUNCH=1
      • Bug 26490: Remove the security slider notification
      • Bug 27301: Improve about:tor behavior and appearance
      • Bug 27097: Add text for Tor News signup widget
      • Bug 27214: Improve the onboarding text
      • Translations update
    • Update Tor Launcher to 0.2.16.4
      • Bug 25405: Cannot use Moat if a meek bridge is configured
      • Bug 27392: Update Moat URLs
      • Translations update
    • Update HTTPS Everywhere to 2018.8.22
    • Update NoScript to 10.1.9.1
    • 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 26670: Make canvas permission prompt respect first-party isolation
    • Bug 26561: .onion images are not displayed
    • 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 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 25405: Cannot use Moat if a meek bridge is configured
    • Bug 27268+27257+27262+26603 : Preferences clean-up
  • Windows
    • 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
  • Build System
    • All Platforms
      • Bug 27061: Enable verification of langpacks checksums
      • Bug 27178+27179: Add support for xz compression in mar files
Seth Schoen

September 06, 2018

Permalink

TOR does not load. I can however get the following report.

[NOTICE] Bootstrapped 85%: Finishing handshake with first hop
9/7/18, 05:12:27.570 [NOTICE] Bootstrapped 90%: Establishing a Tor circuit
9/7/18, 05:12:27.676 [WARN] Rejecting SOCKS request for anonymous connection to private address [scrubbed].
9/7/18, 05:12:28.704 [NOTICE] Tor has successfully opened a circuit. Looks like client functionality is working.
9/7/18, 05:12:28.704 [NOTICE] Bootstrapped 100%: Done

Seth Schoen

September 07, 2018

Permalink

just updated to version 8, now browser won't work. message window opens saying: tor unexpectedly exited… pressing button: [Restart Tor] doesn't restart or open Tor. am running on Mac OS 10.9.5. help would be really nice.

Yes, that's an unfortunate bug as the current stable Tor version we ship is missing a patch to make it compatible with macOS 10.9 (which, by the way, does not get security updates anymore for two years). This will be fixed in Tor Browser 8.0.1, though. Meanwhile you can use Tor Browser 8.5a1 (https://www.torproject.org/projects/torbrowser.html.en#downloads-alpha), the alpha version which is almost the same as Tor Browser 8.0 but with a newer Tor version which contains the fix. Sorry for the inconvenience.

Disabled 3rd party cookies? Great, but what about all other elements from 3rd party sites? Loading any element from them leaves some fingerprint.
Another Firefox add-on, uMatrix, when installed together with NoScript, reveals a lot more linked sites that NoScript doesn't (try and compare at various sites). What's more, you can block those additional 3rd party elements from uMatrix (proof: the page often looks different after reloading), while NoScript seems to quietly allow them all.

I have the same problem. I save a website "Save Page As..." and it does not download the website. The pictures are missing and the layout is totally messed up. This error can be reproduced on most websites. Additionally, there is no need to download the website a second time. Just save it from the browsers cache.

Seth Schoen

September 07, 2018

Permalink

le navigateur Tor déjà installé ne veut plus s'ouvrir après la dernière mise à jour. Je suis sur Mac os 10.9.5 .

Seth Schoen

September 07, 2018

Permalink

always the useragent not possible change, WTF ? all work fine with the old version, now the useragent is the real !!!!

Seth Schoen

September 07, 2018

Permalink

Исправьте пожалуйста fix, после нового обновление на ubuntu, пропал значёк картинки тора зелёного , и стоит вопросительный знак серого цвета+ тор плохо очень грузит

Seth Schoen

September 07, 2018

Permalink

When i try to verify the signature of the package i get a error message:

Verify signatures failed: error while opening file. I use Ubuntu 16.04

Thanks

Seth Schoen

September 07, 2018

Permalink

I just recently updated to the latest TB & heres my problem

1. Useragent cannot be spoofed manually
2. Sandbox mode keep TB tabs crashing, running to the latest firejail

The UI doesn't interest me, Pls. fix this on your next update, I hope

Seth Schoen

September 07, 2018

Permalink

We've got a bigger problem now...ever since I updated to the new Tor, my PC has slowed down and started "crashing" / "freezing" every few minutes !

What operating system are you running? Windows I guess? You could try a clean 64bit Tor Browser bundle for Windows as it is said that Firefox is running much more stable with the 64bit than the 32bit version. That said another issue could be that your Antivirus/Firewall software is causing this. If you have any installed, please test after removing it temporarily (disabling is often not enough).

Seth Schoen

September 07, 2018

Permalink

I'm fully aware of this being a Alpha release but why so slow?

1. I miss the Onion, I hope you guys are not removing that! I know about the Update arrow next to the URL lock but that's not the same thing. I wont remove the active website and restart in a new clean window. Also you can't see the countries.

2. I don't know if it's just because it's a alpha but I don't like the look of the new window tabs. They just look so, 1980 look a like. I prefer then being round in the corners with a more modern and a dark layout.

Keep up the good work with giving people privacy and freedom!

Criminals who do stupid shit can go to hell. But for normal people who just want some privacy we really do appreciate all the hard work you guys are doing!

If you agree with me about the last part, scroll up in top of this thread and hit the Donate button!
$1 is enough if everyone does it! Not much to ask for comparing for what you get in return for FREE!

Seth Schoen

September 07, 2018

Permalink

The Javascript error message is backwards. It says it's enabled when it's not and then it says it's not enabled when it is. It's programmed backwards with the new update. You should do a reverse update and bring back the old Tor.

This is the error. It's backwards:
You have JavaScript enabled, you are putting yourself at risk! Please disable it immediately!"

Where can I see this error message?

EDIT: Oh, I see. That's nothing we did but the website owner. If you don't like JavaScript disabled there is the security slider (see the onboarding in the upper left on the about:tor page) to change that.

Seth Schoen

September 07, 2018

Permalink

I have problems everywhere with this new update, you are sure this isn't the beta tor browser released as stable ?

You just posted this comment in the alpha release blog post but I guess you are using Tor Browser 8.0? A good first start would be giving us some hints about your problems and your operating system you are using. Without that it's hard to explain things or help you.

Seth Schoen

September 08, 2018

Permalink

right click dont work on some sites = cant use wiew img or open in new tab so on .... left click = open several new windows in backgrond pop ups ... and need confirm every closing of window ... cant use this ver. like a virus .. what to do ?

Seth Schoen

September 08, 2018

Permalink

no script is not keeping changes in its options, after restarting tor browser settings return to default.

Seth Schoen

September 08, 2018

Permalink

In the old tor i could see and chose witch circuit i want to use. Speed and so on.
Not its gone?
and i get the same circuit all the time and it also stands
"your guard node may not change" what and how to i change or chose another one

Seth Schoen

September 08, 2018

Permalink

I wouldn't be suprised if this release is full of exploit, the new Tor Browser is shit made by idiots or feds

Noscript work 50% of the time, tracker protection and DNT are not by default, duckduckgo as search engine (us based) etc
EDIT : IT ALSO LEAK YOUR NUMBERS OF CPU CORES AND OS, DON'T USE THE UPDATE

I feel its anonymity aspect has been compromised. This update is sloppy as a mother fucker
compromised by insiders

Yes, this new update is very buggy. It's not a good update at all. The Javascript error message is backwards. I really think this update was programmed by a bunch of elementary school students as a school project to teach them to program. It's really bad. Tor really should do a reverse update. Lol. It's bad.

Seth Schoen

September 08, 2018

Permalink

NoScript auto-updated today (Sep. 8, 2018), and changed the General "Presets customization" checkboxes for Default and Untrusted. This is bad.

Default preset is now: Frame, Other
Trusted preset is now: Script, Media, Frame, Font, WebGL, Fetch, Other
Untrusted preset is now: Frame

Many sites don't load anymore after NoScript auto-updated unless I manually change the settings back.

Seth Schoen

September 09, 2018

Permalink

The first node which is linked to my browser is always the same. Why is this node not allowed to change? Thank you! :)

Seth Schoen

September 09, 2018

Permalink

I really DO NOT like the new "New identity" and "New circuit for this site" solution! So I will return to the last version before 8! Please change this back to the user friendly button! Thanks

Seth Schoen

September 09, 2018

Permalink

New Identity:
[09-09 16:41:50] Torbutton NOTE: Exception on control port [Exception... "Component returned failure code: 0x804b000e (NS_ERROR_NET_TIMEOUT) [nsIBinaryInputStream.readBytes]" nsresult: "0x804b000e (NS_ERROR_NET_TIMEOUT)" location: "JS frame :: chrome://torbutton/content/torbutton.js :: torbutton_socket_readline :: line 707" data: no]

Seth Schoen

September 10, 2018

Permalink

getting message saying "Tor unexpectedly quit. This might be due to a bug..."
There no error log though?
Any idea on a fix?

Join the discussion...

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

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