Opened 5 months ago

Closed 4 months ago

#24756 closed enhancement (fixed)

New default bridge: bridge-01.noisetor.net

Reported by: patrickod Owned by: patrickod
Priority: Medium Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords: tbb-bridges, TorBrowserTeam201801R
Cc: dgoulet, dcf Actual Points:
Parent ID: Points:
Reviewer: gk Sponsor:

Description

Capable of relaying 125MiB/sec at the moment with the option for expansion should it be utilized. Committed to at least 12 months of operation funded by Noisetor[0]

Bridge obfs4 216.252.162.21:46089 0DB8799466902192B6C7576D58D4F7F714EC87C1 cert=XPUwcQPxEXExHfJYX58gZXN7mYpos7VNAHbkgERNFg+FCVNzuYo1Wp+uMscl3aR9hO2DRQ iat-mode=0

[0] - http://tor.noisebridge.net

Child Tickets

Change History (13)

comment:1 Changed 5 months ago by patrickod

Derp that's meant to be 125MBit/sec.

comment:2 Changed 5 months ago by patrickod

Associated pull request to add bridge to OONI reachability test set - https://github.com/OpenObservatory/ooni-resources/pull/10

comment:3 Changed 5 months ago by arma

Cc: dgoulet dcf added

This is great! Thanks!

comment:4 Changed 4 months ago by gk

Keywords: TorBrowserTeam201801R added

patrickod: Do you want to write a proper patch for including the new bridge into Tor Browser or should we turn the data in comment:description into a proper one (I am fine either way)? I assume the latter and put it onto our review radar nevertheless.

comment:5 Changed 4 months ago by dcf

We usually ask the default bridges to block their ORPort (9001 in this case) so that you won't get any vanilla-Tor connections.

I did a port scan and found ports 22 (SSH), 9001 (ORPort), 9101 (?), and 46089 (obfs4) open. You might want to firewall all but 22 and 46089.

comment:6 Changed 4 months ago by patrickod

@gk I'm happy to do it, however I've not contributed to Tor Browser at all before. Would you have an example patch introducing a new bridge that I could use as a reference?

@dcf Thanks for the suggestion. Will update the configuration later tonight.

comment:7 in reply to:  6 Changed 4 months ago by cypherpunks

Replying to patrickod:

@gk I'm happy to do it, however I've not contributed to Tor Browser at all before. Would you have an example patch introducing a new bridge that I could use as a reference?

Examples: https://trac.torproject.org/projects/tor/attachment/ticket/21917/0001-Add-new-default-bridges-cymrubridge31-80-and-cymrubr.patch and
https://github.com/isislovecruft/tor-browser-bundle/tree/bug23166

comment:8 Changed 4 months ago by cypherpunks

Owner: changed from tbb-team to patrickod
Reviewer: gk
Status: newassigned

comment:9 Changed 4 months ago by gk

Keywords: TorBrowserTeam201801R removed

patrickod, thanks! You want to write a patch against the code in tor-browser-build, see e.g. https://gitweb.torproject.org/builders/tor-browser-build.git/commit/?id=5eb4c84fd87c80496dc522f44f26928f1330b814

comment:10 Changed 4 months ago by patrickod

@gk patch is here: https://git.patrickod.com/tor-browser-build/commit/?h=patrickod/add-noisetor-bridge&id=756b3f5673e71b392644898a3acffb2708c42855

Let me know if there's anything else that needs to be done on our end. I'm going to block the ORPort today also as per @dcf's comments.

comment:11 Changed 4 months ago by cypherpunks

Status: assignedneeds_review

comment:12 Changed 4 months ago by gk

Keywords: TorBrowserTeam201801R added

comment:13 Changed 4 months ago by gk

Resolution: fixed
Status: needs_reviewclosed

Looks good to me. Cherry-picked to master (commit ccf20f2ccb106dbe1fa44b1e569bba9ce3682ddf) and maint-7.5 (commit 5e4aa670cefc55756bd9f727bb9d23fc483f8f93). The upcoming 8.0a1 and 7.5 releases will have the bridge available.

Note: See TracTickets for help on using tickets.