Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #8645
Closed (moved) (moved)
Open
Created Apr 05, 2013 by David Fifield@dcf

Pluggable transports bundles warn of need to upgrade when no new version is yet available

Say there is a TBB and corresponding PT bundle both with version number X.Y.Z-alpha-1. https://check.torproject.org/RecommendedTBBVersions will say:

[
/* ... stable bundles ... */
"X.Y.Z-alpha-1-MacOS",
"X.Y.Z-alpha-1-Windows",
"X.Y.Z-alpha-1-Linux"
]

When the X.Y.Z-alpha-2 TBB is released, the file changes to

[
/* ... stable bundles ... */
"X.Y.Z-alpha-2-MacOS",
"X.Y.Z-alpha-2-Windows",
"X.Y.Z-alpha-2-Linux"
]

If we haven't built new corresponding PT bundles yet, those will still have the old version number X.Y.Z-alpha-1, and users will get a blinking Tor button telling them to upgrade. However no upgrade exists for them yet.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking