Tor Browser 7.0.10 is released

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

This release features important security updates to Firefox.

This release updates Firefox to version 52.5.0esr and Tor to version version 0.3.1.8, the second stable release in the 0.3.1 series. In addition to that we updated the HTTPS Everywhere and NoScript extensions we ship. For Windows users we backported patches from the alpha series that update the msvcr100.dll runtime library we include and which should make Tor Browser more robust against crashes due to misbehvaing third party software.

The full changelog since Tor Browser 7.0.9 (7.0.8 for Windows) is:

  • All Platforms
    • Update Firefox to 52.5.0esr
    • Update Tor to 0.3.1.8
    • Update Torbutton to 1.9.7.10
      • Bug 23997: Add link to Tor Browser manual for de, nl, tr, vi
      • Translations update
    • Update HTTPS-Everywhere to 2017.10.30
      • Bug 24178: Use make.sh for building HTTPS-Everywhere
    • Update NoScript to 5.1.5
      • Bug 23968: NoScript icon jumps to the right after update
  • Windows
    • Bug 23582: Enable the Windows DLL blocklist for mingw-w64 builds
    • Bug 23396: Update the msvcr100.dll we ship
    • Bug 24052: Block file:// redirects early

There are no advisories for 57.0.1 because 52.5.1esr never made it to the release channel. There will be a 57.0.2 and a 52.5.2esr out there shortly with the usual advisories detailing more than just "Various security fixes".

Anonymous

December 01, 2017

Permalink

Hmmmmm

Anonymous

December 01, 2017

Permalink

Canada's Brampton wireless is blocking Tor while I was using public IP 192.82.150.249 on a Mac. I have it set to use ports 80 and 443 and I tried All transport types, OBFS4 ,OBF3,meek-azure and meek-amazon. And I still can not connect. Below is the log showing connection problem.

