[tor-bugs] #1345 [Tor Client]: Exits tracked with TrackHostExits reset on hup

[Tor Bug Tracker & Wiki]

#1345: Exits tracked with TrackHostExits reset on hup
--------------------------------+-------------------------------------------
 Reporter:  Sebastian           |         Type:  defect    
   Status:  new                 |     Priority:  minor     
Milestone:  Tor: 0.2.3.x-final  |    Component:  Tor Client
  Version:  0.2.1.25            |   Resolution:  None      
 Keywords:  easy                |       Parent:            
--------------------------------+-------------------------------------------
Changes (by nickm):

  * keywords:  => easy
  * milestone:  => Tor: 0.2.3.x-final


Old description:

> Using TrackHostExits with a long TrackHostExitsExpire should mean
> Exits are only rotated if they go down. I don't see a reason why
> we should forget the trackings we set up earlier when we got a hup
> and the TrackingHostExits* options didn't change, especially because
> some Tor packages like the debian package hup tor frequently.
>
> [Automatically added by flyspray2trac: Operating System: All]

New description:

 Using TrackHostExits with a long TrackHostExitsExpire should mean
 Exits are only rotated if they go down. I don't see a reason why
 we should forget the trackings we set up earlier when we got a hup
 and the TrackingHostExits* options didn't change, especially because
 some Tor packages like the debian package hup tor frequently.

 [Automatically added by flyspray2trac: Operating System: All]

--

Comment:

 This should be fairly easy for anybody who reads C and can track the
 control flow for the SIGNAL command from handle_control_signal() down
 through signal_callback() to do_hup().

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