Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 6): Bug 1024825
Description of problem: This issue was observed during the manual test execution of https://bugzilla.redhat.com/show_bug.cgi?id=725281. During execution numerous auth requests are sent to the server in a loop, and atleast 2000 iterations are expected to pass without auth failure or file descriptor leak Version-Release number of selected component (if applicable): sssd-1.9.2-129.el6.x86_64 How reproducible: Always Steps to Reproduce: 1. Download the reproducer program from https://bugzilla.redhat.com/show_bug.cgi?id=725281 2. Compile the test program "check_user2.c" # gcc -lpam -o check_user2 check_user2.c 3. Modify /etc/pam.d/system-auth as follows #%PAM-1.0 # This file is auto-generated. # User changes will be destroyed the next time authconfig is run. auth required pam_env.so auth sufficient pam_unix.so nullok try_first_pass auth requisite pam_succeed_if.so uid >= 500 quiet auth sufficient pam_winbind.so use_first_pass auth required pam_deny.so account required pam_unix.so broken_shadow account sufficient pam_localuser.so account sufficient pam_succeed_if.so uid < 500 quiet account [default=bad success=ok user_unknown=ignore] pam_winbind.so account required pam_permit.so password requisite pam_cracklib.so try_first_pass retry=3 password sufficient pam_unix.so md5 shadow nis nullok try_first_pass use_authtok password sufficient pam_winbind.so use_authtok password required pam_deny.so session optional pam_keyinit.so revoke session required pam_limits.so session [success=1 default=ignore] pam_succeed_if.so service in crond quiet use_uid session required pam_unix.so 3. Run the program # ./check_user2 -s system-auth -n 1030 aduser Actual results: User auth failed at loop 204 with a system error. Expected results: User auth should succeed till 2000 iterations of loop Additional info:
Fields changed
blockedby: => blocking: => changelog: => coverity: => design: => design_review: => 0 feature_milestone: => fedora_test_page: => milestone: NEEDS_TRIAGE => SSSD 1.11.3 review: True => 0 selected: => testsupdated: => 0
Lukas was already looking into the associated bugzilla, so I'm going to assign this ticket to him as well.
owner: somebody => lslebodn
File descriptor leak is in module pam_fprintd.so and not in pam_sss.
I am closing this bug as invalid.
resolution: => invalid status: new => closed
Metadata Update from @dpal: - Issue assigned to lslebodn - Issue set to the milestone: SSSD 1.11.3
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/3181
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.