[tor-bugs] #17330 [Tor Browser]: Figure out what happens when a user's chosen transport is removed from bridge_prefs.js in an update

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#17330: Figure out what happens when a user's chosen transport is removed from
bridge_prefs.js in an update
-------------------------+--------------------------
 Reporter:  dcf          |          Owner:  tbb-team
     Type:  task         |         Status:  new
 Priority:  normal       |      Milestone:
Component:  Tor Browser  |        Version:
 Keywords:  meek         |  Actual Points:
Parent ID:               |         Points:
  Sponsor:               |
-------------------------+--------------------------
 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?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/17330>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs