Username & Password fields seems to be ignored
$ tail /var/log/auth.log
[skip]
Dec 28 23:44:03 xxx sshd[4850]: Invalid user from 127.0.0.1
Dec 28 23:44:03 xxx sshd[4850]: pam_unix(sshd:auth): check pass; user unknown
Dec 28 23:44:03 xxx sshd[4850]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=localhost
$ sudo netstat -tlp|grep ssh
cp 0 0 localhost:ssh *:* LISTEN 15479/sshd
[skip]
PS:
libssh2 version 1.2.2
Bindings for the libssh2 library: 0.11.0-dev (debian package from squeeze)
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | 1009162-5.ssh-username-busted.patch | 909 bytes | dww |
Comments
Comment #1
carlos8f commentedHi, can you reproduce this bug with RC3? We are pretty far past beta3 at this point.
Comment #2
skirpichev commentedSorry, it's my wrong tagging. This issue has been tested for rc3 (not beta3).
Comment #3
skirpichev commentedlevel up priority (ssh support for update is not usable anyway)
Comment #4
ogi commentedSimple fix in #1011972: SSH username authorize field is not correctly handled. More radical changes in #1010506: FileTransfer doesn't properly handle any advanced settings nor the ssh username.
Comment #5
dwwReposting Ognyan Kulev's patch from #1011972: SSH username authorize field is not correctly handled in here. I'm happy with the code, it was an obvious typo from an earlier patch. I think this is a trivial, obvious fix that could go in now, independently of the bigger surgery in #1010506: FileTransfer doesn't properly handle any advanced settings nor the ssh username chx and I are arguing about now.
Comment #6
dwwOkay, upon closer inspection, we really do need #1010506: FileTransfer doesn't properly handle any advanced settings nor the ssh username. Even though that's a later node ID, let's just fix this there, since it's got more info.