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
  • #21108

Closed (moved)
Open
Opened Dec 29, 2016 by Roger Dingledine@arma

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

While debugging #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
Tor: 0.2.9.x-final
Milestone
Tor: 0.2.9.x-final
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#21108