Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #24128

Closed (moved)
Open
Opened 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 admin enable hashed storage. More information
Assignee
Assign to
Tor: 0.3.3.x-final
Milestone
Tor: 0.3.3.x-final
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#24128