[tor-bugs] #10671 [Pluggable transport]: Pluggable Transports: Improve method of transferring parameters to client-side transports

Tor Bug Tracker & Wiki blackhole at torproject.org
Wed Jan 29 14:45:00 UTC 2014


#10671: Pluggable Transports: Improve method of transferring parameters to client-
side transports
-------------------------------------+--------------------
     Reporter:  asn                  |      Owner:  asn
         Type:  enhancement          |     Status:  new
     Priority:  normal               |  Milestone:
    Component:  Pluggable transport  |    Version:
   Resolution:                       |   Keywords:
Actual Points:                       |  Parent ID:  #10629
       Points:                       |
-------------------------------------+--------------------

Comment (by asn):

 I like your approach Yawning. We will also need to define what happens if
 Tor wants to do the 0x80 `SOCKS PT` method but it's not sure whether the
 PT supports it. We will probably need to define a
 `TOR_PT_CMETHOD_PROXY_TYPES` environment variable like David suggested
 (and the PT will have to advertise `socks5pt` support or something). I
 guess this is not too bad but not too good either.

 I'm also thinking on whether `EXTDATA` needs to be `(NR_EXTDATA, KLEN,
 KEY, VLEN, VAL, ...)`. To be honest, I think it's fine as it is (opaque
 towards the extra data).

 David I also like your idea about SOCKSv4a. I think I slightly prefer the
 SOCKS5PT avenue because it seems a bit less hacky (we don't use SOCKSv4a
 in unspecified ways) and we also don't clog the SOCKS username/password
 method (which ''might'' be useful in the future). I think the
 implementation effort is pretty much the same for both approaches. It's
 also worth noting that SOCKS5 supports domain names on the CONNECT method.

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


More information about the tor-bugs mailing list