Opened 3 years ago

Last modified 9 months ago

#20251 new defect

Mac Sierra Rend stream

Reported by: metabaron Owned by:
Priority: Medium Milestone:
Component: Archived/Obfsproxy Version:
Severity: Normal Keywords: Mac Sierra
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Fresh install of Tor Browser following the download of the latest version of Tor Browser from the official website (with signature confirmed).
Removed ALL previous directory related to Tor so this really is a fresh start as much fresh as "find" command cannot find any mention of TorBrowser on the hard drive.

PS: same behaviour with latest version of Tor Browser following the upgrade to Mac Sierra (hence the reason I think this is a problem on Mac Sierra and not Tor itself).

Install tor and configure obfuscation 4
Start tor
(so far so good most of the time)
Try to access ANY tor website
Browse it for a while.
Suddenly, no more connection at all
Need to stop Tor Browser and start a new Tor Browser (from scratch, not a new window) to retrieve some connection.
Repeat
Cry

Here is a log:
27/9/16, 2:15:16.000 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
27/9/16, 2:15:16.000 [NOTICE] Opening Socks listener on 127.0.0.1:9150
27/9/16, 2:15:17.600 [NOTICE] Bootstrapped 5%: Connecting to directory server
27/9/16, 2:15:17.600 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server
27/9/16, 2:15:18.900 [NOTICE] Bootstrapped 15%: Establishing an encrypted directory connection
27/9/16, 2:15:19.100 [NOTICE] Bootstrapped 20%: Asking for networkstatus consensus
27/9/16, 2:15:19.500 [NOTICE] new bridge descriptor 'XXXXX' (fresh): XXXXXX at XXX.XXX.XXX.XXX
27/9/16, 2:15:19.500 [NOTICE] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
27/9/16, 2:15:20.100 [NOTICE] Bootstrapped 25%: Loading networkstatus consensus
27/9/16, 2:15:25.100 [NOTICE] Bootstrapped 80%: Connecting to the Tor network
27/9/16, 2:15:25.900 [NOTICE] Bootstrapped 90%: Establishing a Tor circuit
27/9/16, 2:15:26.900 [NOTICE] Tor has successfully opened a circuit. Looks like client functionality is working.
27/9/16, 2:15:26.900 [NOTICE] Bootstrapped 100%: Done
27/9/16, 2:15:28.100 [NOTICE] New control connection opened from 127.0.0.1.
27/9/16, 2:15:28.300 [NOTICE] New control connection opened from 127.0.0.1.
27/9/16, 2:19:34.900 [NOTICE] Rend stream is 120 seconds late. Giving up on address '[scrubbed].onion'.
27/9/16, 2:19:34.900 [NOTICE] Rend stream is 120 seconds late. Giving up on address '[scrubbed].onion'.
27/9/16, 2:19:34.900 [NOTICE] Rend stream is 120 seconds late. Giving up on address '[scrubbed].onion'.
27/9/16, 2:19:34.900 [NOTICE] Rend stream is 120 seconds late. Giving up on address '[scrubbed].onion'.
27/9/16, 2:19:34.900 [NOTICE] Rend stream is 120 seconds late. Giving up on address '[scrubbed].onion'.
27/9/16, 2:19:34.900 [NOTICE] Rend stream is 120 seconds late. Giving up on address '[scrubbed].onion'.
27/9/16, 2:21:27.900 [NOTICE] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
27/9/16, 2:21:35.900 [NOTICE] Rend stream is 120 seconds late. Giving up on address '[scrubbed].onion'.
27/9/16, 2:21:35.900 [NOTICE] Rend stream is 120 seconds late. Giving up on address '[scrubbed].onion'.
27/9/16, 2:21:35.900 [NOTICE] Rend stream is 120 seconds late. Giving up on address '[scrubbed].onion'.
27/9/16, 2:21:35.900 [NOTICE] Rend stream is 120 seconds late. Giving up on address '[scrubbed].onion'.
27/9/16, 2:21:35.900 [NOTICE] Rend stream is 120 seconds late. Giving up on address '[scrubbed].onion'.
27/9/16, 2:21:35.900 [NOTICE] Rend stream is 120 seconds late. Giving up on address '[scrubbed].onion'.
27/9/16, 2:23:36.900 [NOTICE] Rend stream is 120 seconds late. Giving up on address '[scrubbed].onion'.
27/9/16, 2:23:36.900 [NOTICE] Rend stream is 120 seconds late. Giving up on address '[scrubbed].onion'.
27/9/16, 2:23:36.900 [NOTICE] Rend stream is 120 seconds late. Giving up on address '[scrubbed].onion'.
27/9/16, 2:23:36.900 [NOTICE] Rend stream is 120 seconds late. Giving up on address '[scrubbed].onion'.
27/9/16, 2:23:36.900 [NOTICE] Rend stream is 120 seconds late. Giving up on address '[scrubbed].onion'.
27/9/16, 2:23:36.900 [NOTICE] Rend stream is 120 seconds late. Giving up on address '[scrubbed].onion'.

