Re: [tor-bugs] #7822 [Pluggable transport]: Create an ezpt pluggable transports wrapper

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#7822: Create an ezpt pluggable transports wrapper
-------------------------------------+--------------------------
     Reporter:  dcf                  |      Owner:  asn
         Type:  project              |     Status:  needs_review
     Priority:  normal               |  Milestone:
    Component:  Pluggable transport  |    Version:
   Resolution:                       |   Keywords:  easy
Actual Points:                       |  Parent ID:
       Points:                       |
-------------------------------------+--------------------------

Comment (by dcf):

 Replying to [comment:8 infinity0]:
 > It was just more convenient to do so - we only had to create one single
 ~~class~~__file__ (well and some minor refactoring tweaks) rather than re-
 implement the whole SOCKS-ExtORPort handling and reactor/circuit setup
 stuff.
 >
 > Do you see a major advantage having a separate ezpt proxy? We could
 certainly do it, but it would take a bit more effort.

 Making it an obfsproxy module seems to be raising some design questions
 with awkward answers. An ezpt.spec file, for example, is quite different
 from the design in the ticket description (as I envisioned it, anyway),
 and so far the patch has a surprising lot of changes to obfsproxy itself.
 As it is, it's more "here's an easy way to create an obfsproxy module"
 than "here's an easy way to create a new pluggable transport." I'm not
 saying that's a bad thing, and it may actually be more useful in the long
 run.

 The need for SOCKS and ExtORPort support is a pretty important
 consideration. We should try to make those things part of pyptlib. I
 remember George and I talked about it--it wasn't so easy to do because you
 can't assume that programs will be using Twisted.

 Or maybe we should just recommend building on obfsproxy in general for
 Python pluggable transports? Use obfsproxy as the basic library, rather
 than pyptlib? It's what everyone will do anyway, because it's the easiest.
 It worked for ScrambleSuit; maybe it's a good idea in general?

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