Bug 1057871

Summary: x2goclient fails to connect with password ("Authentication failed")
Product: [Fedora] Fedora Reporter: Michael Lipp <mnl>
Component: x2goclientAssignee: Orion Poplawski <orion>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 20CC: cpanceac, lsof, mnl, orion
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: x2goclient-4.0.1.3-3.fc20 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-07 03:12:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Michael Lipp 2014-01-25 15:39:03 UTC
Description of problem:
Trying to connect to any of my x2goservers, I get "Authentication failed". I'm sure that I have typed the proper password (I even copy/pasted it to be sure).

Version-Release number of selected component (if applicable):
4.0.1.2-1.fc20

How reproducible:
Always

Steps to Reproduce:
1. Start x2goclient
2. Choose profile
3. Type password

Actual results:
Dialog box "Authentication failed"

Expected results:
Successful login

Additional info:
x2go client on Ubuntu works for all servers
pyhoca-cli works using the profiles from x2go

Comment 1 Michael Lipp 2014-01-25 17:33:16 UTC
I just found out that I can use x2go if I use the RSA-/DSA-key option instead of typing my password.

Comment 2 Orion Poplawski 2014-01-25 18:05:16 UTC
What version of libssh?
Any help to downgrade libssh or x2goclient?
Can you try https://admin.fedoraproject.org/updates/FEDORA-2014-1402/x2goclient-4.0.1.3-2.fc20
Any special characters?  What keyboard layout do you use?

Comment 3 Michael Lipp 2014-01-25 19:41:26 UTC
* libssh: 0.6.0-1.fc20
* How can I downgrade? 
* Installing 4.0.1.3-2 doesn't help
* Yes, using special characters in my password, of course. And German keyboard layout. But as mentioned, I tried with copy/paste (entering password visible in editor and then pasting). But to make sure, I just rechecked with a "simple" password, doesn't help.

Comment 4 Orion Poplawski 2014-01-26 03:52:04 UTC
To downgrade:

yum downgrade libssh

Running sshd in DEBUG3 logging mode on the server and looking the /var/log/secure messages from a connection could verify what password is transmitted.

Comment 5 Michael Lipp 2014-01-29 15:22:11 UTC
* Downgrading libssh solves the problem
* From what I see in DEBUG3, it closes the connection before passwords are exchanged (I cannot find the password in the log)

Now question is, is it safe to use the downgraded libssh? Surly the latest version fixes security issues...

Comment 6 Orion Poplawski 2014-01-29 15:43:06 UTC
It's safe - 0.6.0 was more of a (apparently broken) feature update.

Comment 7 Orion Poplawski 2014-01-29 15:54:36 UTC
The other workaround should be to delete the server's entry in your ~/.ssh/known_hosts file.

Comment 8 Michael Lipp 2014-01-29 16:03:47 UTC
No. I even deleted the complete ~/.ssh/known_hosts to be sure: doesn't help.

Comment 9 Orion Poplawski 2014-01-29 16:04:44 UTC
Ah, you are correct, I wonder why..

Comment 10 Orion Poplawski 2014-01-29 16:34:58 UTC
Okay, I figured this out.  Indeed a bug in x2goclient.

Comment 11 Fedora Update System 2014-01-29 17:20:51 UTC
x2goclient-4.0.1.3-3.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/x2goclient-4.0.1.3-3.fc19

Comment 12 Fedora Update System 2014-01-29 17:21:04 UTC
x2goclient-4.0.1.3-3.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/x2goclient-4.0.1.3-3.fc20

Comment 13 Michael Lipp 2014-01-29 17:32:46 UTC
x2goclient-4.0.1.3-3.fc20 works for me. Very nice. Thanks!

Comment 14 Need Real Name 2014-01-29 22:35:05 UTC
That error goes away for me, but x2goclient still fails later:

Connection failed Can not create remote file ~user/.x2go/ssh/key.HfB525 - scp status code 1d not valid

Comment 15 Orion Poplawski 2014-01-29 22:42:11 UTC
Yeah, that's bug 1056757 - I wasn't sure that it completely blocked the connection though.

Comment 16 Fedora Update System 2014-01-30 03:37:06 UTC
Package x2goclient-4.0.1.3-3.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing x2goclient-4.0.1.3-3.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-1786/x2goclient-4.0.1.3-3.fc20
then log in and leave karma (feedback).

Comment 17 Michael Lipp 2014-01-30 21:52:45 UTC
(In reply to Orion Poplawski from comment #15)
> Yeah, that's bug 1056757 - I wasn't sure that it completely blocked the
> connection though.

I get the message as well, but things continue to work here.

Comment 18 Need Real Name 2014-01-31 06:20:51 UTC
(In reply to Orion Poplawski from comment #15)
> Yeah, that's bug 1056757 - I wasn't sure that it completely blocked the
> connection though.

WFM now too.

Comment 19 cornel panceac 2014-02-02 18:00:12 UTC
i get

Connection failed Can not create remote file ~cornel/.x2go/ssh/key.MT7522 - scp status code 1d not valid

but i can actually connect to the remote macine. Only the local client was updated as instructed on comment #6.

Thank you.

Comment 20 Fedora Update System 2014-02-07 03:12:28 UTC
x2goclient-4.0.1.3-3.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 21 Fedora Update System 2014-02-07 03:13:49 UTC
x2goclient-4.0.1.3-3.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.