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 325
    • Issues 325
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 30
    • Merge requests 30
  • 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
  • #12226
Closed
Open
Issue created Jun 08, 2014 by Roger Dingledine@armaReporter

Make Strict{Entry,Exit}Nodes obsolete, rather than synonym for StrictNodes?

Right now if you type "StrictExitNodes 1" you quietly get the behavior that a) this line is ignored for your ExitNodes selection, but b) if you set ExcludeNodes then it interprets it fanatically.

Since StrictExitNodes and StrictEntryNodes have been non-functional in this way for a while, should we make them OBSOLETE() rather than a synonym for a different (albeit similar sounding) config option?

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