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.
DescriptionNalin Dahyabhai
2013-11-19 15:56:49 UTC
Description of problem:
When I log in using gdm and gnome-shell and then lock the screen, on unlock gdm is calling pam_setcred with the wrong flag (it uses PAM_ESTABLISH_CRED instead of PAM_REINITIALIZE_CRED). If a module in the PAM configuration is going to do different things based on that flag, the wrong thing can happen.
Version-Release number of selected component (if applicable):
gdm-3.8.4-7.el7.x86_64
gnome-shell-3.8.4-14.el7.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Use authconfig to enable NIS and Kerberos, which should force the system to use pam_krb5.
2. Add this to your /etc/krb5.conf's [appdefaults] section:
pam = {
debug = true
}
3. Log in, lock the screen, and unlock it.
Actual results:
/var/log/secure will note something like:
Nov 19 10:38:56 blah gdm-password]: pam_krb5[2258]: pam_setcred(PAM_ESTABLISH_CRED) returning 0 (Success)
Expected results:
/var/log/secure will note something like:
Nov 19 10:38:56 blah gdm-password]: pam_krb5[2258]: pam_setcred(PAM_REINITIALIZE_CRED) returning 0 (Success)
Additional info:
While this appears to work when the default ccache is configured to a location that doesn't change (so that when the module attempts to create a new ccache, it happens to use the same location that was also used when the user logged in), if you configure it to use a per-session location (say, FILE:/tmp/krb5cc_%{uid}_XXXXXX), it'll create a new ccache every time the user unlocks their screen, and the ccache that the user is actually using won't be updated.
Comment 2Ray Strode [halfline]
2013-11-20 19:34:10 UTC
Any chance you could make the binary rpms available? I'd like to verify that this also fixes the renewal of AFS tokens when the screen is unlocked - right now, pam_krb5 does acquire a fresh token but I think it ends up in a different PAG.
I'd patch and build myself, but 7.0 beta doesn't ship many of the build requirements.
Thanks.
Comment 6Ray Strode [halfline]
2014-01-06 16:31:10 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.
Description of problem: When I log in using gdm and gnome-shell and then lock the screen, on unlock gdm is calling pam_setcred with the wrong flag (it uses PAM_ESTABLISH_CRED instead of PAM_REINITIALIZE_CRED). If a module in the PAM configuration is going to do different things based on that flag, the wrong thing can happen. Version-Release number of selected component (if applicable): gdm-3.8.4-7.el7.x86_64 gnome-shell-3.8.4-14.el7.x86_64 How reproducible: Always Steps to Reproduce: 1. Use authconfig to enable NIS and Kerberos, which should force the system to use pam_krb5. 2. Add this to your /etc/krb5.conf's [appdefaults] section: pam = { debug = true } 3. Log in, lock the screen, and unlock it. Actual results: /var/log/secure will note something like: Nov 19 10:38:56 blah gdm-password]: pam_krb5[2258]: pam_setcred(PAM_ESTABLISH_CRED) returning 0 (Success) Expected results: /var/log/secure will note something like: Nov 19 10:38:56 blah gdm-password]: pam_krb5[2258]: pam_setcred(PAM_REINITIALIZE_CRED) returning 0 (Success) Additional info: While this appears to work when the default ccache is configured to a location that doesn't change (so that when the module attempts to create a new ccache, it happens to use the same location that was also used when the user logged in), if you configure it to use a per-session location (say, FILE:/tmp/krb5cc_%{uid}_XXXXXX), it'll create a new ccache every time the user unlocks their screen, and the ccache that the user is actually using won't be updated.