Bug#557718: vinagre ssh doesn't allow you to specify the remote username
> for ssh connections, vinagre assumes that the username you want to log
> in with on the remote machine is the same as your current username on
> the local machine, and doesn't appear to offer any way of changing or
> over-riding that.
Good point. I'd also like to see Vinagre support the option of going via
an ssh gateway like xvnc4viewer and xtightvncviewer's -via option do.
Indeed, the idea of SSH *or* VNC is broken- the machine you SSH to
is not necessarily the one you are connecting to. For convenience, I'll
quote the relevant bit of the manpage here:
Automatically create encrypted TCP tunnel to the
gateway machine before connection, connect to the host through that
cific). By default, this option invokes SSH local port
forwarding, assuming that SSH client binary can be accessed as
/usr/bin/ssh. Note that
when using the -via option, the host machine name
should be specified as known to the gateway machine, e.g. "localhost"
denotes the gateway,
not the machine where vncviewer was launched. The
environment variable VNC_VIA_CMD can override the default
tunnel command of
/usr/bin/ssh -f -L "$L":"$H":"$R" "$G" sleep 20. The
tunnel command is executed with the environment variables L, H, R, and
G taken the val‐
ues of the local port number, the remote host, the port
number on the remote host, and the gateway machine respectively.
(Ironically, that's a quote from the xvnc4viewer manpage, not xtightvncviewer)
Vinagre's a good program and I could see it replacing the above tools
in many sysadmins' arsenals with just a little more tweaking.
How about doing VNC-over-SSH by giving you a place to type host or
user@host and also a place to enter any other ssh options you need
(like -p <portnum>). Or honoring the contents of $HOME/.ssh/config
and pointing people there.