Sorry, it actually worked. I just had to import key with puttygen and prepare it for putty and winscp. Now it works.... Thanks, regards, Rob. ----- Original Message ----- From: "Robert Rozman" To: "Christian Volkmann" ; Sent: Thursday, April 14, 2005 3:06 AM Subject: Re: [suse-security] Problems setting up key based ssh access to suse 9.2 ...

Hi,

yes I cannot login in username/password way, but also cannot login with key....

Is problem if I use keys that were generated in Linux on Windows clients (winscp, putty) ?

I get this : Authentication log (see session log for details): Using username "root". Unable to use key file "C:\robi\TINIA\ASTERISK_development\Astera 2\id_dsa" (OpenSSH SSH2 private key) No supported authentication methods left to try!

Connection has been unexpectedly closed. Server sent command exit status 0.

Any advice ?

regards,

Rob.

----- Original Message ----- From: "Christian Volkmann" To: "Robert Rozman" Sent: Thursday, April 14, 2005 2:54 AM Subject: re: [suse-security] Problems setting up key based ssh access to suse 9.2 ...

...

Hi, I am read only to the list.

you might try to turn this parameter off:

# Set this to 'yes' to enable PAM authentication, account processing, # and session processing. If this is enabled, PAM authentication will # be allowed through the ChallengeResponseAuthentication mechanism. # Depending on your PAM configuration, this may bypass the setting of # PasswordAuthentication, PermitEmptyPasswords, and # "PermitRootLogin without-password". If you just want the PAM account and # session checks to run without PAM authentication, then enable this but set # ChallengeResponseAuthentication=no UsePAM yes

Please post to the list if you have success.

Best regards,

Christian

-- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-help@suse.com Security-related bug reports go to security@suse.de, not here