New Release: Tor 0.3.3.9 (Bridge Authority Update)

 

Tor 0.3.3.9 moves to a new bridge authority. The only people who need to upgrade are people who operate a bridge relay — so their bridge address can resume being given out to censored users, and so their stats can resume being included in the metrics pages.

Changes in version 0.3.3.9 - 2018-07-13

  • Directory authority changes:
    • The "Bifroest" bridge authority has been retired; the new bridge authority is "Serge", and it is operated by George from the Tor BSD Diversity project. Closes ticket 26771.

We also put out new oldstable releases for 0.2.9.16 and 0.3.2.11, and those releases include other backported fixes:
https://gitweb.torproject.org/tor.git/tree/ReleaseNotes?h=tor-0.2.9.16
https://gitweb.torproject.org/tor.git/tree/ReleaseNotes?h=tor-0.3.2.11

If for whatever reason you can't upgrade yet, you can also manually switch to advertising your bridge descriptor to the new bridge authority by using this torrc line:

AlternateBridgeAuthority Serge orport=9001 bridge 66.111.2.131:9030 BA44 A889 E64B 93FA A2B1 14E0 2C2A 279A 8555 C533

Anonymous

July 16, 2018

Permalink

all v3 hidden services are dead (cannot find any HsDir):

[notice] Closed 2 streams for service [scrubbed].onion for reason resolve failed. Fetch status: No more HSDir available to query.

old onion services are OKAY

Anonymous

July 17, 2018

Permalink

We also put out new oldstable releases for 0.2.9.16 and 0.3.2.11

oldstable - for 0.3.2.x, LTS - for 0.2.9.x

Anonymous

July 19, 2018

Permalink

7/19/2018 9:36:45 AM.400 [WARN] Proxy Client: unable to connect to 154.35.22.12:4304 ("general SOCKS server failure")

Anonymous

July 19, 2018

Permalink

The proxy server is refusing connections

Firefox is configured to use a proxy server that is refusing connections.

Check the proxy settings to make sure that they are correct.
Contact your network administrator to make sure the proxy server is working.

Anonymous

July 29, 2018

Permalink

If you care why sometimes users say Tor "stalls" during bootstrap, see:

[07-29 14:05:34] Torbutton INFO: tor SOCKS: https://www.https-rulesets.org/v1//latest-rulesets-timestamp via
--unknown--:7c78468ddbed6e418db8215adc6237b1
Tor NOTICE: Bootstrapped 10%: Finishing handshake with directory server
Tor NOTICE: Bootstrapped 15%: Establishing an encrypted directory connection
Tor NOTICE: Bootstrapped 20%: Asking for networkstatus consensus
Tor NOTICE: Bootstrapped 25%: Loading networkstatus consensus
[07-29 14:06:39] TorLauncher INFO: NOTICE CONSENSUS_ARRIVED

More than a minute nothing happens: no cpu/disk/net activity. By what wonderful way does consensus arrive here?!

Anonymous

August 06, 2018

Permalink

Bridges metrics gone crazy right after update, it says that their amount has decreased from near 1500 to about 500, why? Are 1000 bridges really become disconnected from TOR Network or it's just metrics bug?