Opened 7 months ago

Closed 4 months ago

#32485 closed defect (worksforme)

Dead obfs4 Bridges on Tor Browser Android

Reported by: torify Owned by: tbb-team
Priority: Medium Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords: TorBrowserTeam202002
Cc: phw Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Hi All,

I had shared screenshots about dead (General SOCKS server failure) obfs4 bridges on Tor Browser Android few months ago. Also i heard a torrc option called UpdateBridgesFromAuthority and i wanted to try (on Windows) that. When i added that as "1" Tor Browser stuck at "Starting" step and when i removed that Tor Browser is working good. I have two (2) wish about this dead obfs4 bridges on TBA. First one is there any possibility to implement this torrc option to the TBA? And second one could you please tell us how works UpdateBridgesFromAuthority option on Tor Browser?

I marked this as Very High (if possible Immediate) because we can't use Tor Browser in a restricted country and this is sad for us.

Thanks in advance.

Kind Regards,

torify

Child Tickets

Attachments (1)

TBA-log (2.7 KB) - added by torify 6 months ago.
Tor Browser Android Connection Log File

Download all attachments as: .zip

Change History (17)

comment:1 Changed 7 months ago by torify

....because we can't use Tor Browser Android*.....

Last edited 7 months ago by torify (previous) (diff)

comment:2 Changed 7 months ago by nickm

Component: Core Tor/TorCircumvention

comment:3 Changed 7 months ago by torify

I found a trick. If you stuck at 30%, first try to connect with meek and then try to connect with obfs4
bridges. Problem is not solved.

EDIT: I noticed bug is still going on

Last edited 7 months ago by torify (previous) (diff)

comment:4 Changed 7 months ago by sysrqb

Component: CircumventionApplications/Tor Browser
Keywords: TorBrowserTeam201911 added; dead obfs4 bridge removed
Owner: set to tbb-team
Priority: Very HighHigh
Severity: MajorNormal
Version: Tor: 0.4.1.6

The logs refer to https://gitweb.torproject.org/builders/tor-browser-build.git/tree/projects/tor-browser/Bundle-Data/PTConfigs/bridge_prefs.js#n11

WARN: Proxy Client: unable to connect 85.31.186.98:443 ("general SOCKS server failure")

comment:5 Changed 7 months ago by sysrqb

Status: newneeds_information

I just tested that bridge, and it is working now. Maybe there was maintenance?

11/18/19, 16:13:29.863 [NOTICE] Switching to guard context "bridges" (was using "default")
11/18/19, 16:13:30.184 [NOTICE] Delaying directory fetches: No running bridges
11/18/19, 16:13:31.332 [NOTICE] new bridge descriptor 'griinchux' (fresh): $011F2599C0E9B27EE74B353155E244813763C3E5~griinchux at 85.31.186.98

comment:6 Changed 7 months ago by sysrqb

Apparently some networks (country? countries?) are blocking this bridge.

comment:7 in reply to:  6 Changed 6 months ago by torify

Replying to sysrqb:

Apparently some networks (country? countries?) are blocking this bridge.

Yes, i am living in a restricted country and my country blocked Tor network, torproject.org domains and more.

Changed 6 months ago by torify

Attachment: TBA-log added

Tor Browser Android Connection Log File

comment:8 Changed 6 months ago by torify

My attachment is from 2019/11 and those screenshots are from older versions. I tried now again but TBA stuck at 30% (loading_status) step and i received "NOTICE: No circuits are opened. Relaxed timeout for circuit 4 (a General-purpose client 1-hop circuit in state doing handshakes with channel state open) to 60000ms. However, it appears the circuit has timed out anyway." notification message again like in log file.

comment:9 Changed 6 months ago by gk

Status: needs_informationnew

comment:10 Changed 6 months ago by pili

Keywords: TorBrowserTeam201912 added; TorBrowserTeam201911 removed

Moving tickets to December

comment:11 Changed 5 months ago by phw

Cc: phw added

comment:12 Changed 5 months ago by sysrqb

Keywords: TorBrowserTeam202001 added; TorBrowserTeam201912 removed

comment:13 Changed 4 months ago by arma

Hopefully useful thoughts:

(A) It is very reasonable that one (or all) of the default obfs4 bridges are blocked in your country. China blocks them quickly, and periodically we hear reports from places like Venezuela and Peru that they've grabbed the list of default bridges and blocked them by IP address.

(B) You probably want to leave UpdateBridgesFromAuthority alone. It was potentially a good design at the beginning, but we never finished building it, so it's very unlikely that it will do what you want here.

(C) You should be sure to watch #30767, the ticket about how custom obfs4 bridges don't work on Tor Browser Android. This could be your bug right here.

comment:14 Changed 4 months ago by boklm

Priority: HighMedium
Status: newneeds_information

comment:15 Changed 4 months ago by pili

Keywords: TorBrowserTeam202002 added; TorBrowserTeam202001 removed

Moving tickets to February

comment:16 Changed 4 months ago by sysrqb

Resolution: worksforme
Status: needs_informationclosed

Hi torify,

We have a new default bridge included in the newest update (and that should work for you, for a short time). We also fixed the bug that prevented using non-default obfs4 bridges (#30767). This is included in the next Tor Browser alpha release (it should be available later this week).

Note: See TracTickets for help on using tickets.