Opened 8 months ago

Last modified 2 months ago

#32810 new defect

Move timing-related authority options into dirauth module

Reported by: nickm Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: 043-deferred, 044-deferred
Cc: nickm Actual Points:
Parent ID: #32139 Points:
Reviewer: Sponsor:

Description

We should concentrate all of the options related to vote timing into the dirauth module.

Some of these will turn out to belong in voting_schedule.c: we'll need to be careful.

The ones I know of are:

  • TestingV3AuthInitialDistDelay
  • TestingV3AuthInitialVoteDelay
  • TestingV3AuthInitialVotingInterval
  • TestingV3AuthVotingStartOffset
  • V3AuthDistDelay
  • V3AuthNIntervalsValid
  • V3AuthVoteDelay
  • V3AuthVotingInterval



Child Tickets

TicketStatusOwnerSummaryComponent
#33436closednickmRemove all non-dirauth usage of dirauth timing options.Core Tor/Tor

Change History (4)

comment:1 Changed 8 months ago by nickm

Parent ID: #32806#32139

comment:2 Changed 7 months ago by nickm

Keywords: 043-deferred added

All 0.4.3.x tickets without 043-must, 043-should, or 043-can are about to be deferred.

comment:3 Changed 7 months ago by nickm

Milestone: Tor: 0.4.3.x-finalTor: 0.4.4.x-final

comment:4 Changed 2 months ago by nickm

Keywords: 044-deferred added
Milestone: Tor: 0.4.4.x-finalTor: unspecified

Bulk-remove tickets from 0.4.4. Add the 044-deferred label to them.

Note: See TracTickets for help on using tickets.