Child Tickets

Change History (7)

comment:1 Changed 3 years ago by metabaron

Small update once I tried to reload the site when I waited for like 5 minutes:
27/9/16, 2:31:32.500 [WARN] Proxy Client: unable to connect to 109.105.109.165:10527 ("general SOCKS server failure")
27/9/16, 2:31:32.500 [WARN] Proxy Client: unable to connect to 192.99.11.54:443 ("general SOCKS server failure")
27/9/16, 2:31:32.500 [WARN] Proxy Client: unable to connect to 154.35.22.9:80 ("general SOCKS server failure")
27/9/16, 2:31:40.900 [NOTICE] Rend stream is 120 seconds late. Giving up on address '[scrubbed].onion'.
27/9/16, 2:33:32.600 [WARN] Proxy Client: unable to connect to 109.105.109.147:13764 ("general SOCKS server failure")
27/9/16, 2:33:32.600 [WARN] Proxy Client: unable to connect to 83.212.101.3:50000 ("general SOCKS server failure")
27/9/16, 2:33:32.600 [WARN] Proxy Client: unable to connect to 198.245.60.50:443 ("general SOCKS server failure")
27/9/16, 2:33:32.600 [WARN] Proxy Client: unable to connect to 154.35.22.11:443 ("general SOCKS server failure")
27/9/16, 2:33:32.600 [WARN] Proxy Client: unable to connect to 154.35.22.12:1894 ("general SOCKS server failure")
27/9/16, 2:33:32.600 [WARN] Proxy Client: unable to connect to 154.35.22.13:443 ("general SOCKS server failure")
27/9/16, 2:35:32.700 [WARN] Proxy Client: unable to connect to 109.105.109.165:10527 ("general SOCKS server failure")
27/9/16, 2:35:32.700 [WARN] Proxy Client: unable to connect to 192.99.11.54:443 ("general SOCKS server failure")
27/9/16, 2:35:32.700 [WARN] Proxy Client: unable to connect to 154.35.22.10:80 ("general SOCKS server failure")
27/9/16, 2:35:32.700 [WARN] Proxy Client: unable to connect to 154.35.22.9:80 ("general SOCKS server failure")
27/9/16, 2:35:32.900 [NOTICE] Delaying directory fetches: No running bridges
27/9/16, 2:37:32.700 [WARN] Proxy Client: unable to connect to 154.35.22.12:1894 ("general SOCKS server failure")

comment:2 Changed 3 years ago by cypherpunks

#20250 could be related. Mac Sierra (10.12) and PTs.

But what if it's about updated censorship itself and ability to block obfs4?

Can someone with no censored network (vpn to outside of censorship) to test Tor Browser on Mac Sierra with obfs4 (and meek just in case)?.

comment:3 Changed 3 years ago by cypherpunks

Component: ObfuscationObfuscation/Obfsproxy
Owner: set to asn

comment:4 Changed 3 years ago by cypherpunks

Try to access ANY tor website
Suddenly, no more connection at all

What about non onion links? like google.com?

comment:5 in reply to:  2 Changed 3 years ago by tordevSZ0

Replying to cypherpunks:

#20250 could be related. Mac Sierra (10.12) and PTs.

But what if it's about updated censorship itself and ability to block obfs4?

Can someone with no censored network (vpn to outside of censorship) to test Tor Browser on Mac Sierra with obfs4 (and meek just in case)?.

cypherpunks, I am writing this comment using TorBrowser with meek on a machine running 10.11.6. The two machines I have tested using 10.12 are in the same censored country, but fail to maintain the meek connection. The problem is that meek-client is crashing.

comment:6 Changed 9 months ago by teor

Owner: asn deleted
Status: newassigned

asn does not need to own any obfuscation tickets any more. Default owners are trouble.

comment:7 Changed 9 months ago by cohosh

Status: assignednew

tickets are unassigned, reverting to 'new'

Note: See TracTickets for help on using tickets.