https://bugs.kde.org/show_bug.cgi?id=274170
--- Comment #18 from Roland Pallai <da...@magex.hu> --- (In reply to Roland Pallai from comment #17) > I still have an issue with kio-sftp if ed25519 type key is *present* in > known_hosts file for the host. It does not matter if correct rsa/ecdsa keys > are present - if there is ed25519 type key for the host, verification always > fails [1] and the hosts' ecdsa key will be appended to known_hosts file > every time I click 'connect'. > > This is a bad behavior regardless of supported key types - the correct > behaviour is that not supported key types must be ignored and supported key > type must be used. > > Should I file a new bug report that draws attention to this bad behavior > instead of supported key types..? > > [1] The authenticity of host [...] cannot be established. The > ecdsa-sha2-nistp256 key fingerprint is: [...] Are you sure you want to > continue connecting? > > Fedora 37 > kf5-kio-core-5.101.0-1.fc37.x86_64 > libssh-0.10.4-2.fc37.x86_64 After some digging I'm sure this is a libssh issue as ssh_session_is_known_server() returns with SSH_SERVER_NOT_KNOWN when ed25519 key is present in known_hosts. There is nothing to fix in kio-sftp.. -- You are receiving this mail because: You are watching all bug changes.