On Mon, Dec 10, 2012 at 01:02:39AM -0500, Nick Mathewson wrote: > > And last question, is there a reason that a line like > > ClientTransportPlugin obfs2 exec /usr/bin/obfsproxy --managed > > causes Tor to always run an obfsproxy daemon, even if there are no obfs2 > > bridges defined in torrc? > > Interesting; I'm not sure that's how it should work at all. George, > any ideas about this one?
I believe the answer is "because the code can't yet handle the concept of having a bridge configured for a given pluggable transport yet not having that transport ready for use". See also https://trac.torproject.org/projects/tor/ticket/5018 It would be great to get this fixed, so we can include various pluggable transports in the default client bundles. --Roger _______________________________________________ tor-talk mailing list tor-talk@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
