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

Re: [tor-bugs] #7153 [Pluggable transport]: Don't require pluggable transport proxies to be SOCKS proxies

#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:14 dcf]:
 > Notice you don't configure any bridges (because none exist yet).
 >  2. The transport plugin does its rendezvous and waits.
 >  3. Tor ''doesn't'' make a SOCKS connection because it knows of no
 bridges yet.

 Oh oh oh! This reminds me of a third data point we have, for a pluggable
 transport that doesn't work well with our current approach: Skypemorph.

 See ticket #5483: the Skypemorph people want exactly this feature too.
 They're thinking of working around it by starting Tor with DisableNetwork
 set to 1, and then when their Skypemorph transport is done bootstrapping,
 they set DisableNetwork back to 0. That sure is a hack though, since the
 pluggable transport isn't meant to have to be a Tor controller too.

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