[tor-bugs] #3049 [Tor Client]: Allow a Tor process to be ‘owned’ by a controller process

[Tor Bug Tracker & Wiki]

#3049: Allow a Tor process to be ‘owned’ by a controller process
-------------------------+--------------------------------------------------
 Reporter:  rransom      |          Owner:  rransom           
     Type:  enhancement  |         Status:  needs_review      
 Priority:  major        |      Milestone:  Tor: 0.2.2.x-final
Component:  Tor Client   |        Version:                    
 Keywords:               |         Parent:                    
   Points:               |   Actualpoints:                    
-------------------------+--------------------------------------------------

Comment(by rransom):

 Replying to [comment:11 arma]:
 > This feature reminds me of a related feature mwenge advocated for a long
 time -- letting a controller "lock" the control port with its connection,
 so nobody else gets to connect so long as it remains connected. That way
 once your controller is connected, assuming you mean to have only one
 controller, some jerk can't use a flash applet to look up your control
 password and connect.

 If a controller ‘owns’ Tor in the sense used here (i.e. Tor dies when its
 controller does), that controller can keep other processes from connecting
 to its Tor instance by sending ‘`RESETCONF ControlPort`’ to turn off the
 control-port listener, without breaking existing control connections.

 That isn't the Right Thing if Tor needs to outlive a single controller
 process, as the control listener would not reappear if the control
 connection closes -- but if your Tor process outlives its controller,
 ensuring that only one controller is connected at a time is likely to be
 either unnecessary or insufficient.

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