You are not logged in.
Hi all,
I keep getting asked the following question over and over on each re-connection to the same host:
The authenticity of host gigsdb cannot be established.
The ssh-ed25519 key fingerprint is: SHA256:WpHn3EO+vQeFjwm0s0dfP/yx5RpbIhMGa+FFMlL1pSo
Are you sure you want to continue connecting?gigsdb host is configured in ~/.ssh/.config with IP, user and private key.
The ssh-ed25519 key is getting written to known_hosts over and over, like it wouldn't actually be there.
I only get this behavior from Konqueror/Dolphin/Krusader for many hosts, not only for gigsdb. The native ssh/sftp clients perform as expected.
I found some suggestions about using the StrictHostKeyChecking no setting, but that doesn't solve trashing the known_hosts file.
Any clues?
Thanks in advance.
Last edited by mdcclxv (2022-05-02 22:36:41)
Offline
I've been caught out by that prompt a few times. Did you try answering "yes" (all three characters) to confirm? Just "y" or "Y" won't work
Offline
I've been caught out by that prompt a few times. Did you try answering "yes" (all three characters) to confirm? Just "y" or "Y" won't work
This only happens with Konqueror/Dolphin/Krusader, which are GUI tools, they show a message box with Yes/No buttons, there is no prompt.
Also, as I said, the key does get written into known_hosts, so there's definitely happening a working yes there.
Last edited by mdcclxv (2022-05-01 01:23:32)
Offline
If you move away known_hosts and try to re-connect, do you get asked once more and then no longer (resulting in the one relevant entry)?
I could imagine a bug in the kio (I guess) module when reading that file causes it to fail on a specific line (don't ask me, if you want to take a look, look for soemthing that looks formatted differently than what kio adds) and give up on testig for known_hosts…
Online
The ssh-ed25519 key is getting written to known_hosts over and over, like it wouldn't actually be there.
And these entries are exactly the same?
Try raising verbosity (ssh -vvv) to get more debug info. Another attempt would be an 'strace' log. Maybe the file cannot be accessed or something.
Last edited by Maniaxx (2022-05-01 17:03:18)
sys2064
Offline
@seth: that did the trick. You rock! Thanks a million.
@Maniaxx, @skunktrader: thank you for your time and involvement.
Last edited by mdcclxv (2022-05-02 22:35:21)
Offline