Please try with the March 1 beta of the SSH Secure Shell Windows
client. It should work now, even though I am not sure if it has been
fully tested. If you have problems, please report it as a bug to
[EMAIL PROTECTED]
Tatu
Keith A. Iverson writes:
> I am attempting to connect to an SSH2 server (UNIX) from an SSH2
> Windows client (Have tried both the F-Secure client as well as the
> new SSH2 Windows Beta). I have the server configured to require BOTH
> pubkey AND password. The windows client chokes on this saying that
> Authentication failed. My other UNIX clients and Mac clients do not
> have any problems connecting - first prompts me for passphrase then
> password and authenticates correctly. I have tried numerous methods
> for generating and propagating the pubkey to/from client/server - no
> go with the Win client. If I comment out the
> 'RequiredAuthenticationMethods' line from my SSHD2 server, then my
> Windows client can login. It appears that the Windows client does
> not support multiple authentication methods? I.e., it can
> authenticate with either password OR pubkey, but can't authenticate
> with both in the same session request. I would call this a bug. Is
> there some sort of config setting on the Win client that I am
> missing? I do not want to have to turn off my required auth methods
> just to support Windows. Thoughts?
>
> Thanks,
> Keith
--
SSH Communications Security http://www.ssh.com/
SSH IPSEC Toolkit http://www.ipsec.com/
SSH Secure Shell http://www.ssh.com/ssh
