tor complains there's no ClientTransportPlugin line when actually it just can't launch the exe
When I set my torrc to say
ClientTransportPlugin obfs2 exec /path/to/nonexistent/file --managedthen the way Tor tells me it couldn't launch or find the file is by logging
Feb 10 03:23:28.000 [warn] Could not launch managed proxy executable!
Feb 10 03:23:28.000 [warn] You have a Bridge line using the obfs2 pluggable transport, but there doesn't seem to be a corresponding ClientTransportPlugin line.That second line is confusing people. It's not true.
If I then change the line to
ClientTransportPlugin obfs2 exec /bin/false --managedI get
Feb 10 03:29:57.000 [notice] Managed proxy stream closed. Most probably application stopped running
Feb 10 03:29:57.000 [notice] Failed to terminate process with PID '13672'
Feb 10 03:29:57.000 [warn] You have a Bridge line using the obfs2 pluggable transport, but there doesn't seem to be a corresponding ClientTransportPlugin line.
Feb 10 03:29:58.000 [notice] Bootstrapped 5%: Connecting to directory server.
Feb 10 03:29:58.000 [warn] Tried to connect through proxy, but proxy address could not be found.Again the warn line is what people look to. Also, should the "it closed" be a warn in this case? Also also, what's with the "tried to connect through proxy" line -- why does it tell me the proxy address could not be found?
To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information