Skip to content
GitLab
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 328
    • Issues 328
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 31
    • Merge requests 31
  • 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
  • #1929
Closed
Open
Issue created Sep 10, 2010 by Sebastian Hahn@sebastian

It's hard to specify a really long *Nodes option

Scott Bennett was quite confused by this (see this thread for details, http://archives.seul.org/or/talk/Sep-2010/msg00023.html ).

In theory we could change the ROUTERSET config type to be one of the types that you can only append to, not replace by setting another entry later on.

I'm not sure we should change this for 0.2.2.x, first because we are in feature freeze and second because this changes behaviour that someone might rely upon (setting the option via controller for example, expecting this to overwrite, not append to the previously specified entry). For this reason I'm not sure that's a good idea at all; now with Tor warning about this kind of configuration setup we should at least confuse fewer users about thinking that they can use more than one line to specify *Nodes.

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