Opened 6 months ago

Last modified 45 hours ago

#20822 assigned project

Follow-up tasks for prop271 (new guard API) implementation

Reported by: nickm Owned by: nickm
Priority: Medium Milestone: Tor: 0.3.2.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-guard, triaged-out-20170124, TorCoreTeam201705
Cc: isis, catalyst Actual Points:
Parent ID: Points: parent
Reviewer: Sponsor:


This is a parent ticket to capture follow-up tasks that we (might) want to do in order to improve QOI, usability, security, etc, for our new guard algorithm.

Child Tickets

#20718Prop271 -- Resolve all 'XXXX prop271' itemsnickm
#20719prop271 -- make parameters configurablenickm
#20823[controller, prop271] GETINFO support for new guard selection logicnickm
#20824[prop271, controller] DROPGUARDS support for new guard backendnickm
#20825User-named guard selections
#20826Restrict GUARDS set to EntryNodes when the set of guards is restrictivenickm
#20827Record guards' ed25519 identities
#20828Should we provide a migration method from the old guard logic to the new one?
#20830Remove legacy guard algorithm codenickm
#20831Support existing guard torrc options better with new guard code, or deprecate them.nickm
#20832Design proposals to further improve guard securitynickm
#20835Refactor choose_good_entry_server so it is (almost) never usednickm
#20919Extract prop271 state-parsing code into a generic thing
#20921Refactor global_origin_circuit_list code into separate functions.nickm
#20931[prop271] Generate GUARD controller eventsnickm
#20950Design guard algorithm tweaks to be more tolerant when picking directory guard.
#20974Call no directory guard happy until its directory headers are receivednickm
#21006Reduce NumDirectoryGuards to 1
#21039Refactor and simplify guard code of circuit_send_next_onion_skin()asn
#21052Bad prop271 behavior when exhausting all guardsasn
#21421Maybe check for GUARD_WAIT circuit readiness whenever a guard fails
#21422Possibly, learn more network data from GUARD_USABLE_NEVER circuits?
#21423Refactor choose_good_entry_server based on different usecases
#21424Treat directory guard success only as a partial success for the guard?
#21425entry_list_is_constrained() should look at the guard_selection_t object

Change History (9)

comment:1 Changed 6 months ago by dgoulet

  • Keywords tor-guard added

comment:2 Changed 5 months ago by nickm

  • Owner set to nickm
  • Status changed from new to assigned

comment:3 Changed 5 months ago by nickm

  • Points set to parent

comment:4 Changed 4 months ago by nickm

  • Keywords triaged-out-20170124 added
  • Milestone changed from Tor: 0.3.0.x-final to Tor: 0.3.1.x-final

comment:5 Changed 4 weeks ago by nickm

  • Keywords 031-reach added

comment:6 Changed 2 weeks ago by nickm

  • Keywords TorCoreTeam201705 added
  • Milestone changed from Tor: 0.3.1.x-final to Tor: 0.3.2.x-final

These are things I should work on during May, but they're prep work for 0.3.2 and beyond.

comment:7 Changed 2 weeks ago by isis

  • Cc isis added

comment:8 Changed 2 weeks ago by catalyst

  • Cc catalyst added

comment:9 Changed 45 hours ago by nickm

  • Keywords 031-reach removed
Note: See TracTickets for help on using tickets.