Tor Browser 8.0a4 is released

Tor Browser 8.0a4 is now available from the Tor Browser Project page and also from our distribution directory.

This release features important security updates to Firefox.

The full changelog since Tor Browser 8.0a3 is:

  • All platforms
    • Update Firefox to 52.7.2esr

Why does TOR get stuck on U.S.A. based relays? Every time TOR uses a U.S.A. based relay, the webpage I am using stops working. The NSA slows all U.S. traffic and ruins TOR. Tonight I can't get TOR to switch away from U.S. relay. PLEASE STOP USING ANY U.S. BASED RELAYS!!!!

When I set Torrc for Exit {us} it only chose 1-2 of the same exits even though the database shows many many more Exit relays for the US. Did not matter how many times I changed identity, and or session changes over days/weeks. I only used if for about 2-3 week period. Also very slow............Bridges or not bridges has no apparent difference. If China can block bridges USA obviously can as China learns most of their tricks from USA about popularized Totatlitarianisms.

John

March 19, 2018

Permalink

two days ago I posted here:
----------- start
itsme (not verified) said:

March 17, 2018
Permalink

thanks for your great work!! :))

any one who recognized the "new" behaviour of TB too?
starting with version 8.0a2 the "hops" through tor network looking very often like this:

entry node: country A
middle node: B
exit node: B (same country different node of course)

And very often I get something like this: A A A

In earlier versions of TB I experienced something like A B C - it was normal to hop through different countries.

Why is TB focus on just one country ( A-A-A) as of version 8.0a2 ?
---------------- end

This behaviour remains the same in Version 8.0a4 !
And even worse, TB very often choses an exit node in my country (say its E) so the chain looks like this:

A - B - E
A - E -E

