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.
DescriptionDalibor Pospíšil
2020-01-16 19:12:18 UTC
Description of problem:
There are passwords which work (password, PaSSword) and which does not (password123, password?) specifically on s390x and x86_64 only. Ppc64le and aarch64 are not affected.
Version-Release number of selected component (if applicable):
pam-1.3.1-8.el8
How reproducible:
100%
Steps to Reproduce:
1. use linked test
There seems to be a problem with crypt_r() API in s390x and x86_64 architectures with passwords longer than 8 characters.
As an example: password "password123" would be encrypted as "ZZKRwXSu3tt8s" with DES, but debugging the code I found that crypt_r() encrypted it as "ZZKRwXSu3tt8sjZuBF/FYdyE", which contains the expected result plus other characters. Something similar happens with "password?", which also has more than 8 characters. On the other hand "password" or "PaSSword", which are 8 characters long, work correctly.
Basically this means crypt_r() behaves like it was a "bigcrypt" implementation instead of the pure DES crypt. What's even more weird is that this happens only on some architectures.
Thank you! I've just seen that Tomas Mraz has already reviewed it, so if you don't mind I leave you in his hands. He has a deeper knowledge of the package and he's one of the maintainers of the project.
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 (pam bug fix and enhancement update), 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://access.redhat.com/errata/RHBA-2021:4395