Opened 4 years ago

Closed 2 years ago

#19364 closed task (implemented)

Implement improved guard-node design

Reported by: asn Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-guard, tor-guards-revamp
Cc: asn Actual Points:
Parent ID: #17295 Points: 6
Reviewer: Sponsor: SponsorU-can


This ticket is about revisiting the guard picking algorithm of Tor, improving it and implementing the changes in little-t-tor.

Related tickets:

Ticket #12595 is about designing a better algorithm for picking guard nodes (proposal 259).

Ticket #17262 is about simulating and verifying the correctness of the new algorithm.

Child Tickets

Change History (5)

comment:1 Changed 3 years ago by asn

Cc: asn added

comment:2 Changed 3 years ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:3 Changed 3 years ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

comment:4 Changed 3 years ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:5 Changed 2 years ago by nickm

Resolution: implemented
Status: newclosed

This was prop 271, implemented in 0.3.0.x

Note: See TracTickets for help on using tickets.