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.
DescriptionChance Callahan
2023-08-02 16:43:36 UTC
Description of problem:
A customer came to us with the following bug: on RHEL 6, if they told pam_pwhistory to remember the last five passwords, it would remember them. If they give the same instruction to the PAM module on RHEL 7.5, it remembers the last six passwords instead of five.
Version-Release number of selected component (if applicable):
* pam-1.1.8-22.el7.x86_64
How reproducible:
I did not personally reproduce it, but the customer has indicated it's affecting multiple systems.
Steps to Reproduce:
1. Enable pam_pwhistory
2. Set it to remember the last five passwords.
3. Change password five times.
4. Try using the original password again.
Actual results:
(per customer) pam_pwhistory remembers the last six passwords instead of the last five.
Expected results:
pam_pwhistory only recalls the last five passwords.
I tried reproducing the error in RHEL7 and it's working as expected. So, I'm wondering, maybe there was a problem in RHEL6 and it was fixed for RHEL7.
Steps:
1- Set 6 different passwords for a user.
2- Change the password to the second one -> Fails because we are reusing a password.
3- Change the password to the first one -> Succeeds.
Can you provide any additional information?
Hi Chance,
Can you help us with the reproducer? As Iker mentioned, he was using the same pam version as stated in the description, but it worked as expected.
Kindly
Comment 7RHEL Program Management
2023-09-14 08:30:11 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 8RHEL Program Management
2023-09-14 08:43:50 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.