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.
Created attachment 462391[details]
Proposed patch
pam_ssh_agent_auth sets euid temporarily to the user during the connect to the ssh-agent socket to avoid possible race conditions. However if the connect fails for example if the ssh-agent is not running it will fail to restore the original euid. This causes following modules in the PAM stack to fail.
Testing instructions:
Add
auth sufficient pam_ssh_agent_auth.so file=~/.ssh/authorized_keys
to the /etc/pam.d/su.
Run
'ssh-agent -a .ssh-agent-socket'
as user. Then kill the ssh-agent process. Verify that the stale unix socket ~/.ssh-agent-socket is still present. Try to su to root - it asks for password but it fails even if you supply correct root password.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHBA-2011-0598.html
Created attachment 462391 [details] Proposed patch pam_ssh_agent_auth sets euid temporarily to the user during the connect to the ssh-agent socket to avoid possible race conditions. However if the connect fails for example if the ssh-agent is not running it will fail to restore the original euid. This causes following modules in the PAM stack to fail. Testing instructions: Add auth sufficient pam_ssh_agent_auth.so file=~/.ssh/authorized_keys to the /etc/pam.d/su. Run 'ssh-agent -a .ssh-agent-socket' as user. Then kill the ssh-agent process. Verify that the stale unix socket ~/.ssh-agent-socket is still present. Try to su to root - it asks for password but it fails even if you supply correct root password.