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

["Tor Bug Tracker & Wiki" <torproject-admin@xxxxxxxxxxxxxx>]

#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):

 On the interface:

 I can get that we need to expose the ControlPort via a way that doesn't
 involve using the ControlPort, but is there some reason that we can't use
 a GETINFO command for the other ports?  Also, is there any reason to do
 this _only_ for socksport and controlport?

 As far as possible, I want to avoid having log messages be any part of our
 defined interface.  If we *did* do that, we'd want to make it really
 obvious which ones they are.

 On the implementation:

 It seems like "FooPort auto" ought to mean "bind the address with sin_port
 set to 0, then do a getsockname() on the socket, then advertise that one."
 That doesn't sound too hard.  We would also need to tweak anything that
 advertises a port.

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