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

[Tor Bug Tracker & Wiki]

#1345: Exits tracked with TrackHostExits should not reset on hup
--------------------------------+-------------------------------------------
 Reporter:  Sebastian           |           Type:  defect    
   Status:  new                 |       Priority:  major     
Milestone:  Tor: 0.2.3.x-final  |      Component:  Tor Client
  Version:  0.2.1.25            |     Resolution:  None      
 Keywords:  easy                |         Parent:            
   Points:                      |   Actualpoints:            
--------------------------------+-------------------------------------------

Comment(by rransom):

 Replying to [comment:6 nickm]:
 > The patch is easy enough to do.  One thing to note, though: right now,
 addressmap_clear_transient() clears three things: DNS results, virtual
 address mappings, and trackexithost mappings.  Do we want to clear all of
 these on HUP?  Some?  None?

 We want to clear TrackHostExits mappings on SIGHUP ''iff'' they are for
 hosts not listed in TrackHostExits after the HUP.  More generally, we want
 to clear a TrackHostExits mapping whenever TrackHostExits changes and the
 mapped host is not in the new TrackHostExits list.

 We should clear virtual address mappings on SIGHUP iff
 AutomapHostsOnResolve is off after the HUP.

 We shouldn't clear DNS results on SIGHUP.

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