Ubuntu
vinagre package

The SSH tunnel can't be established to a different port.

Bug #594746 reported by Jon "The Nice Guy" Spriggs
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Vinagre: VNC client for GNOME
Fix Released
Medium
vinagre (Ubuntu)
Fix Released
Low
Unassigned
Lucid
Fix Released
Low
Sebastien Bacher

Bug Description

Binary package hint: vinagre

I use a non-standard port for my SSH daemon, and the Vinagre client won't permit me to use the non-standard port I use.

It's quite obvious that it's not using the file ~/.ssh/config as that does specify the non-standard port.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: vinagre 2.30.1-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
Architecture: i386
Date: Tue Jun 15 19:08:30 2010
EcryptfsInUse: Yes
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Beta i386 (20100318)
ProcEnviron:
 PATH=(custom, user)
 SHELL=/bin/zsh
 LANG=en_GB.utf8
SourcePackage: vinagre

Revision history for this message
Jon "The Nice Guy" Spriggs (jontheniceguy) wrote :
Revision history for this message
Jonh Wendell (wendell) wrote :

I'm working on it.

Bug Watch Updater (bug-watch-updater)
Changed in vinagre:
status: Unknown → Confirmed
Revision history for this message
Jonh Wendell (wendell) wrote :

fix committed also in gnome-2-30 branch. I'll release 2.30.2 next week (Jun 21)

Bug Watch Updater (bug-watch-updater)
Changed in vinagre:
status: Confirmed → Fix Released
Revision history for this message
Sebastien Bacher (seb128) wrote :
Changed in vinagre (Ubuntu):
importance: Undecided → Low
status: New → Fix Committed
Changed in vinagre (Ubuntu Lucid):
assignee: nobody → Sebastien Bacher (seb128)
importance: Undecided → Low
status: New → Fix Committed
Revision history for this message
Sebastien Bacher (seb128) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package vinagre - 2.30.2-0ubuntu1.1

---------------
vinagre (2.30.2-0ubuntu1.1) maverick; urgency=low

  * New upstream version
    - Removed password length limit for SSH connections (lp: #588532)
    - Allows using of an alternative ssh port when doing tunnel
      (lp: #594746)
 -- Sebastien Bacher <email address hidden> Mon, 21 Jun 2010 16:53:47 +0200

Changed in vinagre (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Steve Langasek (vorlon) wrote : Please test proposed package

Accepted into lucid-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

tags: added: verification-needed
Revision history for this message
Rocko (rockorequin) wrote :

The fix works nicely, thanks.

In a possibly related note, it would be nice if the 'Host' setting automatically defaulted to localhost if left blank. I imagine that this would be the most likely candidate for a target host when using a ssh tunnel in vinagre, and it's not particularly obvious what to type in there from the connection screen.

Sebastien Bacher (seb128)
tags: added: verification-done
removed: verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package vinagre - 2.30.2-0ubuntu1

---------------
vinagre (2.30.2-0ubuntu1) lucid-proposed; urgency=low

  * New upstream version
    - Removed password length limit for SSH connections (lp: #588532)
    - Allows using of an alternative ssh port when doing tunnel
      (lp: #594746)
 -- Sebastien Bacher <email address hidden> Mon, 21 Jun 2010 16:25:44 +0200

Changed in vinagre (Ubuntu Lucid):
status: Fix Committed → Fix Released
Revision history for this message
Rocko (rockorequin) wrote :

The fix worked when I tried connecting from home, but it doesn't seem to work over the internet. I just get 'connection closed'. Perhaps my router forwarding affected the testing?

The router forwards port 8822 to port 22 on the networked machine. My test is to get vinagre to create a ssh tunnel on the connection to the external address on port 8822. I've still got vinagre v 2.30.2-0ubuntu1 installed. I can connect if I connect with ssh forwarding port 6000 to the remote VNC port and then just connect with vinagre to localhost:6000, so everything is set up correctly for it to work as far as I can see.

Is this likely the same bug, or another one?

Bug Watch Updater (bug-watch-updater)
Changed in vinagre:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.