Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 833
    • Issues 833
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 34
    • Merge requests 34
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #3419

Closed
Open
Created Jun 17, 2011 by Nick Mathewson@nickm🏃Owner

Revert or repair bug2355 changes

Apparently the changed semantics for UseBridges in Tor 0.2.2.28-beta caused some problems for Vidalia. The default "UseBridges auto" threw some people into bridge mode who didn't expect to be in bridge mode, and the new behavior of "UseBridges 1" with no bridges set made people's tors stop working without a clear explanation of why. See bug legacy/trac#3354 (closed) for full details.

Counterproposals to reverting seem too complex to me. I've got a branch "bug 2355_revert" in my public repository to do the revert. I suggest applying it to 0.2.2.x and 0.2.3.x. Comments?

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