[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 asn):

 Replying to [comment:18 nickm]:
 > Replying to [comment:17 dcf]:
 >  [...]
 > > I guess there is a tension with #5018--ideally we want the
 `flashproxy-client` transport plugin to start without having to configure
 any false bridges. We currently use the "fake" address 0.0.1.0:1, but it's
 not for the sake of getting the transport to start up--it's because we
 don't know any real bridge addresses at startup time.
 >
 > Good point -- we'll need:
 >   * A flag to apply to a client plugin to tell Tor to launch the plugin
 whether any current bridges want it or not.

 This is also related to #5018.

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