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 1198823[details]
strace fail output
Description of problem:
We received an email from a customer with the following:
Host is configured to authenticate using AD via pam_krb5.
Some users were able to authenticate to sudo, others were not.
If a user's entry in /etc/passwd is beyond the 4K byte point, attempts to authenticate into sudo fail after 3 prompts for password. The following entry is
generated in /etc/var/log/secure:
sudo: pam_krb5[61945]: account checks fail for 'uname.EDU<uname.edu>': user disallowed by .k5login file for 'username'
Note: there is no .k5login file in the user account
strace'ing the command determined that when the authentication failed, initially 2 reads were made to the passwd file. The first was 4096 bytes, the second was the remainder of the file. On subsequent reads of passwd, did not read beyond the 4k byte mark. Every user that failed was beyond the the 4k byte point.
Moving the user's passwd entry above the 4k point in the passwd file allows the user to authenticate normally.
Version-Release number of selected component (if applicable):
pam_krb5-2.4.8-4.el7
How reproducible:
Every time
Steps to Reproduce:
1. Create passwd file with enough users to make the file larger than 4K bytes.
2. Give a user at the bottom of the file permissions in /etc/sudoers
3. Execute `sudo -l`
4. After 3 attempts, the command will fail with "bad password" and log message above.
Actual results:
users can't authenticate as sudo
Expected results:
user will authenticate successfully.
Additional info:
Adding "debug" flag to directives in /etc/pam.d/sudo results in a hang of the command.
See attached strace output for successful and unsuccessful execution.
Created attachment 1198823 [details] strace fail output Description of problem: We received an email from a customer with the following: Host is configured to authenticate using AD via pam_krb5. Some users were able to authenticate to sudo, others were not. If a user's entry in /etc/passwd is beyond the 4K byte point, attempts to authenticate into sudo fail after 3 prompts for password. The following entry is generated in /etc/var/log/secure: sudo: pam_krb5[61945]: account checks fail for 'uname.EDU<uname.edu>': user disallowed by .k5login file for 'username' Note: there is no .k5login file in the user account strace'ing the command determined that when the authentication failed, initially 2 reads were made to the passwd file. The first was 4096 bytes, the second was the remainder of the file. On subsequent reads of passwd, did not read beyond the 4k byte mark. Every user that failed was beyond the the 4k byte point. Moving the user's passwd entry above the 4k point in the passwd file allows the user to authenticate normally. Version-Release number of selected component (if applicable): pam_krb5-2.4.8-4.el7 How reproducible: Every time Steps to Reproduce: 1. Create passwd file with enough users to make the file larger than 4K bytes. 2. Give a user at the bottom of the file permissions in /etc/sudoers 3. Execute `sudo -l` 4. After 3 attempts, the command will fail with "bad password" and log message above. Actual results: users can't authenticate as sudo Expected results: user will authenticate successfully. Additional info: Adding "debug" flag to directives in /etc/pam.d/sudo results in a hang of the command. See attached strace output for successful and unsuccessful execution.