New Release: Tor Browser 8.0.9

Tor Browser 8.0.9 is now available from the Tor Browser Download page and also from our distribution directory.

This release fixes the issue which caused NoScript and all other Firefox extensions signed by Mozilla to be disabled.

If you used the workaround mentioned in our previous blog post, don't forget to set the xpinstall.signatures.required entry in about:config back to true after installing this update.

Note: We did not bump the Firefox version number to be able to build faster, thus it will still show 60.6.1esr as the Firefox version.

The full changelog since Tor Browser 8.0.8 is:

  • All platforms
    • Update Torbutton to 2.0.13
      • Bug 30388: Make sure the updated intermediate certificate keeps working
    • Backport fixes for bug 1549010 and bug 1549061
      • Bug 30388: Make sure the updated intermediate certificate keeps working
    • Update NoScript to 10.6.1
      • Bug 29872: XSS popup with DuckDuckGo search on about:tor
Anonymous

May 21, 2019

Permalink

First seen new behaviour. Every new tab looks like to be send to 31.31.78.49 by Tor, b u t the Guard is another IP and I've never seen always another IP than the Guard, or sometimes another IP for a second Guard, but now, this second IP is always there, new tab and appears, CR and appears, than traffic only through the Guard, next click, 31.31.78.49 appears but traffic through the Guard as usual. What' going on, is the ok?

Some more details. After start, there are some connections done by TOR. Later on, may 2 or 3 staying alive, the others are closed. As usual, there is the Guard, and is some kind of fixed. So the traffic runs through the Guard and sometimes are keep alive from the 2 or 3 other connection made by TOR. That was always the case, the traffic is between the LAN IP and the Guard, and sometimes one keep alive from the others, but only sometimes. Now there was this second IP. It was easy to see, that all traffic runs through the Guard shown under (i) site information, but always after CR, there was this second IP once, one data packet, after every click, but what was the data and where did they go. This one data packet send to the second IP must be for reason, but who is the recipient? It is impossible to see, where this second connection ends. You said, this IP belongs to a Guard relay, but why is TOR doing this second line, never seen before, is some kind of weird. Looks like as if it sends my visited web pages somewhere.

Anonymous

May 22, 2019

Permalink

Further infos. As I've written, it happens for the first time, that there was a second Guard relay active and after every CR or every click it appeard with one data packet, one packet was send from TOR somewhere through the second Guard and it disappeard after that, but all alive connections made by TOR. It was easy to see, all traffic runs through the Guard as shown under (i) site information as it should be. Also to see, other alive connections are there and made by TOR, but never seen before, such second 'Guard' and TOR sending datas once after any click. Captured traffic is from inside the windows system an from outside out of the 'wire', out of the switch, to check, if there are some differences. TOR is always downloaded for every session. The system is all new for every session, no traces of previous sessions, no trojans, automated system, fast setup. Next try yesterday with version 8.0.9 behaviour as usual, one Guard active, all traffic between LAN IP and active Guard, no second IP, only keep alive rarely from other hold connections. What was going on? Why there was this second parallel route/connection and it was impossible to see, what was the destination, no infos about the parallel line. Looked weird.

Anonymous

May 23, 2019

Permalink

hi
can you please make sure the adverts content doesnt cover the browser content? my iphone tor browser has ads cover the bottom of the screen so i cant use any navigation, rendering the app useless!
thanks