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

Re: [tor-bugs] #9013 [BridgeDB]: BridgeDB should pass pluggable transport shared-secrets to clients

#9013: BridgeDB should pass pluggable transport shared-secrets to clients
----------------------+-----------------------------------------------------
 Reporter:  asn       |          Owner:  isis             
     Type:  defect    |         Status:  needs_information
 Priority:  major     |      Milestone:                   
Component:  BridgeDB  |        Version:                   
 Keywords:  pt        |         Parent:                   
   Points:            |   Actualpoints:                   
----------------------+-----------------------------------------------------

Comment(by sysrqb):

 Replying to [comment:4 asn]:
 > The idea was that the elements of the arglist are space-separated as in:
 > {{{
 > transport obfs3 11.22.33.44:443 shared-secret=asedqwe secondarg=lol
 > }}}
 >
 > The spec is indeed unclear and should be fixed.
 Yup, I think the spec if contradictory. It presents the examples (as in my
 last comment) with a space-separated arglist but then it defines the
 options, afaict, as comma-separated.

 The spec defines
 [https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/180
 -pluggable-transport.txt#l457 [2]] the arglist as:
 {{{
 Bridges put the 'method' lines in their extra-info documents.
      transport SP <transportname> SP <address:port> [SP arglist] NL

   The address:port are as returned from an SMETHOD line (unless they are
   replaced by the FORWARD: directive).  The arglist is a K=V,... list as
   returned in the ARGS: part of the SMETHOD line's Options component.
 }}}

 Where ARGS: is
 {{{
       - ARGS:K=V,K=V,K=V

         If this option is set, the K=V arguments are added to Tor's
         extrainfo document.
 }}}

 and that leads me to think extra-info documents present args as comma-
 separated. dir-spec does not specify the format of arglist, either. Did I
 misinterpret something? If not, then you prefer to change the spec? (I'm
 not opposed to this, just looking for clarity).

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