[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #12614 [Pluggable transport]: Design a good way to pass transport options to child PTs

#12614: Design a good way to pass transport options to child PTs
-------------------------------------+---------------------------
     Reporter:  infinity0            |      Owner:  RushingWookie
         Type:  defect               |     Status:  new
     Priority:  normal               |  Milestone:
    Component:  Pluggable transport  |    Version:
   Resolution:                       |   Keywords:  fog
Actual Points:                       |  Parent ID:
       Points:                       |
-------------------------------------+---------------------------

Comment (by infinity0):

 With regards to whether the ordering of keywords is significant, I think
 it's more important to look at what the SOCKS protocol spec says, rather
 than what tor implements itself. I would guess it's unordered.

 If you pick a new separator, you should use it as an internal separator
 rather than an external separator - since typical SOCKS protocol parsers
 won't recognise your custom separator. For example, `fog-
 child=a&key1=val1&key2=val;fog-child=b&key1=val1&key2=val` rather than
 your (2).

 Specifying by the name instead of the index in the chain is more usable
 and readable, but watch out for things like `b64|obfs3|b64`.

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