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.
DescriptionStanislav Zidek
2014-08-14 08:49:01 UTC
Description of problem:
pam_fail_delay() function documentation states that it will delay execution by given time +- 25%, but it actually waits for given time +- 50%
Version-Release number of selected component (if applicable):
pam-1.1.1-17.el6.x86_64
How reproducible:
always
Steps to Reproduce:
1. set pam_fail_delay()
2. measure time of failed pam_authenticate()
Actual results:
When delay was set to 20s, I got this distribution:
3 11s
20 12s
24 13s
51 14s
140 15s
197 16s
190 17s
166 18s
197 19s
296 20s
417 21s
445 22s
350 23s
208 24s
93 25s
59 26s
51 27s
41 28s
10 29s
1 30s
Expected results:
Either the times to be between 15 and 25 seconds, or adjust documentation accordingly.
Additional info:
I already reported an upstrem bug after consulting with tmraz - https://fedorahosted.org/linux-pam/ticket/36
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2016-0901.html
Description of problem: pam_fail_delay() function documentation states that it will delay execution by given time +- 25%, but it actually waits for given time +- 50% Version-Release number of selected component (if applicable): pam-1.1.1-17.el6.x86_64 How reproducible: always Steps to Reproduce: 1. set pam_fail_delay() 2. measure time of failed pam_authenticate() Actual results: When delay was set to 20s, I got this distribution: 3 11s 20 12s 24 13s 51 14s 140 15s 197 16s 190 17s 166 18s 197 19s 296 20s 417 21s 445 22s 350 23s 208 24s 93 25s 59 26s 51 27s 41 28s 10 29s 1 30s Expected results: Either the times to be between 15 and 25 seconds, or adjust documentation accordingly. Additional info: I already reported an upstrem bug after consulting with tmraz - https://fedorahosted.org/linux-pam/ticket/36