libpam-gnome-keyring only uses keyrings with 'login' name

Bug #608480 reported by Iuri Diniz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
GNOME Keyring
Won't Fix
Low
gnome-keyring (Ubuntu)
Triaged
Low
Unassigned

Bug Description

Binary package hint: libpam-gnome-keyring

Hello folks, on lucid 10.04 with the latest updates, pam_gnome_keyring.so only unlock the keyring using the password provided if the keyring has 'login' name

/var/log/auth.log
Jul 21 19:13:14 folha gnome-keyring-daemon[1077]: Failed to unlock login on startup

How to reproduce:
create a new keyring using seahorse, set it as default, move some passwords to it (wifi password per example);
[ or you can rename it via 'mv $HOME/.gnome2/keyrings/login.keyring $HOME/.gnome2/keyrings/default.keyring' and alter $HOME/.gnome2/keyrings/default]

Possible solutions:
1) pam-gnome-keyring may honor $HOME/.gnome2/keyrings/default; or
2) pam-gnome-keyring must unlock each keyrings with the provided password

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

Thank you for your bug report. The issue is an upstream one and it would be nice if somebody having it could send the bug the to the people writting the software (https://wiki.ubuntu.com/Bugs/Upstream/GNOME)

Changed in gnome-keyring (Ubuntu):
importance: Undecided → Low
Changed in gnome-keyring:
status: Unknown → New
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for sending the bug upstream now

Changed in gnome-keyring (Ubuntu):
status: New → Triaged
Changed in gnome-keyring:
importance: Unknown → Low
Changed in gnome-keyring:
status: New → Confirmed
Changed in gnome-keyring:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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