Include default bridges configuration in Tor Messenger

In tor-browser-bundle.git/Bundle-Data/PTConfigs/bridge_prefs.js there is configuration for the default bridges. We should include that configuration in the default Tor Messenger profile.

added component::archived/tor messenger owner::boklm priority::medium resolution::fixed severity::normal status::closed type::defect labels

I assume that https://gitweb.torproject.org/tor-messenger-build.git/commit/?id=7a1c6fd121dd001eb999ef03ebbbed264da37026 fixes #17476 (closed) as well?

Ugh, I'm not sure how I feel about having yet another place we need to edit when we change the bridge list (In particular the obfs4 bridges are subject to change soon because of capacity reasons).

Replying to arlolra:

I assume that https://gitweb.torproject.org/tor-messenger-build.git/commit/?id=7a1c6fd121dd001eb999ef03ebbbed264da37026 fixes #17476 (closed) as well?

Yes, this and the latest commit to use meek in standalone mode should fix #17476 (closed).

Replying to yawning:

Ugh, I'm not sure how I feel about having yet another place we need to edit when we change the bridge list (In particular the obfs4 bridges are subject to change soon because of capacity reasons).

We are using the bridge_prefs.js file from tor-browser-bundle.git so there is only one place to edit. We still need to think about updating the hash of the tor-browser-bundle.git commit we use when there are bridge updates, but we can't use the latest commit automatically or this would make the build unreproducible.

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

closed