After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 622282 - Doesn't work in SSH session with X forwarding
Doesn't work in SSH session with X forwarding
Status: RESOLVED NOTABUG
Product: seahorse
Classification: Applications
Component: Daemon
unspecified
Other Linux
: High enhancement
: 2.26.0
Assigned To: Seahorse Maintainer
Seahorse Maintainer
Depends on:
Blocks:
 
 
Reported: 2010-06-21 11:42 UTC by Victor Engmark
Modified: 2010-10-19 02:22 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Victor Engmark 2010-06-21 11:42:22 UTC
[Also reported at https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/596567]

I've got identical id_rsa and id_rsa.pub files on two computers (both were restarted after installing the certificate). When trying to do something that requires the key on the machine I'm sitting at, I get a pop-up which asks for the password and caches the key afterwards. Then I try to do the same on the other machine, after `ssh -X`, but it keeps asking for the passphrase, and there's no pop-up. Example session:

laptop:~/foo$ git pull
[window pops up, I fill in the passphrase and click OK]
[git pull output]
laptop:~/foo$ cd ~/bar
laptop:~/bar$ git pull
[git pull output]
laptop:~/foo$ ssh -X desktop
desktop:~$ cd foo
desktop:~/foo$ git pull
Enter passphrase for key '/home/jdoe/.ssh/id_rsa':
desktop:~/foo$ cd ~/bar
desktop:~/bar$ git pull
Enter passphrase for key '/home/jdoe/.ssh/id_rsa':

The first time I do `git pull` on desktop, it should pop up a dialog to request the passphrase, and when I do the last `git pull` it shouldn't ask for the passphrase at all.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: seahorse 2.30.0-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
Architecture: i386
Date: Sun Jun 20 15:37:24 2010
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Release i386 (20100429.4)
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: seahorse
Comment 1 Stef Walter 2010-09-11 23:49:15 UTC
It seems to me that gnome-keyring-daemon crashed between the first successful 'git pull' and the last ones. Could you provide a stack trace of the crash?

Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 Victor Engmark 2010-09-25 19:04:42 UTC
I didn't get any message about a crash, but I suspect the issue is different: Seahorse is not started when logging in via ssh -X. Changing to "enhancement" since I guess it's more of an issue of SSH working with Seahorse when possible.
Comment 3 Stef Walter 2010-10-19 02:22:30 UTC
You need to use ForwardAgent in your laptop ~/.ssh/config  

See:

man ssh_config