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

[tor-bugs] #4685 [Pluggable transport]: Design and implement further pluggable transport extensions



#4685: Design and implement further pluggable transport extensions
---------------------------------+------------------------------------------
 Reporter:  karsten              |          Owner:  asn                      
     Type:  project              |         Status:  new                      
 Priority:  normal               |      Milestone:  Sponsor F: March 15, 2012
Component:  Pluggable transport  |        Version:                           
 Keywords:                       |         Parent:                           
   Points:                       |   Actualpoints:                           
---------------------------------+------------------------------------------
 [wiki:org/sponsors/SponsorF/Year1 Sponsor F deliverable 4] is about
 designing and implementing further pluggable transport extensions.  The
 original deliverable text is: "further extensions as needed from the Tor
 perspective for pluggable transport (proposal 180) support."

 Quoting Roger here for more background: "Basically, we should make sure
 Tor is ready for whatever people are going to try to do with pluggable
 transports.  Make Tor implement the pluggable transport spec, and make
 sure the spec is what we thought it should be.  And guess what people will
 want it to be in the future so we're ready for that.  And if somebody
 tries to use it for some of that future stuff, make it work for that."

 Note that there's an overlap between this deliverable and the
 [wiki:org/sponsors/SponsorG#Phase3:June302012 sponsor G milestone in June
 2012] where we promised to finish the coding on Tor, obfsproxy, BridgeDB
 et al. to make pluggable transports work with obfs2 as proof-of-concept
 transport.  The current plan is to finish the Tor coding until March 15,
 2012 for this deliverable and the coding on obfsproxy and BridgeDB until
 June 30, 2012 for the sponsor G deliverable (#4566, #4567, #4568).

 This ticket gets auto-assigned to George.  Not sure if Nick should lead
 this deliverable, because George already leads all the other pluggable
 transport deliverables for sponsor G.

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