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

Closed (moved)
Open
Opened Nov 17, 2015 by Roger Dingledine@arma

Document the files in $datadir/keys, maybe in the man page?

Nick and I were just pondering the legacy v3 signing key feature. I told him to go to the man page and look for the word 'legacy'. Then I actually did it: I found "V3AuthUseLegacyKey", but no further instructions on how to use it.

I assume the next step is for people who want to use it to go to src/or/config.c and track down other words that include the substring "egacy".

Is there some better place to look? Should the man page list at least the possible filenames in $datadir/keys/ ?

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