Bug 825723 - remmina cannot connect to lsh-based servers
remmina cannot connect to lsh-based servers
Product: Fedora
Classification: Fedora
Component: remmina (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Christoph Wickert
Fedora Extras Quality Assurance
: Triaged
Depends On:
  Show dependency treegraph
Reported: 2012-05-28 05:43 EDT by Enrique
Modified: 2013-02-13 08:23 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-02-13 08:23:24 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Enrique 2012-05-28 05:43:16 EDT
Description of problem:

 I am trying to connect to a vnc server with remmina using a ssh tunnel. The ssh server uses lsh (http://www.lysator.liu.se/~nisse/lsh/) to implement the ssh server and remmina hangs trying to create the ssh connection. If I use the openssh server instead, then everything works fine.

Version-Release number of selected component (if applicable):


On the VNC/LSH server:
lsh-server 2.0.4-dfsg-6 (Linux Mint 9)

How reproducible:

Steps to Reproduce:
1. On the VNC/LSH server: vncserver
2. On the Fedora 15 client, create a connection with a "Enable SSH tunnel".
The ssh server is the address of the VNC/LSH in my LAN. I am trying to connect using "Public key (automatic)". In the basic tab the server points to localhost:1
3. This configuration works if the server uses openssh-server rather than lsh-server.
Comment 1 Rex Dieter 2012-05-28 20:42:40 EDT
reassinging rekonq->remmina
Comment 2 Christoph Wickert 2012-05-29 03:32:31 EDT
Do you see any debug output on the console when it hangs?
Comment 3 Fedora End Of Life 2013-01-16 07:49:26 EST
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 4 Fedora End Of Life 2013-02-13 08:23:28 EST
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.