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
  • #31081

Closed (moved)
Open
Opened Jul 04, 2019 by Taylor Yu@catalyst

GETCONF allows zero arguments, contrary to spec

control-spec.txt says GETCONF takes at least one argument. Tor currently allows there to be zero arguments for GETCONF. If there are zero arguments, it replies with 250 OK. A reply with a keyword and no = can mean that a configuration variable has its default value. We've therefore committed to having no configuration variables named OK. I suppose that's OK.

Probably the easiest thing to do is to document the existing behavior.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
Tor: 0.4.3.x-final
Milestone
Tor: 0.4.3.x-final
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#31081