Can not request bridges from torproject.org (App Engine is broken for moat)

Can not request bridges from torproject.org , Tor gets stuck at Contacting BridgeDB. please wait. Direct connection to Tor Works. TorBrowser 8a5

Trac:
Username: Dbryrtfbcbhgf

added GeorgKoppen201804 TorBrowserTeam201804R component::applications/tor launcher owner::tbb-team priority::medium reporter::Dbryrtfbcbhgf resolution::fixed severity::normal status::closed type::defect labels

#25804 (moved) snowflake and moat stopped working

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

Looking closer dcf seems to have #25804 (moved) for snowflake despite the generic title. Let's have that one for moat then.

The problem in #25804 (moved) is affecting Moat as well because we are doing something like

./TorBrowser/Tor/PluggableTransports/meek-client" "-url" "https://tor-bridges-hyphae-channel.appspot.com" "-front" "www.google.com" "--helper" "127.0.0.1:44219

I leave this ticket in the Tor Browser component right now even though we can't do anything about it until the issue at the BridgeDB side gets solved (or the App Engine starts to work for us again).

Trac:
Cc: N/A to mcs, brade, hiro
Summary: Can not request bridges from torproject.org to Can not request bridges from torproject.org (App Engine is broken for moat)
Status: closed to reopened
Resolution: duplicate to N/A

Replying to gk:

Looking closer dcf seems to have #25804 (moved) for snowflake despite the generic title. Let's have that one for moat then.

The problem in #25804 (moved) is affecting Moat as well because we are doing something like {{{ ./TorBrowser/Tor/PluggableTransports/meek-client" "-url" "https://tor-bridges-hyphae-channel.appspot.com" "-front" "www.google.com" "--helper" "127.0.0.1:44219 }}}

I leave this ticket in the Tor Browser component right now even though we can't do anything about it until the issue at the BridgeDB side gets solved (or the App Engine starts to work for us again).

Oh, wait… what is the issue on the BridgeDB server-side? (Did you maybe mean fixing/updating the middleware server for the meek-reflector?)

Let's work around that for now. See bug_25807 (https://gitweb.torproject.org/user/gk/tor-launcher.git/commit/?h=bug_25807&id=add227697f9af12056ca26f6e510572cd9c5faef) in my public tor-launcher repo for a patch that works for me.

Trac:
Keywords: N/A deleted, TorBrowserTeam201804R, GeorgKoppen201804 added
Status: reopened to needs_review
Component: Applications/Tor Browser to Applications/Tor Launcher

Replying to gk:

Let's work around that for now. See bug_25807 (https://gitweb.torproject.org/user/gk/tor-launcher.git/commit/?h=bug_25807&id=add227697f9af12056ca26f6e510572cd9c5faef) in my public tor-launcher repo for a patch that works for me.

r=mcs Your patch looks fine, but won't it be easy to block Moat now?

Replying to mcs:

Replying to gk:

Let's work around that for now. See bug_25807 (https://gitweb.torproject.org/user/gk/tor-launcher.git/commit/?h=bug_25807&id=add227697f9af12056ca26f6e510572cd9c5faef) in my public tor-launcher repo for a patch that works for me.

r=mcs Your patch looks fine, but won't it be easy to block Moat now?

Yes, it will be much easier now. However, we don't have a setup ready to move away from Google. Thus, we are faced with the option to leave it broken for now or make it working again for users which could help shaking out more Moat related bugs or just give alpha users bridges in areas where the appengine is not blocked. It seems to me the latter is preferable (while we are trying to solve this issue in a more sustainable way).

Thanks for the review, I applied the patch to master (commit add227697f9af12056ca26f6e510572cd9c5faef).

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

closed

mentioned in issue #25986 (moved)

moved to tpo/applications/tor-launcher#25807 (closed)

mentioned in issue tpo/anti-censorship/pluggable-transports/snowflake#25804 (closed)

mentioned in issue tpo/anti-censorship/bridgedb#25986