GNOME Bugzilla – Bug 306596
sftp:// does not report an error when RSA keys conflict
Last modified: 2006-06-12 20:10:55 UTC
Please describe the problem: When there is a conflict regarding the entry in ~/.ssh/known_hosts and the target of sftp://, gnome-vfs gives no error dialogue or any sort of indication that there is a problem. Steps to reproduce: 1. Change/regenrate the RSA key in a remote host that has an entry in known_hosts 2. sftp:// to that machine 3. Actual results: A "Cancel Open" dialogue appears after a short wait. Expected results: An error message reporting the conflict should appear immediately, in a similar manner to what ssh and sftp provide. Does this happen every time? Yes. Other information:
Thanks for your bug. What version of gnome-vfs/nautilus do you use? How do you open the URI? Here nautilus opens a dialog describing the issue with 2 choices
Funny enough I was just about to report this same today as my website changed hosts. Background info: So I try to access sftp://tigert@very.hard.to.guess.com. The host has a conflicting entry on my ~/.ssh/known_hosts since I did not fix known_hosts yet, and luckily bumped to this problem. I had already a "desktop mount" to my site (via "connect to server..") on the desktop that I had been using with the previous server without a problem of course, and it puzzled me for a moment as to why nautilus briefly froze, but then recovered again, but there was no error message or notification as to the nature of the problem - just as nothing had even happened. When I try to open the same uri from the location bar on an existing nautilus window, it gives me the "Nautilus cannot display "sftp://foo@blaa.com", please select another viewer and try again" which sounds plain wrong as the "default error message" for issues like this, since it is not at all a "viewer" problem.
Oh, and this is Ubuntu, latest Dapper as of today. $ pkg-config --modversion gnome-vfs-2.0 2.14.0
$ nautilus --version Gnome nautilus 2.14.0
Marking this as a duplicate of a newer bug 318251 that has more info. *** This bug has been marked as a duplicate of 318251 ***