30-11-2017, 19:01:07.100 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
30-11-2017, 19:01:07.100 [NOTICE] Opening Socks listener on 127.0.0.1:9150
30-11-2017, 19:01:07.100 [NOTICE] Bootstrapped 80%: Connecting to the Tor network
30-11-2017, 19:01:07.100 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop
30-11-2017, 19:01:07.100 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:01:08.300 [NOTICE] Bridge at '154.35.22.9:12166' isn't reachable by our firewall policy. Asking bridge authority instead.
30-11-2017, 19:01:08.300 [NOTICE] Bridge at '154.35.22.12:4304' isn't reachable by our firewall policy. Asking bridge authority instead.
30-11-2017, 19:01:08.300 [NOTICE] Bridge at '37.218.245.14:38224' isn't reachable by our firewall policy. Asking bridge authority instead.
30-11-2017, 19:01:08.300 [NOTICE] Bridge at '37.218.240.34:40035' isn't reachable by our firewall policy. Asking bridge authority instead.
30-11-2017, 19:01:08.300 [NOTICE] Bridge at '109.105.109.165:10527' isn't reachable by our firewall policy. Asking bridge authority instead.
30-11-2017, 19:01:08.300 [NOTICE] Bridge at '154.35.22.13:16815' isn't reachable by our firewall policy. Asking bridge authority instead.
30-11-2017, 19:01:08.300 [NOTICE] Bridge at '154.35.22.11:16488' isn't reachable by our firewall policy. Asking bridge authority instead.
30-11-2017, 19:01:08.300 [NOTICE] Bridge at '109.105.109.147:13764' isn't reachable by our firewall policy. Asking bridge authority instead.
30-11-2017, 19:01:08.300 [NOTICE] Bridge at '154.35.22.10:15937' isn't reachable by our firewall policy. Asking bridge authority instead.
30-11-2017, 19:01:08.300 [NOTICE] Bridge at '83.212.101.3:50002' isn't reachable by our firewall policy. Asking bridge authority instead.
30-11-2017, 19:01:08.300 [WARN] Could not choose valid address for JonbesheSabz
30-11-2017, 19:01:08.300 [WARN] Could not make a one-hop connection to $00DC6C4FA49A65BD1472993CF6730D54F11E0DBB. Discarding this circuit.
30-11-2017, 19:01:08.300 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:01:08.300 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:01:08.300 [WARN] Proxy Client: unable to connect to 154.35.22.11:80 ("general SOCKS server failure")
30-11-2017, 19:01:08.300 [WARN] Proxy Client: unable to connect to 154.35.22.10:80 ("general SOCKS server failure")
30-11-2017, 19:01:08.300 [WARN] Proxy Client: unable to connect to 38.229.33.83:80 ("general SOCKS server failure")
30-11-2017, 19:01:08.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:01:09.000 [WARN] Proxy Client: unable to connect to 154.35.22.11:80 ("general SOCKS server failure")
30-11-2017, 19:01:09.000 [WARN] Proxy Client: unable to connect to 154.35.22.10:80 ("general SOCKS server failure")
30-11-2017, 19:01:09.100 [WARN] Proxy Client: unable to connect to 38.229.33.83:80 ("general SOCKS server failure")
30-11-2017, 19:01:45.500 [WARN] Proxy Client: unable to connect to 85.17.30.79:443 ("general SOCKS server failure")
30-11-2017, 19:02:06.600 [WARN] Proxy Client: unable to connect to 154.35.22.13:443 ("general SOCKS server failure")
30-11-2017, 19:02:06.900 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:02:08.200 [WARN] Proxy Client: unable to connect to 154.35.22.9:443 ("general SOCKS server failure")
30-11-2017, 19:02:08.200 [WARN] Proxy Client: unable to connect to 85.31.186.26:443 ("general SOCKS server failure")
30-11-2017, 19:02:08.200 [WARN] Proxy Client: unable to connect to 192.99.11.54:443 ("general SOCKS server failure")
30-11-2017, 19:02:09.900 [WARN] Could not choose valid address for JonbesheSabz
30-11-2017, 19:02:09.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:02:10.900 [WARN] Could not choose valid address for JonbesheSabz
30-11-2017, 19:02:10.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:02:11.900 [WARN] Could not choose valid address for JonbesheSabz
30-11-2017, 19:02:11.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:02:23.300 [WARN] Proxy Client: unable to connect to 85.17.30.79:443 ("general SOCKS server failure")
30-11-2017, 19:02:39.900 [WARN] Could not choose valid address for JonbesheSabz
30-11-2017, 19:02:39.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:02:40.900 [WARN] Could not choose valid address for JonbesheSabz
30-11-2017, 19:02:40.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:02:41.900 [WARN] Could not choose valid address for JonbesheSabz
30-11-2017, 19:02:41.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:02:42.900 [WARN] Could not choose valid address for JonbesheSabz
30-11-2017, 19:02:42.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:02:43.900 [WARN] Could not choose valid address for JonbesheSabz
30-11-2017, 19:02:43.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:02:44.900 [WARN] Could not choose valid address for JonbesheSabz
30-11-2017, 19:02:44.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:03:05.300 [WARN] Proxy Client: unable to connect to 154.35.22.13:443 ("general SOCKS server failure")
30-11-2017, 19:03:06.900 [NOTICE] Ignoring directory request, since no bridge nodes are available yet.
30-11-2017, 19:03:07.900 [NOTICE] Tried to fetch a descriptor directly from a bridge, but that bridge is not reachable through our firewall.
30-11-2017, 19:03:07.900 [NOTICE] Tried to fetch a descriptor directly from a bridge, but that bridge is not reachable through our firewall.
30-11-2017, 19:03:07.900 [NOTICE] Tried to fetch a descriptor directly from a bridge, but that bridge is not reachable through our firewall.
30-11-2017, 19:03:07.900 [NOTICE] Tried to fetch a descriptor directly from a bridge, but that bridge is not reachable through our firewall.
30-11-2017, 19:03:07.900 [NOTICE] Tried to fetch a descriptor directly from a bridge, but that bridge is not reachable through our firewall.
30-11-2017, 19:03:07.900 [NOTICE] Tried to fetch a descriptor directly from a bridge, but that bridge is not reachable through our firewall.
30-11-2017, 19:03:08.000 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:03:08.900 [WARN] Proxy Client: unable to connect to 85.31.186.26:443 ("general SOCKS server failure")
30-11-2017, 19:03:10.900 [WARN] Could not choose valid address for JonbesheSabz
30-11-2017, 19:03:10.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:03:11.900 [WARN] Could not choose valid address for JonbesheSabz
30-11-2017, 19:03:11.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:03:11.900 [WARN] Proxy Client: unable to connect to 154.35.22.10:80 ("general SOCKS server failure")
30-11-2017, 19:03:11.900 [WARN] Proxy Client: unable to connect to 154.35.22.11:80 ("general SOCKS server failure")
30-11-2017, 19:03:12.900 [WARN] Could not choose valid address for JonbesheSabz
30-11-2017, 19:03:12.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:03:12.900 [WARN] Proxy Client: unable to connect to 154.35.22.11:80 ("general SOCKS server failure")
30-11-2017, 19:03:12.900 [WARN] Proxy Client: unable to connect to 154.35.22.10:80 ("general SOCKS server failure")
30-11-2017, 19:03:13.900 [WARN] Could not choose valid address for JonbesheSabz
30-11-2017, 19:03:13.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:03:41.900 [WARN] Could not choose valid address for JonbesheSabz
30-11-2017, 19:03:41.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:03:42.900 [WARN] Could not choose valid address for JonbesheSabz
30-11-2017, 19:03:42.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:03:43.900 [WARN] Could not choose valid address for JonbesheSabz
30-11-2017, 19:03:43.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:03:44.900 [WARN] Could not choose valid address for JonbesheSabz
30-11-2017, 19:03:44.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:03:45.900 [WARN] Could not choose valid address for JonbesheSabz
30-11-2017, 19:03:45.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:03:46.900 [WARN] Could not choose valid address for JonbesheSabz
30-11-2017, 19:03:46.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:04:06.900 [WARN] Cannot make an outgoing begindir connection without a remote ORPort.
30-11-2017, 19:04:10.100 [WARN] Proxy Client: unable to connect to 154.35.22.13:443 ("general SOCKS server failure")
30-11-2017, 19:04:11.900 [WARN] Proxy Client: unable to connect to 154.35.22.9:443 ("general SOCKS server failure")
30-11-2017, 19:04:12.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:04:13.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:05:14.900 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:06:06.900 [WARN] Proxy Client: unable to connect to 85.31.186.26:443 ("general SOCKS server failure")
30-11-2017, 19:06:16.900 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:06:17.000 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:06:17.900 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:06:20.700 [WARN] Proxy Client: unable to connect to 38.229.33.83:80 ("general SOCKS server failure")
30-11-2017, 19:06:20.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:06:22.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:06:59.400 [WARN] Proxy Client: unable to connect to 85.17.30.79:443 ("general SOCKS server failure")
30-11-2017, 19:07:08.600 [WARN] Proxy Client: unable to connect to 85.31.186.26:443 ("general SOCKS server failure")
30-11-2017, 19:07:18.800 [WARN] Proxy Client: unable to connect to 154.35.22.13:443 ("general SOCKS server failure")
30-11-2017, 19:07:47.900 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:07:49.900 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:07:51.400 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:07:51.900 [WARN] Proxy Client: unable to connect to 38.229.33.83:80 ("general SOCKS server failure")
30-11-2017, 19:07:52.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:07:53.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:07:54.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:08:08.900 [WARN] Proxy Client: unable to connect to 85.31.186.26:443 ("general SOCKS server failure")
30-11-2017, 19:08:48.900 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:08:51.900 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:08:52.900 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:08:53.900 [WARN] Proxy Client: unable to connect to 38.229.33.83:80 ("general SOCKS server failure")
30-11-2017, 19:08:55.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:08:57.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:09:01.000 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:09:34.300 [WARN] Proxy Client: unable to connect to 85.17.30.79:443 ("general SOCKS server failure")
30-11-2017, 19:09:50.000 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:09:54.600 [WARN] Proxy Client: unable to connect to 154.35.22.13:443 ("general SOCKS server failure")
30-11-2017, 19:10:50.900 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:10:54.600 [WARN] Proxy Client: unable to connect to 85.31.186.26:443 ("general SOCKS server failure")
30-11-2017, 19:10:55.900 [WARN] Proxy Client: unable to connect to 38.229.33.83:80 ("general SOCKS server failure")
30-11-2017, 19:10:56.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:10:57.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:10:58.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:11:07.000 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:11:09.100 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:11:54.900 [WARN] Proxy Client: unable to connect to 85.31.186.26:443 ("general SOCKS server failure")
30-11-2017, 19:12:00.600 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:12:01.900 [WARN] Proxy Client: unable to connect to 38.229.33.83:80 ("general SOCKS server failure")
30-11-2017, 19:12:03.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:12:05.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:12:42.300 [WARN] Proxy Client: unable to connect to 85.17.30.79:443 ("general SOCKS server failure")
30-11-2017, 19:12:55.900 [WARN] Proxy Client: unable to connect to 85.31.186.26:443 ("general SOCKS server failure")
30-11-2017, 19:13:00.900 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:13:01.100 [WARN] Proxy Client: unable to connect to 154.35.22.13:443 ("general SOCKS server failure")
30-11-2017, 19:14:01.900 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:14:03.900 [WARN] Proxy Client: unable to connect to 85.31.186.26:443 ("general SOCKS server failure")
30-11-2017, 19:14:05.900 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:14:07.000 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:14:08.200 [WARN] Proxy Client: unable to connect to 38.229.33.83:80 ("general SOCKS server failure")
30-11-2017, 19:14:08.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:14:09.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:14:10.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:15:04.900 [WARN] Proxy Client: unable to connect to 85.31.186.26:443 ("general SOCKS server failure")
30-11-2017, 19:15:11.900 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:15:13.900 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:15:14.900 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:15:16.200 [WARN] Proxy Client: unable to connect to 38.229.33.83:80 ("general SOCKS server failure")
30-11-2017, 19:15:17.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:15:19.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:15:56.300 [WARN] Proxy Client: unable to connect to 85.17.30.79:443 ("general SOCKS server failure")
30-11-2017, 19:16:13.000 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:16:15.100 [WARN] Proxy Client: unable to connect to 154.35.22.13:443 ("general SOCKS server failure")
30-11-2017, 19:17:07.000 [WARN] Proxy Client: unable to connect to 85.31.186.26:443 ("general SOCKS server failure")
30-11-2017, 19:17:08.900 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:17:09.900 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:17:10.900 [WARN] Proxy Client: unable to connect to 38.229.33.83:80 ("general SOCKS server failure")
30-11-2017, 19:17:11.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:17:12.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:17:13.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:17:13.900 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:18:07.900 [WARN] Proxy Client: unable to connect to 85.31.186.26:443 ("general SOCKS server failure")
30-11-2017, 19:18:09.900 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:18:10.900 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:18:11.900 [WARN] Proxy Client: unable to connect to 38.229.33.83:80 ("general SOCKS server failure")
30-11-2017, 19:18:13.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:18:14.900 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:18:15.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:18:52.300 [WARN] Proxy Client: unable to connect to 85.17.30.79:443 ("general SOCKS server failure")
30-11-2017, 19:19:08.900 [WARN] Proxy Client: unable to connect to 85.31.186.26:443 ("general SOCKS server failure")
30-11-2017, 19:19:11.200 [WARN] Proxy Client: unable to connect to 154.35.22.13:443 ("general SOCKS server failure")
30-11-2017, 19:19:12.000 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:19:13.000 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:19:13.900 [WARN] Proxy Client: unable to connect to 38.229.33.83:80 ("general SOCKS server failure")
30-11-2017, 19:19:14.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:19:15.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:19:16.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:20:10.600 [WARN] Proxy Client: unable to connect to 85.31.186.26:443 ("general SOCKS server failure")
30-11-2017, 19:20:42.900 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:20:44.900 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:20:45.900 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:20:46.900 [WARN] Proxy Client: unable to connect to 38.229.33.83:80 ("general SOCKS server failure")
30-11-2017, 19:20:48.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:20:50.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:21:07.000 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:21:08.000 [NOTICE] Bridge at '154.35.22.9:12166' isn't reachable by our firewall policy. Asking bridge authority instead.
30-11-2017, 19:21:08.000 [NOTICE] Bridge at '154.35.22.12:4304' isn't reachable by our firewall policy. Asking bridge authority instead.
30-11-2017, 19:21:08.000 [NOTICE] Bridge at '37.218.245.14:38224' isn't reachable by our firewall policy. Asking bridge authority instead.
30-11-2017, 19:21:08.000 [NOTICE] Bridge at '37.218.240.34:40035' isn't reachable by our firewall policy. Asking bridge authority instead.
30-11-2017, 19:21:08.000 [NOTICE] Bridge at '109.105.109.165:10527' isn't reachable by our firewall policy. Asking bridge authority instead.
30-11-2017, 19:21:08.000 [NOTICE] Bridge at '154.35.22.13:16815' isn't reachable by our firewall policy. Asking bridge authority instead.
30-11-2017, 19:21:08.000 [NOTICE] Bridge at '154.35.22.11:16488' isn't reachable by our firewall policy. Asking bridge authority instead.
30-11-2017, 19:21:08.000 [NOTICE] Bridge at '109.105.109.147:13764' isn't reachable by our firewall policy. Asking bridge authority instead.
30-11-2017, 19:21:08.000 [NOTICE] Bridge at '154.35.22.10:15937' isn't reachable by our firewall policy. Asking bridge authority instead.
30-11-2017, 19:21:08.000 [NOTICE] Bridge at '83.212.101.3:50002' isn't reachable by our firewall policy. Asking bridge authority instead.
30-11-2017, 19:21:08.000 [WARN] Could not choose valid address for JonbesheSabz
30-11-2017, 19:21:08.000 [WARN] Could not make a one-hop connection to $00DC6C4FA49A65BD1472993CF6730D54F11E0DBB. Discarding this circuit.
30-11-2017, 19:21:08.000 [NOTICE] We'd like to launch a circuit to handle a connection, but we already have 32 general-purpose client circuits pending. Waiting until some finish.
30-11-2017, 19:21:08.000 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:21:08.000 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:21:08.000 [WARN] Proxy Client: unable to connect to 38.229.33.83:80 ("general SOCKS server failure")
30-11-2017, 19:21:08.000 [WARN] Proxy Client: unable to connect to 154.35.22.11:80 ("general SOCKS server failure")
30-11-2017, 19:21:08.000 [WARN] Proxy Client: unable to connect to 154.35.22.10:80 ("general SOCKS server failure")
30-11-2017, 19:21:27.300 [WARN] Proxy Client: unable to connect to 85.17.30.79:443 ("general SOCKS server failure")
30-11-2017, 19:21:44.100 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:21:46.100 [WARN] Proxy Client: unable to connect to 154.35.22.13:443 ("general SOCKS server failure")
30-11-2017, 19:22:05.100 [WARN] Proxy Client: unable to connect to 85.17.30.79:443 ("general SOCKS server failure")
30-11-2017, 19:22:08.000 [WARN] Proxy Client: unable to connect to 154.35.22.9:443 ("general SOCKS server failure")
30-11-2017, 19:22:08.000 [WARN] Proxy Client: unable to connect to 192.99.11.54:443 ("general SOCKS server failure")
30-11-2017, 19:22:18.600 [WARN] Proxy Client: unable to connect to 85.31.186.26:443 ("general SOCKS server failure")
30-11-2017, 19:22:19.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:22:20.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:22:45.000 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:23:07.900 [NOTICE] Tried to fetch a descriptor directly from a bridge, but that bridge is not reachable through our firewall.
30-11-2017, 19:23:07.900 [NOTICE] Tried to fetch a descriptor directly from a bridge, but that bridge is not reachable through our firewall.
30-11-2017, 19:23:07.900 [NOTICE] Tried to fetch a descriptor directly from a bridge, but that bridge is not reachable through our firewall.
30-11-2017, 19:23:07.900 [NOTICE] Tried to fetch a descriptor directly from a bridge, but that bridge is not reachable through our firewall.
30-11-2017, 19:23:07.900 [NOTICE] Tried to fetch a descriptor directly from a bridge, but that bridge is not reachable through our firewall.
30-11-2017, 19:23:07.900 [NOTICE] Tried to fetch a descriptor directly from a bridge, but that bridge is not reachable through our firewall.
30-11-2017, 19:23:07.900 [WARN] Proxy Client: unable to connect to 154.35.22.10:80 ("general SOCKS server failure")
30-11-2017, 19:23:07.900 [WARN] Proxy Client: unable to connect to 154.35.22.11:80 ("general SOCKS server failure")
30-11-2017, 19:23:08.900 [WARN] Proxy Client: unable to connect to 192.99.11.54:443 ("general SOCKS server failure")
30-11-2017, 19:23:08.900 [WARN] Proxy Client: unable to connect to 154.35.22.9:443 ("general SOCKS server failure")
30-11-2017, 19:23:09.000 [WARN] Proxy Client: unable to connect to 154.35.22.10:80 ("general SOCKS server failure")
30-11-2017, 19:23:09.000 [WARN] Proxy Client: unable to connect to 154.35.22.11:80 ("general SOCKS server failure")
30-11-2017, 19:23:18.900 [WARN] Proxy Client: unable to connect to 85.31.186.26:443 ("general SOCKS server failure")
30-11-2017, 19:23:21.400 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:23:22.000 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:23:23.000 [WARN] Proxy Client: unable to connect to 38.229.33.83:80 ("general SOCKS server failure")
30-11-2017, 19:23:46.000 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:23:51.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:23:53.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:24:06.000 [WARN] Proxy Client: unable to connect to 154.35.22.13:443 ("general SOCKS server failure")
30-11-2017, 19:24:10.000 [WARN] Proxy Client: unable to connect to 154.35.22.9:443 ("general SOCKS server failure")
30-11-2017, 19:24:19.900 [WARN] Proxy Client: unable to connect to 85.31.186.26:443 ("general SOCKS server failure")
30-11-2017, 19:24:30.100 [WARN] Proxy Client: unable to connect to 85.17.30.79:443 ("general SOCKS server failure")
30-11-2017, 19:24:54.900 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:24:56.900 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:24:58.000 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:24:58.900 [WARN] Proxy Client: unable to connect to 38.229.33.83:80 ("general SOCKS server failure")
30-11-2017, 19:24:59.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:25:00.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:25:01.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:25:05.100 [WARN] Proxy Client: unable to connect to 154.35.22.13:443 ("general SOCKS server failure")
30-11-2017, 19:25:55.900 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:26:56.900 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:26:58.800 [WARN] Proxy Client: unable to connect to 85.31.186.26:443 ("general SOCKS server failure")
30-11-2017, 19:26:59.900 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:27:00.900 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:27:01.900 [WARN] Proxy Client: unable to connect to 38.229.33.83:80 ("general SOCKS server failure")
30-11-2017, 19:27:03.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:27:05.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:27:42.100 [WARN] Proxy Client: unable to connect to 85.17.30.79:443 ("general SOCKS server failure")
30-11-2017, 19:27:58.900 [WARN] Proxy Client: unable to connect to 85.31.186.26:443 ("general SOCKS server failure")
30-11-2017, 19:28:01.000 [WARN] Proxy Client: unable to connect to 154.35.22.13:443 ("general SOCKS server failure")
30-11-2017, 19:28:06.900 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:28:08.900 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:28:09.900 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:28:10.900 [WARN] Proxy Client: unable to connect to 38.229.33.83:80 ("general SOCKS server failure")
30-11-2017, 19:28:11.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:28:12.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:28:13.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:29:07.900 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:30:08.900 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:30:09.900 [WARN] Proxy Client: unable to connect to 85.31.186.26:443 ("general SOCKS server failure")
30-11-2017, 19:30:11.900 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:30:13.000 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:30:13.900 [WARN] Proxy Client: unable to connect to 38.229.33.83:80 ("general SOCKS server failure")
30-11-2017, 19:30:15.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:30:17.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:30:54.300 [WARN] Proxy Client: unable to connect to 85.17.30.79:443 ("general SOCKS server failure")
30-11-2017, 19:31:11.000 [WARN] Proxy Client: unable to connect to 85.31.186.26:443 ("general SOCKS server failure")
30-11-2017, 19:31:13.200 [WARN] Proxy Client: unable to connect to 154.35.22.13:443 ("general SOCKS server failure")
30-11-2017, 19:31:18.900 [WARN] Proxy Client: unable to connect to 85.31.186.98:443 ("general SOCKS server failure")
30-11-2017, 19:31:20.900 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:31:21.900 [WARN] Proxy Client: unable to connect to 38.229.1.78:80 ("general SOCKS server failure")
30-11-2017, 19:31:22.900 [WARN] Proxy Client: unable to connect to 38.229.33.83:80 ("general SOCKS server failure")
30-11-2017, 19:31:23.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:31:24.900 [WARN] Proxy Client: unable to connect to 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
30-11-2017, 19:31:25.900 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
30-11-2017, 19:31:47.400 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150
30-11-2017, 19:31:47.400 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
30-11-2017, 19:31:47.400 [NOTICE] Closing old Socks listener on 127.0.0.1:9150
30-11-2017, 19:31:47.900 [NOTICE] Delaying directory fetches: DisableNetwork is set.

