Comment 10 for bug 578733

We need to add one more option: The remote host port number for the SSH connection. Reason: It's not good practice to expose an open Port 22 to the Internet; it attracts relentless break-in attempts from all over the world.

I use a custom port number for SSH into my VNC server machine (stealthed and controlled by UFW & FWKNOP in my case). My router port-forwards this port for incoming SSH, while blocking port 22 traffic. Port 22 use is then restricted to use only within my LAN (for convenience).

In addition, since I have more than one VNC server to connect to, I use different ports to "direct traffic" to the intended machine on my LAN.

Both of these needs prevent use of Port 22 for outside VNC tunneling. Using my custom ports works fine, is secure, does not draw break-in attempts, and allows me to pick & choose which machine I connect to.

The problem is, the "Use host" feature on 'vinagre' does not allow me to specify the port to direct my connection to, and it should.

Note that "Connect to server..." in 'nautilus' *does* allow you to specify the port number -- and this application *is* compatible with the connection scheme I just mentioned. We need 'vinagre' to be equally compatible, so it needs similar features.

In this day & age, secure connections are not an option... and shouldn't be complicated to implement.