[tor-bugs] #2264 [Tor bundles/installation]: Dynamically choose available Tor ports in Tor Browser Bundle

[Tor Bug Tracker & Wiki]

#2264: Dynamically choose available Tor ports in Tor Browser Bundle
--------------------------------------+-------------------------------------
 Reporter:  Sebastian                 |          Owner:  erinn
     Type:  defect                    |         Status:  new  
 Priority:  normal                    |      Milestone:       
Component:  Tor bundles/installation  |        Version:       
 Keywords:                            |         Parent:  #2880
   Points:                            |   Actualpoints:       
--------------------------------------+-------------------------------------

Comment(by mikeperry):

 Replying to [comment:8 arma]:
 > Tor could dynamically choose one, e.g. 'socksport auto'. It would poke
 around until it finds something it can bind.
 >
 > Same with controlport, I guess.
 >
 > The trick then would be: how do we tell the caller which port we picked?
 Can't use the controlport, clearly. Parsing logs on stdout is an option,
 but kind of klunky.
 >
 > And then the question becomes: who does that parsing? Vidalia comes to
 mind, since it will want to know the answer anyway in order to tell
 Firefox (and thus Torbutton) when it launches them, and in order to
 display them in the GUI.

 I think we should just run with this. Shall I create two child tickets,
 one for Tor (SocksPort Auto) and one for Vidalia to parse the logs?

 Otherwise we'll block forever on the perfect solution that just isn't
 going to happen, like a named pipe control port interface...

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