Bug 69104

Summary:	Misleading error message if remote fingerprint has changed
Product:	[Unmaintained] kio	Reporter:	Malte S. Stretz <mss>
Component:	fish	Assignee:	Jörg Walter <trouble>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	gmludo, kdebugs.20.chth
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Malte S. Stretz 2003-11-26 22:41:27 UTC

Version:           unknown (using KDE 3.1.93 (3.2 beta 1), Gentoo)
Compiler:          gcc version 3.2.3 20030422 (Gentoo Linux 1.4 3.2.3-r2, propolice)
OS:          Linux (i686) release 2.4.20-gentoo-r8

If you try to connect via fish://remote to a remote machine and the fingerprint of that machine has changed in between but the old fingerprint is still in known_hosts, the connection will be aborted with the misleading error message "Could not connect to localhost".

Took me quite some time to figure out the actual reason for that message (I suspected an error in kio_fish and didn't try to connect from the console :-/ )

Comment 1 Waldo Bastian 2004-11-19 18:58:01 UTC

I get a correct error message: "Could not connect to host x.y.z"
It could be a bit more informative indeed.

Comment 2 Nicolas Goutte 2005-09-18 02:45:44 UTC

*** Bug 107480 has been marked as a duplicate of this bug. ***

Comment 3 Tommi Tervo 2006-06-26 18:51:13 UTC

*** Bug 129857 has been marked as a duplicate of this bug. ***

Comment 4 Gabor Fekete 2006-11-03 13:01:13 UTC

I have been seeing this for quite a long time now.
Today it happened again at least 2 times. And most of the time it makes
me manually edit the known_hosts file.

kio_sftp/fish should pop up with a window offering to delete the bogus
entry from the known_hosts file and then re-add the new one, IMO.

So... is this bug in kio or somewhere else?

Thanks!

Comment 5 Thorsten Staerk 2008-01-02 16:46:49 UTC


*** This bug has been marked as a duplicate of 135707 ***