Opened 6 years ago

Closed 6 years ago

#12226 closed defect (fixed)

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

Reported by: arma Owned by:
Priority: Medium Milestone: Tor: 0.2.6.x-final
Component: Core Tor/Tor Version:
Severity: Keywords: tor-client, 026-triaged-1, easy, nickm-patch
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


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?

Child Tickets

Change History (4)

comment:1 Changed 6 years ago by nickm

Keywords: tor-client 026-triaged-1 easy added

comment:2 Changed 6 years ago by nickm

Status: newneeds_review

See branch "bug12226" in my public repository.

comment:3 Changed 6 years ago by nickm

Keywords: nickm-patch added

Apply a nickm-patch keyword to tickets in needs_review in 0.2.6 where I wrote the patch, so I know which ones I can('t) review myself.

comment:4 Changed 6 years ago by arma

Resolution: fixed
Status: needs_reviewclosed

Cherry-picked onto master. Thanks!

Note: See TracTickets for help on using tickets.