delight forums

[wnpaul]

Since SSHTunnelClient seems to be built on PuTTY code it should not be too difficult to add the option of using an existing SOCKS proxy to make the tunnel connections.

Could this be added (it would allow me to fully switch to it), and in the meantime, is there a way to set it up manually, by means of a registry entry or config file entry?

The reason for this is a firewalled environment where I have a SOCKS proxy for SSH connections but no ports transparently open (i.e. even port 80 is closed, have to use http proxy for surfing).

Nachdem SSHTunnelClient auf PuTTY Code zu basieren scheint sollte es nicht zu schwierig sein, die Moeglichkeit eines SOCKS-Proxys fuer die Tunnels einzubauen.

Koenntet Ihr das bitte ergaenzen (dann koennte ich komplett darauf umsteigen), und gibt es vielleicht in der Zwischenzeit eine Moeglichkeit, das manuell zu konfigurieren, in der Registry oder in einem Conf-File?

Ich sitze naemlich hinter einer Firewall, wo ich einen SOCKS-Proxy fuer SSH-Verbindungen habe, aber kein einziger Port transparent offen ist (auch nicht 80, fuers Surfen muss ich ueber einen HTTP-Proxy gehen).

[Elias Zurschmiede]

Hi

Yes its based on putty's plink. If plink has this option we can implement this feature in the next version.

I have found this parameter in plink.exe:

[wnpaul]

The plink option you quote is about setting up a tunnel that acts as a SOCKS proxy, and I have no trouble setting that up,

What I am talking about is a SOCKS proxy for plink to use to make its connection in order to set up the tunnels.

Plink does not seem to have a commandline option to do this; however, the doc says that one can give the name of a PuTTY config entry instead of a hostname; I still have to test whether plink will use a proxy configured in such a config entry. If so, I can simply set up a config entry with a proxy, and then specify that inside SSHTunnelclient.

I might also talk to the author of PuTTY about putting a cmdline option into plink.

[Elias Zurschmiede]