connection to a website TB says "transfering data from...." - and one can watch TB to establish the new connection like this: A - B - F .... A - D - C .... A - F - G and in the end I get A - C - E for the website
Seems TB loves my country !!! :-(

John

March 20, 2018

Permalink

Hello guys the work you are doing is fantastic
since a couple of alphas can't customize the UI because

If you click the customize button and then the interface shifts to the customizable one but it automatically reverts to the normal interface (so can't customize like you normally would, you need to move object quickly before the customizable UI reverts to the normal UI)

The point is to have quick access to the preferences button (and other buttons sometimes) so cookies can be enabled/disabled easily (also save page, print, history, bookmarks, downloads, developer, etc)

Of course one can just click the three bar button and a very convenient menu will appear which is perfect and has all the options. Maybe this is not in the bug category but the will to contribute anything was behind this. Thank you and know that we will always support you!

John

March 20, 2018

Permalink

Why is it ok for Tor to create circuits with all relays in the same country? I get that Tor doesn't protect against global adversaries, but no protection against local adversaries?

John

March 21, 2018

Permalink

03/21/2018 09:58:47.900 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
03/21/2018 09:58:47.900 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
03/21/2018 09:58:47.900 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
03/21/2018 09:58:47.900 [NOTICE] Opening Socks listener on 127.0.0.1:9150
03/21/2018 09:58:47.900 [NOTICE] Renaming old configuration file to "/home/user/Downloads/tor-browser_en-US/Browser/TorBrowser/Data/Tor/torrc.orig.1"
03/21/2018 09:58:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server
03/21/2018 09:58:48.100 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server
03/21/2018 09:58:48.400 [NOTICE] Bootstrapped 15%: Establishing an encrypted directory connection
03/21/2018 09:58:48.600 [NOTICE] Bootstrapped 20%: Asking for networkstatus consensus
03/21/2018 09:58:48.700 [NOTICE] Bootstrapped 25%: Loading networkstatus consensus
03/21/2018 09:58:49.800 [NOTICE] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
03/21/2018 09:58:49.900 [NOTICE] Bootstrapped 40%: Loading authority key certs
03/21/2018 09:58:50.700 [WARN] Our clock is 9 hours, 1 minutes behind the time published in the consensus network status document (2018-03-21 19:00:00 UTC). Tor needs an accurate clock to work correctly. Please check your time and date settings!
03/21/2018 09:58:50.700 [WARN] Received microdesc flavor consensus with skewed time (CONSENSUS): It seems that our clock is behind by 9 hours, 1 minutes, or that theirs is ahead. Tor requires an accurate clock to work: please check your time, timezone, and date settings.
03/21/2018 09:58:50.700 [WARN] Problem bootstrapping. Stuck at 40%: Loading authority key certs. (Clock skew -32470 in microdesc flavor consensus from CONSENSUS; CLOCK_SKEW; count 1; recommendation warn; host ? at ?)
03/21/2018 09:58:50.700 [NOTICE] I learned some more directory information, but not enough to build a circuit: We have no recent usable consensus.
03/21/2018 09:58:50.700 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150
03/21/2018 09:58:50.700 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
03/21/2018 09:58:50.700 [NOTICE] Closing old Socks listener on 127.0.0.1:9150
03/21/2018 09:58:50.900 [NOTICE] Delaying directory fetches: DisableNetwork is set.

You should check your local time settings and fix them:

03/21/2018 09:58:50.700 [WARN] Our clock is 9 hours, 1 minutes behind the time published in the consensus network status document (2018-03-21 19:00:00 UTC). Tor needs an accurate clock to work correctly. Please check your time and date settings!

John

March 21, 2018

Permalink

I keep getting "This IP has been automatically blocked." for sites I have visited often. I used to just click on "New Tor Circuit for this Site", and, after a couple of times, I would get a set of relays that did not automatically block. Now, since the beginning relay is remaining the same, for, is it three months, I am blocked without recourse. Am I supposed to wait three months, or however long, until my beginning relay changes. Please tell me there is a simple answer, that Tor has not just stopped working for many common uses.

John

March 21, 2018

Permalink

Tor network keeps crashing and what's up with duckduckgo it no longer allows multiple tabs? I am looking for a new dns that will work with Tor I don't trust Google or Yahoo and getting doubtful about duckduckgo what would you suggest

John

March 22, 2018

Permalink

New and would like to know more about tor and just really get into coding and programming yo better understand and use this the way the experts do.

John

March 23, 2018

Permalink

Unfortunately, Tor Browser overloads 2-core Windows 7 notebook when playing SD video. It's madness, but, maybe, that's the price for security. Nevertheless, it seems too big price for it.

John

March 23, 2018

Permalink

General question regarding software distributed at torproject

Error checking sig of downloaded software from archive.torproject.org

Output sig check:
gpg: using ? key '..numbersandletters..'
gpg: Can't check signature: Invalid public key algorithm

Does anybody know what an 'Invalid public key algorithm' means and how to solve it?
It was not a problem 2 weeks ago and software downloaded 2 weeks ago does not give these new errors. New downloads via other cricuits don't solve the error-problem.

John

March 23, 2018

Permalink

Where do I sign up TOR Bugs or feature changes.

For instance, I wish to make TOR apply it's new crypto to new circuits whenever available and avoid old Tor Circuits that won't build using the new crypto. I notice even when I set for instance in TORRC to Exit {ch} (switzerland) which has only New Tor crypto Exit relays a lot of the time still builds circuits using older crypto Tor nodes as entry or middle relays. It seems like a design flaw.

It would make sense that Tor does not even use the new crypto if it is transporting or making circuits over old Tor relays that don't even support it. I guess we would not want to make things to difficult for the Virtual Gulag Overseers in controlling the new money creation.

John

March 25, 2018

Permalink

Tor is either being censored in New Zealand or deliberately slowed down - or completely stopping searches. Could someone please direct me to how to overcome this issue. I am not using the bridge thing - not sure how to.

I'm a grandmother endeavouring to stay above the lack of ethics that pervade our lives - yet I am determined to rise above - We are as free as we choose to be.

Join the discussion...

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

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