[tor-bugs] #7153 [Pluggable transport]: Don't require pluggable transport proxies to be SOCKS proxies
Tor Bug Tracker & Wiki
blackhole at torproject.org
Tue Jan 8 17:42:01 UTC 2013
#7153: Don't require pluggable transport proxies to be SOCKS proxies
---------------------------------+------------------------------------------
Reporter: karsten | Owner: asn
Type: project | Status: new
Priority: normal | Milestone:
Component: Pluggable transport | Version:
Keywords: SponsorF20130228 | Parent:
Points: | Actualpoints:
---------------------------------+------------------------------------------
Comment(by arma):
Replying to [comment:7 zwol]:
> The "DEFIANCE" architecture that was presented at FOCI last summer
contemplates packaging up pluggable-transport configurations as "network
entry tickets" and delivering them to clients in a semi-automated manner.
So there would be a controller process that would receive basically the
above configuration blob from the network. In the current pluggable
transport design, it would have to be parsed, repackaged as a bridge
descriptor in Tor's dynamic configuration, and then repackaged again to
hand off to the transport plugin. Feeding it directly to the pluggable
transport instead (as a file in the filesystem, presumably) saves two
data-reformatting operations. Furthermore, it means !StegoTorus only
needs one configuration parser, and the "ACS dance" client needs none at
all.
See also
https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/199
-bridgefinder-integration.txt for Tor's view of how such a thing might
work. It does seem like as our pluggable transports get fancier, the
notion that the primary data needed by the pluggable transport receiver is
"IPv4 address and port" is going to get farther from the truth.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/7153#comment:8>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list