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 317
    • Issues 317
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 36
    • Merge requests 36
  • 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
  • #24128
Closed
Open
Created Nov 02, 2017 by Taylor Yu@catalyst

GETCONF doesn't resolve "auto" settings

Right now tor doesn't resolve auto settings when reporting them via GETCONF. This means the controller might need to know beforehand how tor will behave for any given auto setting, which might change across tor versions or even across consensuses. We should have a way to resolve auto settings so controllers can discover what setting tor will actually use.

Implementing this could be a lot of work because I think the behavior of many auto values gets determined by code in the relevant subsystem rather than in a centralized place like control.c.

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