[tor-bugs] #3594 [Tor Bridge]: Add support for SOCKS parameters in Bridge and {Client, Server}TransportPlugin lines

[Tor Bug Tracker & Wiki]

#3594: Add support for SOCKS parameters in Bridge and
{Client,Server}TransportPlugin lines
------------------------+---------------------------------------------------
 Reporter:  asn         |          Owner:                    
     Type:  defect      |         Status:  new               
 Priority:  normal      |      Milestone:  Tor: 0.2.4.x-final
Component:  Tor Bridge  |        Version:                    
 Keywords:              |         Parent:  #3591             
   Points:              |   Actualpoints:                    
------------------------+---------------------------------------------------

Comment(by asn):

 Grr! I'm not sure if the "passing arguments to transports through SOCKS"
 idea can work.

 Using the shared secret option of obfs2 as an example:
 """
 Bridge obfs2 192.0.2.4:5555 shared_secret=test
 ClientTransportPlugin obfs2 exec ./obfsproxy --managed
 """

 In this case, tor will pass the "shared_secret=test" argument to
 obfsproxy in its first SOCKS connection to it. This is way after the
 initialization of obfs2 (and its crypto and its shared-secret).
 The same problem occurs for any argument that must be passed to a
 transport at initialization time.

 Furthermore, server proxies don't use the SOCKS protocol, so there is
 no way to pass arguments to managed server proxies.

 Unfortunately, every solution I can think of, is stupidly dirty. All
 of those solutions involve passing the arguments to the proxy using an
 environment variable, and they all become very messy when I start
 thinking of their implementation or usability.

 I'm considering leaving this to be discussed during the dev. meeting,
 if I don't get any better thoughts. Of course, any ideas are welcome :)

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