#22310: Tor 0.3.x clients won't use Guard-flagged relays as Guards if they don't have V2Dir, throwing off consensus position weights -------------------------------------------------+------------------------- Reporter: arma | Owner: arma Type: defect | Status: | assigned Priority: Medium | Milestone: Tor: | unspecified Component: Core Tor/Tor | Version: Tor: | 0.3.0.1-alpha Severity: Normal | Resolution: Keywords: 032-unreached, 031-backport-maybe, | Actual Points: 032-backport-maybe, 033-triage-20180320, | 033-removed-20180320 | Parent ID: | Points: 0.1 Reviewer: | Sponsor: -------------------------------------------------+------------------------- Changes (by arma):
* owner: (none) => arma * status: new => assigned Comment: Replying to [comment:3 arma]: > Here's the simple patch: Ok, my {{{bug22310}}} branch implements this one-liner. > I expect that updating the specs and documentation and so on will be a bit more involved. I have pushed a {{{bug22310}}} branch to my torspec too, which adds this constraint to the definition of the Guard flag. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/22310#comment:11> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs