My putty not work after dup to VERSION_ID=“20180425” of the Tumbleweed now.
while a connection I see a window with text: Disconnected: No supported authentication methods available (server sent: publickey,keyboard-interactive)
but I can connect by ssh with my key to any servers.
nick@STRELKA:~> ssh 172.25.0.222
Last login: Sun Apr 29 16:11:05 2018 from 172.25.0.225
Have a lot of fun…
Thanks, but I use rsa. Ok, I’ve made a new keys, but result is the same. I’ve tryed with different servers, it was Centos7, Tumbleweed. The client is a last Tumbleweed. I’ve not made any keys by the putty, it has got id-rsa key file from my .ssh dir. But after last update of Tumbleweed the putty is not connect. It was worked yesterday. The problem started after the update. Please check my example, the ssh is work fine now. I will check an update history…
I think, the putty is nonchanged… Yet, I’ve got and successfully compiled last putty from it site, the result is the same.
My keys are all originally openssh keys, imported to PuTTY. So that’s not the issue.
Check permissions very carefully. And check “sshd_config” on Tumbleweed. In my experience, “sshd” is fussy about permissions. The “.ssh” directory must be owned by either the user (i.e. you) or by root, and must not be group writable or other writable. And the authentication config in “sshd_config” must allow the kind of authentication that you are using.
There’s a log option in Putty. Maybe you can use that to get a better idea on what is going wrong.
Good. It should never have been defined in the first place.
Looking on Leap 15.2, I see
But I am using KDE, so I want to use “ksshaskpass” instead of the one that is defined. So I have to override that anyway.
I did test this a few days ago. Running “ssh-add key < /dev/null” currently brings up “ksshaskpass” when I am running KDE, but brings up the “ssh-askpass” built into openssh when I am not in KDE. A predefined SSH_ASKPASS is not needed unless you want to force a particular version.
test -S "$SSH_AUTH_SOCK" -a -x "$SSH_ASKPASS" will be ‘false’ always now. ($SSH_ASKPASS is not defined)
so, ‘ssh-add’ command not launch.
You can define SSH_ASKPASS in your shell startup files or in your desktop startup files (if your desktop supports that).
I recommend to correct part of xinitrc file to this view:
if test -S “$SSH_AUTH_SOCK”; then
ssh-add < /dev/null
What you think about?
I launch “ssh-add” when I am ready. I don’t want it as part of desktop startup. But we all have different preferences, and that’s why you can configure such things yourself.
The story started when I’ve lost putty functionality after Tumbleweed upgrade.
The SSH_ASKPASS variable still undefined.
Yes, I use KDE. ksshaskpass is installed…
But I can’t login to remote hosts by ssh key. It work after manually ssh-add command.
What changed after Tumbleweed update and what is better way to use the putty with ssh keys from KDE?
Perhaps putty needs to be updated to also look at “/usr/libexec/ssh”.
You can maybe try making “/usr/lib/ssh” a symbolic link to “/usr/libexec/ssh” and see if that fixes your problem. And if that does fix it, you should file a bug report about Putty needing to be updated to use “libexec”.
I guess I have always used “ssh-add” to add the keys that I use with Putty. And I don’t currently have Putty installed.
I will maybe install Putty in Tumbleweed, and experiment with it. But I’ve never done it that way. I have used Putty in openSUSE, but always using “ssh-add” for the keys. I guess it won’t hurt for me to experiment.