New default bridge: bridge-01.noisetor.net

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

added TorBrowserTeam201801R component::applications/tor browser owner::patrickod priority::medium resolution::fixed reviewer::gk severity::normal status::closed tbb-bridges type::enhancement labels

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

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

This is great! Thanks!

Trac:
Cc: N/A to dgoulet, dcf

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.

Trac:
Keywords: N/A deleted, TorBrowserTeam201801R added

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.

@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.

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

Trac:
Reviewer: N/A to gk
Owner: tbb-team to patrickod
Status: new to assigned

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

Trac:
Keywords: TorBrowserTeam201801R deleted, N/A added

@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.

Trac:
Status: assigned to needs_review

Trac:
Keywords: N/A deleted, TorBrowserTeam201801R added

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.

Trac:
Status: needs_review to closed
Resolution: N/A to fixed

closed

moved to tpo/applications/tor-browser#24756 (closed)