[tor-bugs] #1090 [Tor Client]: Warning about using an excluded node for exit

[Tor Bug Tracker & Wiki]

#1090: Warning about using an excluded node for exit
---------------------------+------------------------------------------------
    Reporter:  Sebastian   |       Owner:  nickm             
        Type:  defect      |      Status:  needs_review      
    Priority:  major       |   Milestone:  Tor: 0.2.2.x-final
   Component:  Tor Client  |     Version:  0.2.1.19          
  Resolution:  None        |    Keywords:                    
      Parent:              |      Points:                    
Actualpoints:              |  
---------------------------+------------------------------------------------

Comment(by nickm):

 I just convinced roger that the in the case where exit enclaves,
 restricted entries, and families collide, the solution is *not* "Ignore
 families when StrictNodes=0".  It is maaaaybe something closer to "back
 off on the exit enclave if the node in question is in the same family as
 every running bridge".  But in any case, it's a different bug.

 (More rationale: we got into this rabbit-hole by creating underspecified
 carve-outs in configuration options in order to keep running in the face
 of contradictory requirements.  We shouldn't do more of that; any carve-
 outs should be considered, specified, consistent, and disable-able.
 Further, StrictNodes only applies to *Nodes options: making it apply to
 families too in just one case would be odd and surprising.)

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/1090#comment:60>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online