Launchpad has imported 9 comments from the remote bug at https://bugs.kde.org/show_bug.cgi?id=299993.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2012-05-14T11:25:49+00:00 B5cej-linux wrote: When connecting to my webserver, putting in dolphins address-line: sftp://username@domain/directory dolphin displays the username/password dialog (username set, password empty although saved in Kwallet). I enter the password and dolphin says "incorrect password". If Iput sftp://username:password@domain/directory the connection works normally. So something goes wrong with the password verification process of dolphin and/or the communication with Kwallet... Until the last update to the recent version I never had this problem, so I guess it is not related to bug 269095??? kind regards Daniel opensuse 12.1, KDE 4.8.3, dolphin 4.8.3-294.1. Reproducible: Always Steps to Reproduce: 1. enter sftp://username@domain/directory in doplhin, try to connect 2. enter the correct password: connection fails Actual Results: dolphin says, username/password are not correct, although they are Expected Results: connection with the server, display of directory contents Reply at: https://bugs.launchpad.net/kde-runtime/+bug/1011961/comments/0 ------------------------------------------------------------------------ On 2012-05-15T11:19:23+00:00 B5cej-linux wrote: note: "fish" and "ftp" works, only "sftp" does not... Reply at: https://bugs.launchpad.net/kde-runtime/+bug/1011961/comments/1 ------------------------------------------------------------------------ On 2012-05-26T16:17:36+00:00 Tim-thawkins wrote: I can confirm this bug, fedora 16 kde, 64bit all latest updates same problem, rejects known good passwords when connection via dolphin and sftp. Reply at: https://bugs.launchpad.net/kde-runtime/+bug/1011961/comments/2 ------------------------------------------------------------------------ On 2012-05-30T02:10:07+00:00 aditsu wrote: It happens to me too (kde 4.8.3 in Gentoo). I would add that if I don't specify the port, it seems to ask for port 0 in the login dialog (sftp://foo:0), but manually adding :22 doesn't help either. Why do you guys keep breaking sftp, again and again?! Reply at: https://bugs.launchpad.net/kde-runtime/+bug/1011961/comments/3 ------------------------------------------------------------------------ On 2012-05-30T09:00:02+00:00 3-asn wrote: https://git.reviewboard.kde.org/r/104642/ Reply at: https://bugs.launchpad.net/kde-runtime/+bug/1011961/comments/4 ------------------------------------------------------------------------ On 2012-06-08T07:56:35+00:00 Tamás Németh wrote: I can't connect to any SFTP server, where /etc/ssh/sshd_config contains "PasswordAuthentication no". And since this is the default in virtually all of my servers, I can't use them anymore. Fix it, please! Commenting out "PasswordAuthentication no" on the server side circumvents the problem, but I wouldn't like to do that. Fix it in 4.8.4, please!!!! Reply at: https://bugs.launchpad.net/kde-runtime/+bug/1011961/comments/5 ------------------------------------------------------------------------ On 2012-06-08T08:59:07+00:00 Arrigo Marchiori wrote: Created attachment 71659 Patch to kioslave/sftp/kio_sftp.cpp to use QString instead of const char * and use info.password instead of mPassword The attached patch solves the problem on my KDE 4.8.3 installation (FreeBSD port). The patch consists of two modifications, both into sftpProtocol::authenticateKeyboardInteractive(), file kio_sftp.cpp 1- the password is taken from the "info" parameter, instead of the private class attribute "mPassword". That attribute is only initialized once (I guess when parsing the URL, and that's why the syntax sftp://user:password@host works), while the "info" parameter is initialized by a KPasswordDialog, and thus contains the password. 2- the variable "answer" is declared as QString instead of const char*, as it is IMHO safer. The current code creates and destroy a QByteArray object, and assigns its "constData" to answer. If I understood correctly, that memory could be overwritten at any time, because the QByteArray is immediately freed after creation. After the patch, the correctness of the buffer is ensured, because the QByteArray is only destroyed when each call returns. Reply at: https://bugs.launchpad.net/kde-runtime/+bug/1011961/comments/6 ------------------------------------------------------------------------ On 2012-06-12T09:07:58+00:00 Tamás Németh wrote: Still not fixed in 4.8.4!!! Reply at: https://bugs.launchpad.net/kde-runtime/+bug/1011961/comments/8 ------------------------------------------------------------------------ On 2012-06-15T08:37:05+00:00 Arrigo Marchiori wrote: *** This bug has been confirmed by popular vote. *** Reply at: https://bugs.launchpad.net/kde- runtime/+bug/1011961/comments/10 ** Changed in: kde-runtime Status: Unknown => Confirmed ** Changed in: kde-runtime Importance: Unknown => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1011961 Title: sftp connection with password fails To manage notifications about this bug go to: https://bugs.launchpad.net/kde-runtime/+bug/1011961/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
