Comment 30 for bug 187127

How I got rid of this bug and what it indicates:

Important context:
intrepid, autologin by gdm, WPA key stored by nm in a password-less (unsecure plaintext) default.keyring, which also is the default gnome keyring.

Now, trying to use sshfs with a key authentification, this dialog pups up and I can continue by either entering my local user password or pressing "Deny". This is due to a keyring called login.keyring, which has somehow gotten created. Once it is either unlocked with my password or denied, ssh connection works since I had a key file in the first place.

IIRC, login.keyring is the former default keyring and got changed to default.keyring, but, supposedly, some ssh related part of gnome-keyring still has it hardcoded.

The workaround is - delete the login.keyring, restart session by means of autologin (not entering a password), try connecting (using sshfs with rsa keys), now a window appears asking for a password to create a new login.keyring. Just press enter, it warns about unsafe storage, accept it. Connection gets established and the popup is gone.

What has changed is that the login.keyring is now a plaintext file and contains a string with my public key, same as the wireless WPA key in the default.keyring. Thus, this bug (or feature?) may depend on autologin and/or changed passwords.

Hopefully this helps,
Kind regards,
Matiss