Message: previous - next
Month: February 2011

konqueror sftp:// URL handling broken with openssh >= 5.6 (open a bug?)

From: "David C. Rankin" <drankinatty@...>
Date: Sat, 26 Feb 2011 19:26:40 -0600
Tim, Robert, Serghei, All

  There is an error in konqueror sftp URL handling that causes sftp from
konqueror to fail. I first reported this back in October 2010 on the various
lists reporting that the konqueror url syntax 'sftp://user@host:port/path' no
longer works after an update to one of the associated packages (probably openssh
>= 5.6). IIRC, I also forwarded it to Tim at the time. (~ 10/7/2010)

  Back in October, sftp 'in konqueror' continued to work to boxes where ssh was
on the standard port 22, but would fail if sftp had been moved to a high port.
'fish' continued to (and continues in Trinity to) work to both standard and
non-standard ssh ports.

Fast-forward to 'today' with Trinity svn.

  (1) sftp in konqueror fails to work at all:

the sftp target host in the screenshot above (dcrgx2) has ssh on the standard
port 22. Now konqueror will not talk to any host - on standard or high port.

  (2) fish continues to work just fine (both standard and high ports)  (standard) (high)

  (3) sftp from the command line in Trinity (konsole) works fine to either high
or standard ports:

  So the problem is definitely with konqueror's handling of the sftp URLs and
how it passes that information to openssh. This is a distribution generic
problem with KDE3 after the change to openssh (I'm pretty sure). In older
releases of distros (like SuSE 11.0 - sftp in konqueror continues to work normally)

  The bottom line for Trinity going forward is that the normal konqueror sftp
syntax of:


is broken. This is confirmed as a konqueror problem because, in Trinity (and
kde3 in general), the command line syntax:

  sftp -Pport user@host:/dir1/dir2

continues to work fine. So as does 'fish://'.

  I have researched this issue for a couple of months and the best I can tell is
the problem is in kdebase/kioslave/sftp. There were references to an old Gentoo
bug that fixed ksshprocess.cpp line 101 to regarding and openssh 3.6 problem
with "ssh-userauth2 successful:", but I know that doesn't have anything to do
with the current problem. It may be the same file that needs fixing now, but
different problem.

  For Trinity, do we want to open up a bug report so this one can be tracked, or
do we want to work it from the mailing list? Either way, the fix is probabl
simple, but this is a biggie for sftp functionality.


David C. Rankin, J.D.,P.E.