Hi Mihai
 
I have found the problem. The prompt of the SSH server is coded in the source code of x2goclient.
We use for authentication via SecurID a different SSH promtp to emphasize the difference. Last week I already changed the prompt of the SecurID prompt to be the same as the normal SSH, but I didn't notice the blank after the "Password: "...
Unfortunately, I haven't managed to get the blank space at the end of "Password: ". So I just edited the source code of the x2goclient, and changed the line where the expected prompt is defined.
This solution worked.
Would it make sense to include the expected ssh prompt as a parameter in x2go in order to avoid having to recomplie the source code in a such case?
 
Regards
Swizzly
 
 
 
 
Gesendet: Samstag, 14. März 2015 um 17:46 Uhr
Von: "Mihai Moldovan" <ionic@ionic.de>
An: "swizz ly" <swizz.ly@gmx.ch>, x2go-user@lists.x2go.org
Betreff: Re: [X2Go-User] X2Go Two-factor-authentication with SecurID
On 14.03.2015 10:48 AM, swizz ly wrote:
> [...]
> I get the same results: no messages at the RSA console, if I make a
> normal SSH connection forcing password authentication:
> "ssh -o PreferredAuthentications=password -o PubkeyAuthentication=no
> user@server".
> Can it be that x2goclient forces the password authentication
> explicitely if there is no publickey?

Maybe. I have to check. Will do this later.

Shouldn't pam-radius also use password+keyboard-interactive, though?
Given that it works for Nick, I'm skeptical when it comes to x2goclient
forcing password auth. I may be wrong by assuming pam-radius does uses
keyboard-interactive authentication right after password authentication,
though.



Mihai