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

["Tor Bug Tracker & Wiki" <torproject-admin@xxxxxxxxxxxxxx>]

#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):

 Replying to [comment:56 arma]:
 > {{{
 > +    /* XXXX022-1090 Should we also allow foo.bar.exit if ExitNodes is
 set and
 > +       Bar is not listed in it?  I say yes, but our revised manpage
 branch
 > +       implies no. */
 > }}}
 >
 > I say yes as well.
 >
 > (Though it's a pretty small point because we're trying to phase .exit
 > out in general.)

 Actually, .exit is still used for TrackExitHosts and MapAddress.  For
 MapAddress, I'm fine with saying that it overrides ExitNodes.  For
 TrackExitHosts, we *do* want to drop tracked hosts if they become
 excluded. addressmap_clear_excluded_trackexithosts is supposed to solve
 that problem.

 In any case, I believe that this behavior isn't what's on the (revised)
 manpage, and I'm not sure where to put it.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/1090#comment:61>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs