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.
Description of problem:
# cat /proc/sys/crypto/fips_enabled
1
# htpasswd -b -d -c /tmp/foobar user topsecret
htpasswd: crypt() failed: Operation not permitted
Version-Release number of selected component (if applicable): httpd-2.4.6-67.el7_4.2.x86_64
How reproducible: Always
Actual results: "Operation not permitted" when FIPS mode is enabled. Non-FIPS mode works perfect.
Expected results: I would expect an encryption method flag on htpasswd.
Additional info: Workaround is to use bcrypt or some other flag on htpasswd that doesn't call into crypt(), however, these bypass FIPS checks.
The password hashing is not really covered by FIPS requirements unless the password hash leaves the physical boundary of the FIPS module (the computer). I.E. there is no need for it to use FIPS compliant crypto.
However if there is a scenario where the password hash leaves the physical boundary then the password hashing must use a compliant algorithm - whether the SHA256 or SHA512 glibc password hash is that is somewhat debatable. AFAIK the only password based algorithm specified by NIST is PBKDF2 which could be used as password hashing algorithm however I do not know of any such use of PBKDF2.
The ansible installer case is almost completely unrelated. The only connection is that it also creates password hash for httpd but the code used for that is different (coming from python passlib).
So this should be reported as a separate bug.
The ansible installer should either default to a different password hashing algorithm - either use SHA1 or bcrypt (if SHA256 and SHA512 password hashes are not supported by Apache).
Or the python-passlib could pass the override flag to the python hash function so it allows non-security-relevant use of MD5 when creating the hash.
To add more information to the comment #16 - there might be customers that have more strict requirements than what is mandated by FIPS. They might require at least using FIPS approved hash as the underlying crypto primitive which is the password hash based on.
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://access.redhat.com/errata/RHSA-2020:1121