[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #24456 [Core Tor/Tor]: Figure out what to do with the guardfraction feature
#24456: Figure out what to do with the guardfraction feature
------------------------------------+------------------------------------
Reporter: asn | Owner: (none)
Type: defect | Status: needs_revision
Priority: Medium | Milestone: Tor: 0.3.3.x-final
Component: Core Tor/Tor | Version:
Severity: Normal | Resolution:
Keywords: tor-dirauth, tor-guard | Actual Points:
Parent ID: | Points: 2
Reviewer: | Sponsor:
------------------------------------+------------------------------------
Comment (by asn):
OK let's recap here.
For 033 master we need a patch that obsoletes the config options (also
removes all the config option-relevant code), and also kills the
guardfraction voting feature.
For 029 and later, we just need a patch that obsoletes the config options.
Then later in the future, when most dirauths use tor versions with
obsolete config options, we can completely kill the rest of the code
(vote/consensus guardfraction parsing, consensus voting code, client code,
etc.).
Does that make sense?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/24456#comment:6>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs