Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#17747 closed enhancement (fixed)

Add ndnop3 as a new default obfs4 bridge

Reported by: dcf Owned by: tbb-team
Priority: Medium Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords: tbb-bridges TorBrowserTeam201512R
Cc: yawning Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Here is a new bridge set up to be a default obfs4 bridge. See discussion on tor-assistants on 2015-12-03 "schanenlied obfs4 bridge is tiny?"

Bridge obfs4 109.105.109.165:24215 8DFCD8FB3285E855F5A55EDDA35696C743ABFC4E cert=Bvg/itxeL4TWKLP6N1MaQzSOC6tcRIBv6q57DYAZc3b2AzuM+/TfB7mqTFEfXILCjEwzVA iat-mode=0

Child Tickets

Change History (9)

comment:1 Changed 4 years ago by dcf

Status: newneeds_review

comment:2 Changed 4 years ago by gk

Status: needs_reviewneeds_information

Should it be just the fourth obfs4 default bridge? Or maybe the first? Or...? Not sure if that really matters but I figured we might be able to optimize things a bit with a proper order (and there was no patch suggesting me what to do :) ).

comment:3 in reply to:  2 ; Changed 4 years ago by dcf

Cc: yawning added

Replying to gk:

Should it be just the fourth obfs4 default bridge? Or maybe the first? Or...? Not sure if that really matters but I figured we might be able to optimize things a bit with a proper order (and there was no patch suggesting me what to do :) ).

Hmm; actually I have no idea whether order matters either. We should probably ask someone else. I'll Cc yawning.

If order matters, then we want this bridge to be higher priority than schanenlied; that's the rate-limited one the tor-assistants thread is about. This line is schanenlied:

pref("extensions.torlauncher.default_bridge.obfs4.1", "obfs4 178.209.52.110:443 67E72FF33D7D41BF11C569646A0A7B4B188340DF cert=Z+cv8z19Qb8RxWlkagp7SxiDQN++b7D2Tntowhf+j4D15/kLuj3EoSSGvuREGPc3h60Ofw iat-mode=0");

comment:4 in reply to:  3 Changed 4 years ago by yawning

Replying to dcf:

Hmm; actually I have no idea whether order matters either. We should probably ask someone else. I'll Cc yawning.

If order matters, then we want this bridge to be higher priority than schanenlied; that's the rate-limited one the tor-assistants thread is about. This line is schanenlied:

pref("extensions.torlauncher.default_bridge.obfs4.1", "obfs4 178.209.52.110:443 67E72FF33D7D41BF11C569646A0A7B4B188340DF cert=Z+cv8z19Qb8RxWlkagp7SxiDQN++b7D2Tntowhf+j4D15/kLuj3EoSSGvuREGPc3h60Ofw iat-mode=0");

That bridge should probably just be removed all together. I'll leave it running as long as needed, but I'd like to decommission it so I can retask the host it's on. As far as ndnop goes, it probably should be first on the list since the other bridges are smaller capacity (or overloaded in the case of asn's).

comment:5 Changed 4 years ago by gk

Status: needs_informationneeds_review

I've replaced schanenlied with ndnop3 in bug_17747 (https://gitweb.torproject.org/user/gk/tor-browser-bundle.git/commit/?h=bug_17747).

comment:6 Changed 4 years ago by mcs

r=mcs
Looks good.

comment:7 Changed 4 years ago by boklm

Looks good to me too.

comment:8 Changed 4 years ago by gk

Resolution: fixed
Status: needs_reviewclosed

Okay, schanenlied is off the hook then. I applied this patch to all branches.

Last edited 4 years ago by gk (previous) (diff)

comment:9 Changed 4 years ago by dcf

Keywords: tbb-bridges added
Note: See TracTickets for help on using tickets.