[tor-bugs] #8929 [Tor]: Pass server-side pluggable transport parameters to proxies

[Tor Bug Tracker & Wiki]

#8929: Pass server-side pluggable transport parameters to proxies
---------------------------+------------------------------------------------
 Reporter:  asn            |          Owner:     
     Type:  task           |         Status:  new
 Priority:  normal         |      Milestone:     
Component:  Tor            |        Version:     
 Keywords:  tor-bridge pt  |         Parent:     
   Points:                 |   Actualpoints:     
---------------------------+------------------------------------------------

Comment(by asn):

 Assuming that we use environment variables to do the parameter passing on
 the server-side, it's annoying that we can't use the same encoding as the
 one we are using for SOCKS parameters on the client-side.

 Specifically, on the client-side SOCKS parameters look like:
 `shared-secret=blabla;ticket-file=/ticket.file`

 while on the server-side, the names of the pluggable transports must be
 specified, which makes the encoding look like:
 `obfs2:shared-secret=blabla;obfs2:ticket-file=/ticket.file;scramblesuit
 :shared-secret=hoho`

 On the client-side we have to escape semicolons and backslashes, but on
 the server side we have to escape colons, semicolons and backslashes.
 (Actually now that I look at it, we also have to escape the equal signs on
 both cases.)

 Nick, any opinions on the encoding?

 (We could also use environment variables like `TOR_PT_PARAMETERS_OBFS2
 =shared-secret=blabla;ticket-file=/ticket.file` so that we use the same
 encoding, but playing with environment variable names seems a bit silly.)

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