#24456: Figure out what to do with the guardfraction feature
------------------------------------+------------------------------------
Reporter: asn | Owner: (none)
Type: defect | Status: needs_review
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 teor):
> Also separating client guardfraction functionality from dirauth-
guardfraction functionality is not so easy, since they both use the same
funcs, but the latter also uses it for consensus making. So perhaps we can
roll with the branches I posted above for now, and build on top of them
for 034.
Sure!
I suggest we stop clients (and relays) calling those functions in 0.3.4.
We can leave the functions as authority-only.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/24456#comment:10>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online