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

Re: [tor-bugs] #3589 [Tor Bridge]: Advertise bridge pluggable transports using extra-info lines



#3589: Advertise bridge pluggable transports using extra-info lines
------------------------+---------------------------------------------------
 Reporter:  asn         |          Owner:                    
     Type:  defect      |         Status:  new               
 Priority:  normal      |      Milestone:  Tor: 0.2.3.x-final
Component:  Tor Bridge  |        Version:                    
 Keywords:              |         Parent:  #3591             
   Points:              |   Actualpoints:                    
------------------------+---------------------------------------------------
Changes (by karsten):

 * cc: aagbsn (added)


Comment:

 So, I talked to Aaron about this a few days ago.  He thinks it doesn't
 really matter where bridges include this information, though extra-info
 descriptors would require slightly more work.

 Here's another reason why it might make more sense to add pluggable
 transports information to server descriptors.  Clients download server
 descriptors from bridges, but not their extra-info descriptors.  Clients
 could learn about other transports of a bridge and store that information
 in their state file.  And if one of their transports gets blocked they
 might try another transport.  Most of this is probably not supported right
 now, but putting the information in the right descriptors might facilitate
 such a design in the future.

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