Anonymous

December 01, 2017

Permalink

is there a reason for delaying 7.0.11 release?
TBB 7.0.11 from /~gk/builds is running fine.

Yes, there are actually two.

1) We wanted to pick up the new Tor security update.
2) We need to pick up a new Firefox (52.5.2esr) as one of the patches included in 52.5.1esr (which we picked up in the build you mention) seems to be not ready for release yet. It's causing test failures which still need to get investigated.

That said we hope to have new Tor Browser releases out tomorrow (we already built the new alpha and are currently signing it).

Anonymous

December 02, 2017

Permalink

TBB is again crashing at google maps (almost immediately, almost reproducible). Is it something knew and known? Is it regression within the ticket 16771? If it is know, I'll send you my backtrace.

Anonymous

December 02, 2017

Permalink

Please explain:
1) how to remember passwords in TOR;
2) how to start TOR with previous tabs.

Thanks.

Anonymous

December 02, 2017

Permalink

I find it wired that firefox reproducibly crashes on some web pages if and only if it is run in debugger. What does it mean?

Yes. The layout of the FTE files is not compatible with macOS' code signing requirement. We have https://trac.torproject.org/projects/tor/ticket/18495 for fixing that. There are no Scramblesuit default bridges anymore as the one we had sipped could not keep up with the load, see: https://trac.torproject.org/projects/tor/ticket/21536.

