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

Re: [tor-bugs] #4568 [BridgeDB]: Extend BridgeDB to give out pluggable transport information

#4568: Extend BridgeDB to give out pluggable transport information
----------------------+-----------------------------------------------------
 Reporter:  karsten   |          Owner:  aagbsn                  
     Type:  project   |         Status:  accepted                
 Priority:  normal    |      Milestone:  Sponsor G: June 30, 2012
Component:  BridgeDB  |        Version:                          
 Keywords:            |         Parent:                          
   Points:            |   Actualpoints:                          
----------------------+-----------------------------------------------------
Changes (by aagbsn):

 * cc: asn (added)


Comment:

 Replying to [comment:4 asn]:
 > Replying to [comment:2 aagbsn]:
 > > I want to do this.
 >
 > Cool! If you need any help, feel free to ask.

 Is this the right spec for the extra-info lines:

 {{{
 Advertising bridge methods

   Bridges put the 'method' lines in their extra-info documents.

      method SP <methodname> 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.

   If the SMETHOD line includes a DECLARE: part, the router descriptor gets
   a new line:

      method-info SP <methodname> [SP arglist] NL
 }}}
 from torspec.git/proposal/180-pluggable-transport.txt
 (93d89226e73cb535088d4cb4104afefdbdfe83c0)

 So, should BridgeDB parse the extra-infos directly? If the Bridge
 Authority does reachability tests for some or all pluggable-transports,
 how will this be indicated to BridgeDB?

 {{{
 Bridge authority behavior

   We need to specify a way to test different transport methods that
   bridges claim to support.  We should test as many as possible.  We
   should NOT require that we have a way to test every possible
   transport method before we allow its use: the point of this design
   is to remove bottlenecks in transport deployment.
 }}}

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