Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • BridgeDB BridgeDB
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 27
    • Issues 27
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Anti-censorship
  • BridgeDBBridgeDB
  • Issues
  • #29184
Closed
Open
Issue created Jan 27, 2019 by Roger Dingledine@armaDeveloper

Avoid giving out bridges that suffer from #28912

Bridges running 0.3.4.x before 0.3.4.10 suffer from legacy/trac#28912 (moved), where you basically can't bootstrap from them unless they have other people fetching directory information from them at the same time as you try. Same with 0.3.5.x before 0.3.5.7 I think.

Now that 0.3.4.10 is out, and 0.3.5.7 are out, hopefully bridges will upgrade. But for the ones that don't, we might be wise in bridgedb to decline to give them out.

I wonder what fraction of bridges this affects currently? I cc irl and karsten to find out.

Assignee
Assign to
Time tracking