no way to change username for ssh tunneling

[torzsmokus]

Binary package hint: vinagre

Intended action:
connect to a firewalled machine using VNC with SSH tunneling

Steps:
1., start Vinagre
2., Machine > Connect
3., select Protocol: VNC, fill in Host
4., check Use host [remote.host] as a SSH tunnel
5., select Connect
6., a the dialog appears saying Host: [my current username on the local machine]@[remote.host] which is not the desired login !
7., so I am asked to provide a password for a nonexistent user on the remote machine, which I obviously cannot do.

What should happen:
either on the Connect or the Password dialog box, one should have an option to provide the user name for the remote machine

Versions:
Ubuntu 10.04 LTS (up-to-date)
vinagre 2.30.0-0ubuntu2

[torzsmokus (torzsmokus)]

oh, I figured out (from the tooltip of the Host field) that I can enter [<email address hidden>]
but IMHO this is not intuitive enough. there should be a separate field for remote username, maybe defaulting to the local one.

[W. J. van der Laan (laanwj)]

Agree, I got this wrong as well the first time. In my case, it didn't even show what the error was (not providing the xxx@ username) but a generic "could not connect to SSH tunnel".
When I provided user@host instead of just the host it went fine.
I vote for a separate "remote user" field or a GUI-based warning when trying to save settings without entering a username.

[Victor Vargas (kamus)]

shall we mark this issue as a requirement to include a box for put only a username right, in case you are using ssh tunnels of course?

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

[Vish (vish)]

Thank you for bringing this bug to our attention. However, a paper cut should be a small usability issue, in the default Ubuntu install, that affects many people and is quick and easy to fix. So this bug can't be addressed as part of this project.

 - using sshis not a feature an average user uses, it is an advanced user scenario. Not a papercut.
For further information about papercuts criteria, please read https://wiki.ubuntu.com/PaperCut.

Don't worry though, this bug has been marked as "Invalid" only in the papercuts project.

And marking vinagre task incomplete too.
@ torzsmokus : Kindly answer to the question asked in comment #3 and then set the bug to status 'new' .

[torzsmokus (torzsmokus)]

Sorry, I didn't notice #3 was a question to me (and not to the devs).
I don't fully understand what Kamus wants to know, but if I get it right, I suppose it's already answered in my first comment:
> there should be a separate field for remote username, maybe defaulting to the local one.

[Victor Vargas (kamus)]

maybe that sounds confused, what I tried to explain you was if you want include a textbox (box) to fill username instead of pass something like username@your-host-here (same when you are using a SSH connection), isn't?

[torzsmokus (torzsmokus)]

Yes, exactly, that's what I already suggested: a separate box (field) for remote username.

[Jan (jancborchardt-deactivatedaccount)]

Unsubscribing the Papercutters team.

[wild.ideas (wild-ideas)]

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.