Tor Browser 13.5 doesn't show default Built-in bridges, is it a bug or a feature?

Feedback Tor Browser Feedback
1

OS: Linux
Tor Browser Version: 13.5

The issue:
Updated Tor Browser to 13.5, but unlike previous versions, all of the default Built-in brigdes are not shown.
The … menu right to the “Built-in” text only have 1 option “Remove all bridges”.

Desired solution:
Show built-in bridges like before and make it editable.

But If this is a intended feature, I wish dev team could reconsider it.

My Reasons:

I live in a place with heavy censorship. In previous censor events i can tweak default Built-in bridges to make them work when internet is blocked,for example changing domain front. Please see the section about “Change the domain front” in the link below.

relevant link:

In addition,in previous versions when i can seen the default Built-in bridges,I can also backup the default bridges easily, It might sounds strange to some but I really do need to backup the default bridges for legit reasons. But now since the bridges can not be seen, thus it can not be edited in Tor Browser. and I can not backup the bridges now.

I really appreciate the works of tor team and thank you for your hard works and constant helps in maintaining internet access freedom. I wish tor browser become better and better.
Thank you all.

4 Likes
2

The list of current default bridges can be found in the pt_config.json file in the tor-expert-bundle: Tor Project | Download Tor

Or more directly, it can be found in tor-browser-build’s gitlab repo here: projects/tor-expert-bundle/pt_config.json · main · The Tor Project / Applications / tor-browser-build · GitLab

In the future, you should really just be adding new bridge-lines via the Replace Bridges button in about:preferences#connection rather than modifying the browser’s core configuration.

3 Likes
3

Hey @Radar451, thank you for the feedback. I’m curious how you were going about this workaround previously – I’m assuming you were:

  • Copying the built-in bridge address(es) from the bridge cards
  • Selecting “Add a Bridge Manually”
  • Pasting the built-in bridge address(es) here
  • Making the desired modifications
  • Hitting the OK/Connect button

Does that sound correct?

4

Thanks for replying.

The “replace bridge (used to be called ‘add bridges’)” function can not solve this problem alone. For I wish to backup and edit existing default built-in bridges used to be shown within Tor browser itself, which was shown to users before version 13.5.

And the reason for this is because I can not access to any of the links you provided without circumvention tools.

As I said there is a strong state censorship, thus I do not have direct access to most foreign websites, including not limited to Tor official website and any tor repos on gitlab.

So if I can not see the tor bridges within the Tor browser itself then I can not edit the domain-fronting for the workarounds as easy as before.

“rather than modifying the browser’s core configuration.”

I never edited core configuration files themselves.
Then still I known I can dig into tor configuration files to get the bridges but I don’t believe hiding the default bridges from users in the Tor browser itself,like version 13.5 ,is a good approach.

If it is for security concern, then I think this is “Security through obscurity” which is not good. Because it only hinder users like me to use workarounds easily. And State censors can always get the bridges by any other means. That is why i wish Tor dev team could reconsider it.

2 Likes
5

@donuts Thank you for replying.

Almost correct. Sorry i forgot to mention this. Clarifying my steps will make my issue more clearly. Thank you for reminding me.

My detailed steps are as follows:

1. Copying the built-in bridge address(es) from the bridge cards
2. Back up the copied built-in bridges
3. Edit the domain fronting of the copied built-in bridge address(es) 
4. Selecting “Add a Bridge Manually”
5. Pasting the modified built-in bridge address(es) here
6. Hitting the OK/Connect button

And with Tor browser 13.5. because I can not seen the default built-in bridges in Tor browser itself, I can not do the step one “Copying the built-in bridge address(es) from the bridge cards” as easily as before.

1 Like
6

Thanks @Radar451! Could you clarify one last thing for me please – what’s the purpose behind backing up built-in bridges, as you described here?

If you’d feel more comfortable doing so, please feel free to send me a direct message instead :slight_smile:

7

For reference I’ve opened an issue for this pain point on Gitlab, where we’ve began discussing potential workarounds:

1 Like
8

@donuts Thank you for opening an issue in gitlab for me.

Sorry I might need to clear some confusion first.

There is no way to “edit” the built-in bridges

Sorry my use of word “Edit” here might created a misunderstanding. I don’t want a new feature created to edit the built-in bridges directly in tor browser. And I don’t wish to increase tor dev’s workload to add new feature. And I certainly don’t want Tor browser to be too bloated in this way.

What I meant is that I want to be able to use the workaround in the steps I mentioned like before : Copy the built-in bridges,then backup and edit them in a file. then add the edited bridge to Tor browser. So just be able to see and copy the default built-in bridges in Tor browser like previous versions is good enough for me.

what’s the purpose behind backing up built-in bridges, as you described here?

One reason that I backup bridges is so that i can edit domain fronting directly in another file and don’t have to always copy the built-in bridges from Tor browser.

the built-in bridges, since they change all the time.

This is another reason. I think it is reasonable to constantly change built-in bridges, and I agree that cycle around bridges is more censorship resilient. I believe this approach is good and I think Tor browser should keep doing it.

But a little problem is that in my previous experience, sometimes new bridges doesn’t work well like previous one, or in the worst case they might not work at all. But the old bridges might still works for some time. So if I have backup old bridges I would still have an option to bypass censorship.

I know it is not secure to use old bridges but atleast in this way I have free internet access, and I can also report issues and feedbacks regarding new updates. And I will be able to get new Tor browser updates if there is a new fix released.

One last reason to backup Built-in bridges in recent versions of Tor browser is that it will make it possible to share them with people who have very old version of Tor browser.

As the bridges in those very old version probably won’t work, and due to censorships they might not be able use the request bridges nor access to Tor official bridge pages, and they might not be able to get brdiges via E-mail neither. Also they might not have other means to bypass censorship to update their circumvention tools.

So sharing new built-in bridges in recent versions with them might give them workable bridges to gain free internet access, in doing so they can update their circumvention tools including Tor browsers to the latest versions.

3 Likes
9

@Radar451 Thanks very much for the extra details! Judging by the direction of the conversation in Gitlab, it looks like we’ll be re-implementing the ability to copy built-in bridges addresses to your clipboard in the near future.

2 Likes