Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #17330

Closed (moved)
Open
Opened Oct 13, 2015 by David Fifield@dcf

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

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?

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#17330