Perhaps easier than solving bug 3161? It has drawbacks such as double authentications, double encryption.
(In reply to comment #0) > Perhaps easier than solving bug 3161? > > It has drawbacks such as double authentications, double encryption. This is true of ProxyCommand would be some kind of ssh command, but typically it is not. For example, the man page has this example: connect via an HTTP proxy at 192.0.2.0: ProxyCommand /usr/bin/nc -X connect -x 192.0.2.0:8080 %h %p It's also possible to use "connect.c", socat etc to connect to SOCKS proxies, possibly without extra authentication or encryption steps. It would be possible to add a config option for ProxyCommand to tlclient. However,there are a few drawbacks: If you have clients running on different platforms, you need to port and provide such a command on all of them (Windows, Linux, Mac etc). Also, all data will flow through the ProxyCommand, which can give a performance penalty. This can be avoided by instead using ProxyUseFdpass, but few such programs are available, and this mechanism does not work on Windows.
This is one specific solution, so closing this in favour of the more general bug 3161. *** This bug has been marked as a duplicate of bug 3161 ***
