gvfs is not using the gnome-keyring agent for ssh connections

Bug #345496 reported by Jamin W. Collins
44
This bug affects 4 people
Affects Status Importance Assigned to Milestone
GNOME Keyring
Fix Released
Medium
gnome-keyring (Ubuntu)
Fix Released
Low
Ubuntu Desktop Bugs
Nominated for Jaunty by Jamin W. Collins
gvfs (Ubuntu)
Fix Released
Low
Ubuntu Desktop Bugs
Nominated for Jaunty by Jamin W. Collins

Bug Description

Binary package hint: nautilus

For some reason, nautilus is no longer using keys cached by the ssh agent but instead prompting for the already cached key's passphrase on each connection attempt. Providing the same passphrase for the already cached private key completes the connection.

In the past (8.10 and previous) nautilus would utilize existing cached keys for ssh/sftp connections.

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/nautilus
NonfreeKernelModules: nvidia
Package: nautilus 1:2.26.0-0ubuntu1
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
Uname: Linux 2.6.28-11-generic x86_64

Revision history for this message
Jamin W. Collins (jcollins) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report, confirming as a gvfs issue, could be due to the start order

Changed in nautilus (Ubuntu):
assignee: nobody → desktop-bugs
importance: Undecided → Low
status: New → Confirmed
summary: - natilus not using agent for ssh connections
+ gvfs is not using the gnome-keyring agent for ssh connections
Changed in gvfs (Ubuntu):
milestone: none → ubuntu-9.04
Revision history for this message
Thomas (t.c) wrote :

I have the same problem with 8.10, hope it can be fixed...

Revision history for this message
Mark Lynch (mark-lynchconsulting) wrote :

Additional vote for this bug.

We use ssh keys exclusively to connect to servers - i.e. password access is disabled in the SSH server for additional security. This bug is preventing any access to sftp/ssh servers via nautilus which I was getting very used to on 8.10 - now running 9.04 and it has been a problem for a while.

Is there any additional log files that I can attach to help with this? I can't find if/where gvfs writing any output to.

Revision history for this message
Sebastien Bacher (seb128) wrote :

there is no need to "vote" for bugs, that's not really a gvfs bug but rather an issue on how the dbus session bus is started it doesn't get the correst ssh environment set

Revision history for this message
Sebastien Bacher (seb128) wrote :

if you restart gvfsd after the session start that should be working

Revision history for this message
Mark Lynch (mark-lynchconsulting) wrote :

Hi Sebastien, Thanks for the clue re restarting gvfsd. I had to look up how to do it and I think this is the right way - please correct me if I'm wrong.

/usr/lib/gvfs/gvfsd -r

Works perfectly now. Would be great to get this fixed permanently.

Revision history for this message
Jamin W. Collins (jcollins) wrote :

I've added Mark's command to my session startup and I'm happy to say that nautilus is once again using the ssh agent for connections. Thank you.

affects: gvfs (Ubuntu) → gnome-keyring (Ubuntu)
Changed in gnome-keyring (Ubuntu):
status: Confirmed → Triaged
Changed in gnome-keyring:
status: Unknown → New
Changed in gnome-keyring:
status: New → Confirmed
Revision history for this message
Jamin W. Collins (jcollins) wrote :

Any chance of seeing this corrected for the release?

Revision history for this message
Sebastien Bacher (seb128) wrote :

upstream says that's fixed in svn now and will be 2.26.1 which will be in jaunty but you might want to give a try to svn to confirm that's working

Revision history for this message
Sebastien Bacher (seb128) wrote :

will be fixed with the 2.16.1 update once accepted today

Changed in gnome-keyring (Ubuntu):
status: Triaged → Fix Committed
Changed in gvfs (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance: Undecided → Low
status: New → Triaged
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gnome-keyring - 2.26.1-0ubuntu1

---------------
gnome-keyring (2.26.1-0ubuntu1) jaunty; urgency=low

  * New upstream version:
    - Fix many problems with the new secure memory allocator.
      (lp: #328167, #338158, #352269)
    - DBus now automatically starts the gnome-keyring service properly.
      (lp: #344444)
    - When auto activating the gnome-keyring DBus service, check for an
      already running daemon.
    - Don't print critical warnings when registering with DBus fails.
    - Bump glib dependency.
    - Add DBus method for getting the gnome-keyring environment variables.
      (lp: #345496)
    - Fix crash when prompting to unlock the keyring.
    - Initialize daemon with LOGNAME and USERNAME environment variables.
    - Build fixes
  * debian/patches/03_secure-mem_crash.patch:
    - the change is in the new version

 -- Sebastien Bacher <email address hidden> Mon, 13 Apr 2009 11:00:28 +0200

Changed in gnome-keyring (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

---------------
gvfs (1.2.2-0ubuntu1) jaunty; urgency=low

  * New upstream version:
    - ftp: Fix error handling in some cases
    - proxy monitor: Fix warning spew
  * debian/patches/91_svn_change_ssh_use_gnome_keyring.patch:
    - svn change to get the ssh backend to use gnome-keyring (lp: #345496)

 -- Sebastien Bacher <email address hidden> Mon, 13 Apr 2009 21:04:33 +0200

Changed in gvfs (Ubuntu):
status: Triaged → Fix Released
Changed in gnome-keyring:
status: Confirmed → Fix Released
Revision history for this message
Andrei Dziahel (develop7) wrote :

Hi everyone.

I've just hit this bug on my Karmic installation. This guy (http://ubuntuforums.org/showthread.php?t=1354029) as well.

I think this bug should be reopened.

If I could provide any info which could shed light on this issue, please inform me.

TIA.

Changed in gvfs (Ubuntu):
status: Fix Released → Confirmed
Changed in gnome-keyring (Ubuntu):
status: Fix Released → Confirmed
Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Please don't reopen bugs that are already fixed - you should report a new one instead. This specific bug is known to be fixed, so if you're experiencing an issue with similar symptoms, then it's a different bug

Changed in gnome-keyring (Ubuntu):
status: Confirmed → Fix Released
Changed in gvfs (Ubuntu):
status: Confirmed → Fix Released
Changed in gnome-keyring:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.