Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 313
    • Issues 313
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 34
    • Merge requests 34
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #31189
Closed
Open
Created Jul 17, 2019 by cypherpunks@cypherpunks

potential docs update needed for GuardLifetime?

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 385602e9 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?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking