Opened 2 years ago

Closed 23 months ago

#17330 closed task (fixed)

Figure out what happens when a user's chosen transport is removed from bridge_prefs.js in an update

Reported by: dcf Owned by: tbb-team
Priority: Medium Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords: meek
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

I am planning to deactivate meek-amazon. I planned to first simply remove it as an option in Tor Browser by removing the meek-amazon line from bridge_prefs.js. That leaves the question of what happens when someone is using meek-amazon, and then they upgrade to a newer Tor Browser that doesn't have meek-amazon in bridge_prefs.js?

If it continues using a cached meek-amazon bridge line, that's great; that's the best outcome. We'll keep the bridge running for a while.

If it crashes or falls back to no pluggable transport, then we'll have to think about it.

Does anyone know offhand what will happen?

Child Tickets

Attachments (2)

removed-bridge-1.png (8.0 KB) - added by dcf 23 months ago.
Dialog telling you your chosen transport is missing.
removed-bridge-2.png (37.0 KB) - added by dcf 23 months ago.
Bridge configuration dialog after you've acknowledged that your transport is missing.

Download all attachments as: .zip

Change History (4)

comment:1 Changed 2 years ago by mcs

For the built-in bridge choices (including meek-amazon), Tor Launcher will detect this situation during startup (no bridges are available that match the configured type). An error alert like this will be shown:

No provided bridges that have the transport type meek-amazon are available.
Please adjust your settings.

Then the Connect/Configure wizard will be re-displayed, so users will be forced to adjust their configuration.

Changed 23 months ago by dcf

Attachment: removed-bridge-1.png added

Dialog telling you your chosen transport is missing.

Changed 23 months ago by dcf

Attachment: removed-bridge-2.png added

Bridge configuration dialog after you've acknowledged that your transport is missing.

comment:2 Changed 23 months ago by dcf

Resolution: fixed
Severity: Normal
Status: newclosed

I tried it myself it it happened just as you described. I chose meek-amazon, closed the browser, deleted the meek-amazon line from Browser/TorBrowser/Data/Browser/profile.default/preferences/extension-overrides.js, and restarted.

Dialog telling you your chosen transport is missing.

Bridge configuration dialog after you've acknowledged that your transport is missing.

Note: See TracTickets for help on using tickets.