Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionHuzaifa S. Sidhpurwala
2010-05-26 10:17:08 UTC
1. Install RHEL6
2. Create a users and set the password to be changed on the first time using
/usr/bin/chage -d 0 ${user}
3. Login and change the password.
4. gnome-keyring still unlocks with the old password.
[huzaifas@huzaifas ~]$ rpm -q gnome-keyring
gnome-keyring-2.28.2-5.el6.x86_64
[huzaifas@huzaifas ~]$ uname -r
2.6.32-25.el6.x86_64
Comment 4Christopher Aillon
2010-06-05 00:01:54 UTC
Hm, without really knowing much about the code, my guess this is because chage is writing as root to /etc/shadow.
From http://live.gnome.org/GnomeKeyring/Pam
# If root changes the password, or /etc/shadow is directly edited [...],
the 'login' keyring cannot be updated.
Which pam stack is used for changing the password at login in this situation ?
It needs to have the pam-gnome-keyring module in it.
It may be that we need to add
-password optional‣‧‧‧pam_gnome_keyring.so use_authtok
to password-auth (or maybe just to gdm-password) ?
Comment 6Ray Strode [halfline]
2010-06-07 14:33:30 UTC
yup sounds right.
My gut says we want this in password-auth and system-auth not gdm-password because we want to catch people who happen to log into a tty first, as well.
Moving to authconfig. I'll trust Tomas's judgement on this one though. If he thinks this belongs in gdm I'll fix it there.
Both choices have its pros and cons:
Putting it into password-auth and system-auth means that it will be called for all pamified services that handle the expired password change. However I strongly suspect that for most of them it will not work due to the missing rules in the SELinux policy and it will just generate AVCs. So I am not sure this is appropriate change for RHEL-6.
If the module is put just to the gdm configuration files it of course means that it will not be called if someone logs in on the text console. On the other hand as the gnome-keyring is supposed to be used especially in the Gnome GUI, I do not think this would be too serious defect.
Comment 8Ray Strode [halfline]
2010-06-07 22:04:15 UTC
fair enough. changing in gdm seems like the conservative choice given the selinux implications.
Taking back previous verification
gnome-keyring works with old password:
gdm-2.30.4-2.el6.x86_64
Comment 14Ray Strode [halfline]
2010-07-08 13:44:19 UTC
If gnome-keyring works with the old password AND the new password, that's not a problem in this bug fix. That means there may be an additional bug in gnome-keyring which should be filed, investigated and tracked separately.
Hi Ray,
sounds reasonable to me. Moving back to verified.
Verified on:
gdm-2.30.4-2.el6
gdm-2.30.4-5.el6
Comment 16releng-rhel@redhat.com
2010-11-10 20:27:43 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.
1. Install RHEL6 2. Create a users and set the password to be changed on the first time using /usr/bin/chage -d 0 ${user} 3. Login and change the password. 4. gnome-keyring still unlocks with the old password. [huzaifas@huzaifas ~]$ rpm -q gnome-keyring gnome-keyring-2.28.2-5.el6.x86_64 [huzaifas@huzaifas ~]$ uname -r 2.6.32-25.el6.x86_64