gvfs is not using the gnome-keyring agent for ssh connections
Bug #345496 reported by
Jamin W. Collins
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 | ||
gvfs (Ubuntu) |
Fix Released
|
Low
|
Ubuntu Desktop Bugs | ||
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
NonfreeKernelMo
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
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 |
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 |
Changed in gnome-keyring: | |
status: | Confirmed → Fix Released |
Changed in gnome-keyring: | |
importance: | Unknown → Medium |
To post a comment you must log in.
Thank you for your bug report, confirming as a gvfs issue, could be due to the start order