[tor-bugs] #3725 [Tor]: Implement the wildcard "*" protocol in {Client, Server}TransportPlugin lines

[Tor Bug Tracker & Wiki]

#3725: Implement the wildcard "*" protocol in {Client,Server}TransportPlugin lines
------------------------+---------------------------------------------------
 Reporter:  asn         |          Owner:                    
     Type:  defect      |         Status:  new               
 Priority:  normal      |      Milestone:  Tor: 0.2.5.x-final
Component:  Tor         |        Version:                    
 Keywords:  tor-client  |         Parent:  #3591             
   Points:              |   Actualpoints:                    
------------------------+---------------------------------------------------

Comment(by asn):

 This problem seems solvable, even though all the solutions I've
 thought of are messy. Example of such a silly solution:

 When Tor uses the wildcard transport in `TOR_SERVER_TRANSPORTS`, it also
 places all the bindaddrs for all the transport it knows (from its
 state file) to its `TOR_PT_SERVER_BINDADDR` environment variable. When the
 transport proxy supports a transport that is also mentioned in the
 `_BINDADDR` variable, it knows in which port to bind.

 For example, if a transport proxy supports the pluggable transports
 "one" and "two", and Tor in its state file has saved bindaddrs for the
 transports "two", "sixteen" and "thirty", it will create the following
 env vars:

 {{{
 TOR_PT_SERVER_TRANSPORTS="*"
 TOR_PT_SERVER_BINDADDR="two-0.0.0.0:1444;sixteen-0.0.0.0:1201;thirty-0.0.0.0:1001
 }}}
 and the transport proxy will try to bind "two" to "0.0.0.0:1444" and
 "one" to whichever port it wants.

 In any case, I'll try to think of a better solution to this problem, since
 the above is kinda lame.

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