GNOME Bugzilla – Bug 132474
SFTP Module Authentication Dialog---Abscence Thereof.
Last modified: 2004-12-22 21:47:04 UTC
From Applications=>Network Servers=>Connect to Server: If I input sftp://login@host, where login for host has not ever prompted about the authenticity of host by asking whether to continue connecting from the console, and double-click on the new connection, the opening will hang and produce a dialog box "Cancel Open?" If I cancel the "Open" and sftp via the console into the host and verify the authenticity of my destination and retry the previous, it will prompt me with an "Authentication Required" dialog; however, the "Cancel Open" dialog will appear as well. This behavior seems rather backward.
Further information which may be helpful in resolving this bug: As of using the latest 2.6 release, I have noticed that this problem still occurs, but yet slightly differently now than before. Take a server like "d.umn.edu" for example, a server to which you have never connected before. Steps to visualize the problem: 1.) Go to the console; type in "ssh asdf@d.umn.edu" # I can only hope that this is not a real login. 2.) Engage the command and upon its prompting of "The authenticity of host 'd.umn.edu (131.212.161.1)' can't be established. RSA key fingerprint is 5a:51:8e:d5:b3:da:37:8d:f1:3f:c7:a2:c8:8c:4e:3d. Are you sure you want to continue connecting (yes/no)?", type (NO). 3.) Go to Nautilus's "Connect to Server"; type "asdf" into Link Name and "sftp://asdf@d.umn.edu" 4.) Click Connect, and the double-click on the "asdf" connection on the desktop. 5.) Wait a minute and observe the dialog that spawns shortly: "The action associated with "sftp: d.umn.edu" is invalid." (Direct Copy-and-Paste) 6.) Click Cancel; unmount the volume. 7.) Return to the console and "ssh asdf@d.umn.edu"; this type "yes". The authenticity of host 'd.umn.edu (131.212.161.1)' can't be established. RSA key fingerprint is 5a:51:8e:d5:b3:da:37:8d:f1:3f:c7:a2:c8:8c:4e:3d. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added 'd.umn.edu,131.212.161.1' (RSA) to the list of known hosts. asdf@d.umn.edu's password: 8.) Close the connection. 9.) Return to Nautilus's "Connect to Server" dialog. 10.) Perform steps #3 and #4 and wait a moment. 11.) An expected "Authentication Required" dialog will spawn. In the end, Nautilus should have behaved as listed in steps #9, #10, #11, and be it necessary, spawn some "gnomed" version of the "The authenticity of host 'd.umn.edu (131.212.161.1)' can't be established. RSA key fingerprint is 5a:51:8e:d5:b3:da:37:8d:f1:3f:c7:a2:c8:8c:4e:3d. Are you sure you want to continue connecting (yes/no)?" response.
This bug is about the same issue as bug 140749. That bug also links to a mailing-list thread with discussion related to this. This bug should probably be marked a duplicate of bug 140749.
*** Bug 140749 has been marked as a duplicate of this bug. ***
This should be fixed in 2.7.