Wences wrote:
> Hi,
>
> if you can get this to work:
> > >
> > > ssh solaris "command to figure out what port you want"
> > > ssh -L5900:localhost:thatport solaris
> > >
> then perhaps you could prepare a file like this, and give it
> execution permissions:
>
> ------------------------------------------------------------
> #!/bin/bash
> port=$( ssh solaris "command to print out the port number (and nothing
> else)" )
> ssh -L 5900:localhost:$port solaris
> ------------------------------------------------------------
>
> This would require the user to login twice with his shell user and
> pass, and then with his VNC pass, but with a bit more of work you might
> turn it into a script that asks for the user and pass and uses them
> twice.

It is not a great solution, but so far this is one of my only options.

I am considering using vncconnect instead and simply let the vncserver
connect to a listening vncviewer. This can be accomplished using only 1
login (which can be ssh or whatever). Downside is that the traffic is
unencrypted but the vncpassword is not required (and hence not
transmitted) so the danger may not be so great.

Or if I could find a vncviewer that supported socks proxy I could
simply use the socks proxy feature of the ssh client to create the
tunnels dynamically. Tightvnc however does not support socks proxy. I
am considering using SocksCap32 but that requires the user to install
additional software.

Maybe putty is easier to work with... I'll have to check.