[tor-bugs] #4865 [Tor Bridge]: managed obfsproxy cannot talk to tor on other than 127.0.0.1

[Tor Bug Tracker & Wiki]

#4865: managed obfsproxy cannot talk to tor on other than 127.0.0.1
------------------------+---------------------------------------------------
 Reporter:  wwaites     |          Owner:  asn               
     Type:  defect      |         Status:  new               
 Priority:  normal      |      Milestone:  Tor: 0.2.3.x-final
Component:  Tor Bridge  |        Version:                    
 Keywords:              |         Parent:                    
   Points:              |   Actualpoints:                    
------------------------+---------------------------------------------------
Changes (by nickm):

  * component:  Pluggable transport => Tor Bridge
  * milestone:  => Tor: 0.2.3.x-final


Comment:

 Yeah; we want to have it bind to the actual address we're listening on,
 not to the content of a string from the configuration file.  With proposal
 186, these strings can get pretty complex.  Also, we can wind up
 autodetecting an address based on an instruction to use a given port, or
 picking a port based on getting "orport auto" or such.

 router_get_advertised_or_port is a step in the right direction, but this
 needs to actually hook into our logic for figuring out what our address
 is.

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