A research group at the University of Minnesota generously agreed to running a default bridge for us. Let's use this ticket to coordinate the process of adding it to Tor Browser.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items ...
Show closed items
Linked items 0
Link issues together to show that they're related.
Learn more.
Thanks for setting up this bridge! I'm able to connect to your bridge's OR port but its obfs4 port seems unresponsive. Is your firewall allowing port 9000?
We keep having problem with firewall every once in a while. Is it fine if I change obfs4 port to 22 ? That would not be harmful to the clients in any way, right?
We keep having problem with firewall every once in a while. Is it fine if I change obfs4 port to 22 ? That would not be harmful to the clients in any way, right?
Yes, feel free to use port 22 instead. The most important thing is that the port will be consistently available.
Thanks for pointing that out. I've Corrected the config for the Bridge.
Thanks! For what it's worth, this was a usability issue and Roger filed #32753 (moved) to get it fixed. Everything's looking good now, so let's add your bridge to Tor Browser.
Tor Browser Team:
My task/32547 branch has a patch for tor-browser-build.
My task/32547 branch has a patch for tor-android-service.
Thanks. Looks good. I merged your commits to tor-android-service's master (commit 4a81e5806f36e7d0bf9492437d824599ecf4ff43) and tor-browser-build's master (commit 00f4ea3a18f1cbce16f256ca2b7c1c90ad3b1daf) and bumped the tor-android-service commit there to pick up the changes for mobile, too (commit 8f76d71e2a0923d3ca317f82ab5eeec124706e22).
I backported the latter two to maint-9.0 (commit 095dfed8762cd1756b3fc50ed4aa6e8f2d0dc849 and d6bd267e1747a14d2a326a36099bf8e79bbc6a91) to have the bridge available in the next stable release as well.