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 516097 - ssh always asks to unlock private key with no password set
ssh always asks to unlock private key with no password set
Status: RESOLVED NOTABUG
Product: gnome-keyring
Classification: Core
Component: general
2.21.x
Other Linux
: Normal normal
: ---
Assigned To: GNOME keyring maintainer(s)
GNOME keyring maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2008-02-12 20:27 UTC by Sebastien Bacher
Modified: 2009-03-03 04:25 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Sebastien Bacher 2008-02-12 20:27:07 UTC 
The bug has been opened on https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/187127

"My ssh keys have no password, but yet on Hardy, the Gnome key ring manager
is always asking me to unlock them!

The unlock dialog can't handle an empty blank password,
and checking the "always unlock when I login" has no effect either.

So after the upgrade to Hardy, my machine can't do ssh/slogin to any other
machine. This is a showstopper since this machine is used for development
and needs to push/pull from secure git repositories.

Closing the dialog box allows the ssh to work (one time), but doesn't work
well in automated scripts! Doing same thing from console (text mode)
works without dialog."
Comment 1 Stef Walter 2008-02-14 23:31:32 UTC 
Could you paste the first line of the SSH key file into this bug report?
Comment 2 Sebastien Bacher 2008-09-03 20:42:38 UTC 
ubuntu bug reply:

"-----BEGIN DSA PRIVATE KEY-----

What did you expect?"
Comment 3 Stef Walter 2008-09-13 15:36:03 UTC 
I would love to fix this. I really can't duplicate this. I have a DSA key unencrypted without a password and it works correctly. 

Are there messages from gnome-keyring-daemon in your auth.log?
Comment 4 mlsorensen 2008-09-18 17:45:39 UTC 
Same issue. authorized_keys login succeeds after closing the popups

Sep 18 11:40:45 mlsorensen-lnx gnome-keyring-daemon[5780]: couldn't find or load public key for private key
Sep 18 11:42:03 mlsorensen-lnx gnome-keyring-daemon[5780]: couldn't find or load public key for private key
Sep 18 11:42:51 mlsorensen-lnx gnome-keyring-daemon[5780]: couldn't find or load public key for private key
Comment 5 Stef Walter 2009-03-03 04:25:38 UTC 
Those messages seem to indicate that the *.pub key is missing. Is that the case. For each private SSH key there should be a public one in the same directory. For example

Private key:   id_rsa
Public key:    id_rsa.pub