That said you should be able to run Scramblesuit bridges in Tor Browser nevertheless.

Anonymous

December 03, 2017

Permalink

Why comments to recent tor blog news, e.g. "New stable Tor releases, with security fixes" are disabled here?

Anonymous

December 05, 2017

Permalink

Got the problem with this tor version (0.3.1.9):

Dec 06 02:03:03.000 [notice] Heartbeat: Tor's uptime is XX:XX hours, with XX circuits open. I've sent XX.XX MB and received XX.XX GB.
Dec 06 02:03:03.000 [notice] Average packaged cell fullness: 65.XXX%. TLS write overhead: 4%
Dec 06 02:03:03.000 [notice] Diagnostic for issue 8387: Found 1 one-hop circuits more than 1800 seconds old! Logging 1...
Dec 06 02:03:03.000 [notice] #0 created at 2017-12-06 01:10:06. open, General-purpose client. Not marked for close. Package window: 1000. usable for new conns. Dirty since 2017-12-06 01:56:04 (4XX seconds vs 600-second cutoff).
Dec 06 02:03:03.000 [notice] It has been 2 seconds since I last called circuit_expire_old_circuits_clientside().

Added my comment to ticket 8387.

Anonymous

December 06, 2017

Permalink

I'm unable to view most California-based news organizations, including LA Times, and KTLA, as well as some Europeans ones, including BBC, using TOR.
Only https://ixquick-proxy.com/ works from Startpage.
Anyone experiencing similar issues?

