10-03-2007, 04:17 AM
|
| Junior Member | | Join Date: Sep 2009
Posts: 0
| |
 Re: PuTTY and ProxyCommand
Iulius wrote:
> I have a problem with PuTTY 0.59 and the use of the new implemented
> local proxying.
(If you do get this working, be warned that you may find unexpected
crashing unless you upgrade to a development snapshot.)
> Host pc2
> ProxyCommand ssh user@pc1 tcpconnect pc2 22
>
> It works well (a ssh session is created on pc2 through pc1).
>
> I believe PuTTY can now handle that, can't it?
>
> But the problem is that I don't find how to do that in the GUI
In the `Connection > Proxy' config panel, select proxy type `Local',
and enter your command in the `local proxy command' box at the
bottom of the page.
(If you could suggest improvements to the documentation which would
have enabled you to find this more easily, I'd be interested to hear
them.)
> And the documentation explains the new « -nc » feature of PLink.
> Thus I tried:
>
> plink -nc pc2:22 user@pc1
>
> I authenticate well on pc1. Then I have:
> SSH-2.0-OpenSSH_3.8.1p1 Debian-8.sarge.6
>
> And I can't do anything!
That Plink command is functionally equivalent to the command `ssh
user@pc1 tcpconnect pc2 22' you quoted above (assuming that I've
correctly understood what `tcpconnect' does from context). Using it
by itself like this, you would then need to speak the SSH protocol
by hand over the resulting connection. `plink -nc' is designed to be
used _as_ a local proxy command, so that you don't need to worry
about what programs might be installed on pc1 that do the same job
as `tcpconnect'.
--
Simon Tatham "Selfless? I'm so selfless I
don't even know who I am."
 |