[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

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

#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:            
--------------------------------+-------------------------------------------
Changes (by arma):

  * priority:  minor => major


Comment:

 Because debian's tor package hups tor daily, I think this one is important
 to resolve in the 0.2.3 timeframe: it can quite reasonably bite users in a
 way they'll find impossible to track down.

 Speaking of which, is there a full list of things that Tor will
 flush/reset/etc on hup? The list has changed over the years, but if a user
 wants to predict whether this will happen, where would she look?

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/1345#comment:5>
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