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 311
    • Issues 311
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 33
    • Merge requests 33
  • 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
  • #21108
Closed
Open
Created Dec 29, 2016 by Roger Dingledine@armaReporter

Dir auths should vote BadExit even if they don't vote Running

While debugging legacy/trac#21107 (moved), I found that moria1 decided that the atlassky relay was not Running -- and as a result, it voted only the V2Dir flag for it, even though it thinks it's a BadExit.

Since BadExit is based on a threshold of badexit-voting authorities, I think that means moria1 is effectively voting against the badexit flag for this relay, right?

It seems that wherever we decide to withhold most of the flags for relays that we don't think are running, we should stop withholding this one.

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