#19883 closed task (implemented)

Maintain CONFIRMED_GUARDS per new guard plan

Reported by: andrea Owned by: nickm
Priority: Medium Milestone: Tor: 0.3.0.x-final
Component: Core Tor/Tor Version: Tor: unspecified
Severity: Normal Keywords: isaremoved, nickwants029, tor-guards-revamp, nickm-deferred-20161005, TorCoreTeam201611
Cc: asn Actual Points:
Parent ID: #19877 Points: 3
Reviewer: Sponsor: SponsorU-must

Description

New guard plan summarized at https://lists.torproject.org/pipermail/tor-dev/2016-July/011234.html

7) Maintain CONFIRMED_GUARDS

  • Add guard to CONFIRMED_GUARDS when circuit succeeds
  • Fill in state info for each confirmed guard (confirmed_on_date, etc.)
  • Migration from old state format to new
  • Thoughtworks unittest: test_used_guards_parse_state()

Child Tickets

Change History (7)

comment:1 Changed 22 months ago by isabela

Keywords: isaremoved added
Milestone: Tor: 0.2.9.x-finalTor: 0.2.???

comment:2 Changed 22 months ago by nickm

Keywords: nickwants029 tor-guards-revamp added

Batch modification: I believe these are all (or nearly all!) required for the successful completion of the SponorU guards task.

comment:3 Changed 22 months ago by asn

Cc: asn added

comment:4 Changed 21 months ago by isabela

Milestone: Tor: 0.2.???Tor: 0.2.9.x-final
Sponsor: SponsorUSponsorU-must

comment:5 Changed 20 months ago by nickm

Keywords: nickm-deferred-20161005 added
Milestone: Tor: 0.2.9.x-finalTor: 0.3.0.x-final

Deferring more things -- even ones I love -- to 0.3.0. Please argue if I'm wrong.

comment:6 Changed 18 months ago by nickm

Owner: set to nickm
Status: newassigned

These features are now implemented in my (much-rebased, very unstable) prop271 branch. Because #19889 is not done yet, however, they don't actually do anything yet. At least there are tests and documentation?

comment:7 Changed 18 months ago by nickm

Keywords: TorCoreTeam201611 added
Resolution: implemented
Status: assignedclosed
Note: See TracTickets for help on using tickets.