Opened 2 months ago

Last modified 5 days ago

#31189 new defect

potential docs update needed for GuardLifetime?

Reported by: cypherpunks Owned by:
Priority: Medium Milestone: Tor: 0.4.2.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords: docs, guardlifetime, 042-should
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

The documentation for the GuardLifetime torrc option says:

If nonzero, and UseEntryGuards is set, minimum time to keep a guard before
    picking a new one. If zero, we use the GuardLifetime parameter from the
    consensus directory.  No value here may  be less than 1 month or greater
    than 5 years; out-of-range values are clamped. (Default: 0)

In commit hash 385602e9826e79dbf0d8b51abfd925e59f275708 it appears that there was a behavior change which allows guard lifetimes of 1 day or greater (grep for get_options()->GuardLifetime >= 86400). git blame indicated the docs for the GuardLifetime option haven't been touched in 6-7 years, so I think they need an update after this change.

Is the expected behavior that setting UseEntryGuards 1 and GuardLifetime 1 day will result in guards being used for no longer than one day?

Child Tickets

Change History (3)

comment:1 Changed 2 months ago by nickm

Milestone: Tor: 0.4.2.x-final

comment:2 Changed 2 months ago by nickm

Is the expected behavior that setting UseEntryGuards 1 and GuardLifetime 1 day will result in guards being used for no longer than one day?

It's a little more complicated than that, but I think that's approximately right. (See guard-spec.txt for the full details.)

comment:3 Changed 5 days ago by nickm

Keywords: 042-should added
Note: See TracTickets for help on using tickets.