[tor-bugs] #10131 [Pluggable transport]: Clarify whether "*" takes the place of an entire managed transport list

[Tor Bug Tracker & Wiki]

#10131: Clarify whether "*" takes the place of an entire managed transport list
---------------------------------+---------------------
 Reporter:  dcf                  |          Owner:  asn
     Type:  defect               |         Status:  new
 Priority:  minor                |      Milestone:
Component:  Pluggable transport  |        Version:
 Keywords:                       |  Actual Points:
Parent ID:                       |         Points:
---------------------------------+---------------------
 In this paragraph:
 {{{
 If instead of a transport method, the torrc lists "*" for a managed
 proxy, Tor uses that proxy for all transport methods that the plugin
 supports.
 }}}
 it's not clear whether something like this is allowed and whether it is
 the same as just "*":
 {{{
 ServerTransportPlugin foo,*,bar exec </path/to/binary>
 }}}

 The way I read it, "*" has the special meaning of "all transports" only
 when it appears by itself. This interpretation is supported by some
 later text:
 {{{
 A managed proxy is configured as
    ServerTransportPlugin <methods> exec </path/to/binary> [options]
 or
    ServerTransportPlugin * exec </path/to/binary> [options]
 }}}
 {{{
 "TOR_PT_CLIENT_TRANSPORTS" -- A comma-separated list of which
 methods this client should enable, or * if all methods should
 be enabled.  The proxy SHOULD ignore methods that it doesn't
 recognize.
 }}}
 {{{
 "TOR_PT_SERVER_TRANSPORTS" -- A comma-separated list of server
 methods that the proxy should support, or * if all methods
 should be enabled.
 }}}

 The attached patch clarifies the text to match the above interpretation.
 If that interpretation is wrong, then we should add a "foo,*,bar" example
 and specify what happens in that case.

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