Am Mittwoch, 12. Juni 2019, 21:53:28 CEST schrieb Étienne Mollier: > Thomas, on 2019-06-12 :
> Hmn, I spent a bit of time to check that both sftp in command > line, and konqueror (independently of fish:// or sftp:// URL) > were using the same file $HOME/.ssh/known_hosts. Unless the > HOME variable differs, the known_hosts file is used in all > cases. > > Your use of a hash "#" as a prompt suggests you launched your > sftp command line as the administrative user "root". In the > meantime your konqueror instance is probably running as your > regular user account. Was the fish:// connection attempt done > on the same konqueror window as the sftp:// attempt? If not, > maybe you just need to cleanup your host key for your regular > user account too. Hi, yes, it was same konquerer window now , again fresh tried: konquerer window fresh open, same tab ## fish://root@192.168.1.20 # OK ## sftp://root@192.168.1.20 # NOT OK error message is short translated: did not find host key but other type of key existing may be hacker try to change key konsole in user mode (NOT root) (1) # sftp 192.168.1.20 The authenticity of host '192.168.1.20 (192.168.1.20)' can't be established. ECDSA key fingerprint is SHA256:+KS/FE5iyW7zLmLcZ2OnIWTZ1BmtvA0F/4WBLUrs4bM. Are you sure you want to continue connecting (yes/no)? (there might be an difference because user name on server and PC are different) (2) # sftp thomas@192.168.1.20 thomas@192.168.1.20's password: (3) # sftp root@192.168.1.20 root@192.168.1.20's password: konsole in user mode ROOT working in all cases! sftp 192.168.1.20, thomas@192.168.1.20, sftp root@192.168.1.20 Sorry, thats now gets confusing... Thanks... Thomas