Skip to main content
7 events
when toggle format what by license comment
S Dec 12, 2022 at 8:46 history suggested not2savvy CC BY-SA 4.0
fixed a typo
Dec 12, 2022 at 0:21 review Suggested edits
S Dec 12, 2022 at 8:46
Jul 18, 2022 at 14:47 comment added Adam Katz You're right, the error from StrictHostKeyChecking=yes is rather explicit ("No ECDSA host key is known for localhost and you have requested strict checking.") If you cleared your ~/.ssh/known_hosts, then perhaps the issue is your GlobalKnownHostsFile, e.g. /etc/ssh/ssh_known_hosts, but that's not automatically populated.
Jul 16, 2022 at 13:21 comment added becke-ch OS: Ubuntu 20.04.4 LTS; SSH/SFTP/SSHD: OpenSSH_8.2p1 Ubuntu-4ubuntu0.4, OpenSSL 1.1.1f 31 Mar 2020; because the known_hosts file was quite long I just emptied it but the error/bug still occurrs and "-o StrictHostKeyChecking=ask" seems not working/fixing. I either get "Offending ECDSA key in ... known_hosts ..." or "Offending RSA key in ...". It seems an OpenSSH bug that these public key algorithms cannot coexist. And Strict Host Checking actually should not prevent that different algorithms can be used in parallel. Could you get it working?
Jul 14, 2022 at 21:39 comment added Adam Katz Could you comment on what your ~/.ssh/known_hosts looks like? Also, what are you running as the client (OS, sftp, OpenSSH versions)?
Jul 14, 2022 at 21:36 comment added becke-ch Hi Adam, no this is not working "-o StrictHostKeyChecking=ask" does not make any difference. Did you test it yourself? My local sshd and sftp is "OpenSSH_8.2p1 Ubuntu-4ubuntu0.4, OpenSSL 1.1.1f".
Jul 14, 2022 at 20:53 history answered Adam Katz CC BY-SA 4.0