Anonymous

December 07, 2017

Permalink

If JS is enabled, this test tells me that I have:

1000×600 24-bit TrueColor (working area: 984×600)

Is 984 safe value? Or is this test just wrong?

Anonymous

December 08, 2017

Permalink

Hi. Just before there's an avalanche of YouTube related questions: YouTube did a thing again. In order to use their site, Tor users would have to set their security setting to middle (temporarily).
This might not at all be the smartest or most secure way to do it, but it is a way.
Hope this will help someone and have a nice day.

Anonymous

December 09, 2017

Permalink

webgl.disable-angle;true
dom.indexedDB.enabled;false
is this ok until 7.0.11 release?

Anonymous

December 09, 2017

Permalink

Hello , Every time I attempt a new Tor circuit, the initial hookup stays the same: from me to C.R. (31.31.73.222), etc. WTF? This has remained like this for the most part, for three days. It feels wrong. Is it anything?

Anonymous

January 10, 2018

Permalink

If the internet connection goes down while connecting, you enter a world of bing noises and message boxes where you are told that the connection can't be established, and there is no quit option, just an ok button which tries again and fails. Again and again forever. Even though you've fixed the problem and reconnected.

Maybe someone would like to look into the possibility of: If Internet = OK, connect; if No Internet, stop the fucking endless loop and trigger Task Manager allowing a nasty forced termination. Or just self-destruct with a please restart the program message.

Thank you otherwise for a near-flawless program.