SSH2 Server fails to authenticate putty/winscp/filezilla
See original GitHub issueUnix-based clients like the ssh command or several sftp clients are able to connect against my own ssh server implementation, which currently only supports the “password” authentication method. However, using putty, winscp or filezilla, which are widely used in the windows world, fail to authenticate. The behaviour goes as follows:
ssh
command:
The client connects, the different auth methods are tried (‘none’, ‘keyboard-interactive’, ‘publickey’), which all get rejected with ctx.reject(), until the client finally ask for ‘password’ method, which then authenticates successfully with ctx.accept()
putty
/winscp
/filezilla
:
The client connects, tries to authenticate with the “none” method. I ctx.reject() the “none” authentication method, which causes the client to fail directly with client error message "Disconnected: No supported authentication methods available (server sent: )"
. The client will not try any more authentication methods.
I have tried to change several options in putty, but they all lead to the same behaviour.
Any ideas why this is happening?
Issue Analytics
- State:
- Created 9 years ago
- Comments:6 (3 by maintainers)
Same issue here, using [‘password’, ‘publickey’], true works like a charm, do you want a PR to make this more explicit in the doc ?
Elegant patch, works perfectly, thanks for implementing this feature. You’re the man!