[tor-bugs] #3076 [Tor Client]: Implement 'SocksPort auto' and 'ControlPort auto'

[Tor Bug Tracker & Wiki]

#3076: Implement 'SocksPort auto' and 'ControlPort auto'
-------------------------+--------------------------------------------------
 Reporter:  mikeperry    |          Owner:                    
     Type:  enhancement  |         Status:  new               
 Priority:  major        |      Milestone:  Tor: 0.2.2.x-final
Component:  Tor Client   |        Version:                    
 Keywords:               |         Parent:  #2264             
   Points:               |   Actualpoints:                    
-------------------------+--------------------------------------------------

Comment(by nickm):

 All but the "write the controlport to a file or the log or something" part
 is now implemented in branch "feature3076" in my public repo.  Have a
 look.

 Actually, the log _will_ currently note the actual controlport, but please
 don't use that!  Log messages are explicitly not a stable interface.

 As for the interface to expose the controlport...

 Replying to [comment:3 mikeperry]:
  [...]
 > Depends. Can we choose a predictable directory that Vidalia will be able
 to find in all cases? For TBB this is probably just $CWD, but in other
 cases it may be more complex.. Not sure if the other cases matter at all,
 though.

 It could be a filename specified on the command-line, right?  If so, is
 there any reason that finding such a file would be harder for Vidalia than
 finding the log messages would be?

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