Can't browse sftp

Thank you for your bug. Could you try using gvfs-mount and gvfs-ls from gvfs-bin and comment on whether those are working correctly?

gvfs-mount doesn't work.

ubuntu@ubuntu:~$ gvfs-mount ssh://tomcat@hal9000/home/tomcat
Error mounting location: Timed out when logging in

I don' t reproduce this bug with 0.1.7-0ubuntu4.
I am able to reliably mount a sftp location from within nautilus or using gvfs-mount.

is this server using a standard password prompt? could you copy the text you get when using ssh?

It seems here that gvfs-mount is blocked by the RSA fingerprint check. If I run `gvfs-mount sftp://myserver/` on a freshly installed Hardy Alpha5, it fails with "Error mounting location: Zeitüberschreitung beim Anmelden" (ie. timeout during login).

If I run `sftp myserver`, it prints this:
Connecting to myserver...
The authenticity of host 'myserver (192.168.0.1)' can't be established.
RSA key fingerprint is <fingerprint removed>.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'myserver,192.168.0.1' (RSA) to the list of known hosts.
Password:

I don't have to provide the password here, it's enough that the ssh server is now added to known_hosts.

If I then run gvfs-mount sftp://myserver/ again, it asks me for the password and succeeds (I can browse the sftp share in Nautilus afterwards). Deleting ~/.ssh/known_hosts makes gvfs-mount fail again with timeout.

I have the exact behavior Oliver described. Setting to confirmed.

Should we report this upstream?

I guess this is the same problem as described in upstream bug http://bugzilla.gnome.org/show_bug.cgi?id=517460 - the patch there seems to handle the "key fingerprint is" message.

This bug was fixed in the package gvfs - 0.1.8-0ubuntu1

---------------
gvfs (0.1.8-0ubuntu1) hardy; urgency=low

  * New upstream version:
    - Update for gio API changes
    - Add gphoto2 backend
    - Add network: and dns-sd: backend support (lp: #185756)
    - Http and webdav backend updates
    - Keyring support
    - Fix crashes and deadlocks
    - Add trash::item-count attribute to trash:///
    - Fix smb reads > 65535 bytes breaking on some servers
    - Fix cancellation race in reading
    - Fill in thumbnail info for backends
    - sftp: Handle host identity changes (lp: #188790)
    - Enable translations everywhere
    - Add bash completion support for command line apps
    - Fix handling of blank cds and audio cds
    - Support port in sftp uris (lp: #194482)
  * debian/control.in:
    - Build-Depends on libavahi-glib-dev, libavahi-client-dev, libgphoto2-2-dev,
      libgnome-keyring-dev and updated libhal, libglib requirement
    - update the description
  * debian/gvfs-backends.install, debian/gvfs-bin.install:
    - updated to the new version changes
  * debian/patches/80_lists_audio_and_blank_cds.patch,
    debian/patches/81_correct_audio_cds_icon_naming.patch,
    debian/patches/90_from_svn_dont_list_nfs_mounts.patch,
    debian/patches/90_from_svn_fix_fileselector_crash.patch,
    debian/patches/90_from_svn_limit_smb_reads.patch:
    - those are fixed in the new version

 -- Sebastien Bacher <email address hidden> Mon, 25 Feb 2008 23:05:47 +0100

with one particular sftp server I still get this message even in gvfs 0.1.11

gvfs-mount sftp://xxx.xx.xx
Enter password
User [christian]: xxxx
Password:
Error mounting location: Timed out when logging in

similar message from "connect to server" in the gui

I can connect to that server using sftp.

I still get the same errors with 0.2.3, timeouts with either gvfs-mount or the connect to server command.

I have this problem with gvfs 0.2.4-0ubuntu1. (also with gvfs mount and nautilus)

I have this problem with GVFS 0.2.5-0ubuntu2 in both gvfs-mount and Nautilus. It seems to be due to an offending RSA key, as shown below:

When I logged in through the terminal with SSH, I got the following message:

Warning: the RSA host key for 'XXXXXXXXX' differs from the key for the IP address 'XXXXXXXXX'
Offending key for IP in /home/XXXXXXXXX/.ssh/known_hosts:8
Matching host key in /home/XXXXXXXXX/.ssh/known_hosts:25
Are you sure you want to continue connecting (yes/no)? yes
(everything went fine after this)

To make GVFS work all I had to do was delete line 8 in my known_hosts file.

In this situation, Nautilus/gvfs-mount should pop-up/print-out a message to the user, similar to what SSH does.

Since enough people seem to still have this problem, shouldn't this be changed back from "fix released" to "confirmed" ?

Changing back to *Fix released*

A fix was released upstream 4 days ago. I haven't tested it yet, though.
http://bugzilla.gnome.org/show_bug.cgi?id=545445

I believe the other fix mentioned by Oliver Gerlich (https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/188790/comments/7) only applies to "connecting to the server for the first time". That is, it just shows a "Add fingerprint to database?"-type dialog. That's why it doesn't solve the "offending key" issues.