Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #12226

Closed (moved)
(moved)
Open
Created Jun 08, 2014 by Roger Dingledine@arma

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