[tor-bugs] #21816 [Core Tor/Tor]: Add support for Pluggable Transports 2.0

[Tor Bug Tracker & Wiki]

#21816: Add support for Pluggable Transports 2.0
-------------------------------------------------+-------------------------
 Reporter:  chelseakomlo                         |          Owner:
                                                 |  dasyatid1
     Type:  enhancement                          |         Status:
                                                 |  assigned
 Priority:  Medium                               |      Milestone:  Tor:
                                                 |  unspecified
Component:  Core Tor/Tor                         |        Version:  Tor:
                                                 |  unspecified
 Severity:  Normal                               |     Resolution:
 Keywords:  tor-client tor-pt tor-bridge design  |  Actual Points:
  pt2                                            |
Parent ID:                                       |         Points:
 Reviewer:                                       |        Sponsor:
-------------------------------------------------+-------------------------
Changes (by dasyatid1):

 * status:  new => assigned
 * owner:  (none) => dasyatid1
 * cc: dasyatid1 (added)


Comment:

 As I posted on tor-dev a little while ago, I've been working on a patchset
 for this as part of work I've been doing with blanu / Operator. This is
 available at Bitbucket ([https://bitbucket.org/DasyatidPrime/tor-
 rtt2017-21816.git Git], [https://bitbucket.org/DasyatidPrime/tor-
 rtt2017-21816/src Web]).

 With commit 887352263569, I've completed successful circuits through the
 "rtt2017" [https://github.com/OperatorFoundation/shapeshifter-
 dispatcher/tree/rtt2017 branch of shapeshifter-dispatcher] and
 [https://github.com/OperatorFoundation/shapeshifter-ipc/tree/rtt2017
 associated shapeshifter-ipc] using PT2 configuration protocol (there are
 changes there I still want to upstream), and through obfs4proxy using PT1,
 each acting as an obfs4 client for connecting via a bridge.

 I'd like to hear what would be necessary to merge a version of this.
 Currently on my radar: unit tests for JSON/RFC1929 encoding functions,
 'changes' documentation, possibly commit-level cleanup, possibly pushing
 on PT spec and/or Shapeshifter upstream to lock them down. I'm probably
 missing something, though. There are some other details in my
 [https://lists.torproject.org/pipermail/tor-dev/2017-August/012411.html
 original post to tor-dev].

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