Bug 1486889

Summary:	htpasswd: support SHA-x passwords for FIPS compatibility
Product:	Red Hat Enterprise Linux 7	Reporter:	Robert Bost <rbost>
Component:	httpd	Assignee:	Luboš Uhliarik <luhliari>
Status:	CLOSED ERRATA	QA Contact:	Maryna Nalbandian <mnalband>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	7.4	CC:	bgollahe, bnater, cshereme, jmalde, jorton, kwalker, luhliari, mskinner, omoris, rbost, syangsao, tmraz
Target Milestone:	rc	Keywords:	FutureFeature, Reopened, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	httpd-2.4.6-92.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1725031 (view as bug list)		Environment:
Last Closed:	2020-03-31 20:03:28 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1716962

Description Robert Bost 2017-08-30 17:34:02 UTC

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.

Comment 13 Robert Bost 2018-03-28 20:24:22 UTC

Setting needinfo

Comment 16 Tomas Mraz 2018-04-05 13:37:51 UTC

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.

Comment 20 Tomas Mraz 2018-04-06 06:50:24 UTC

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.

Comment 25 Tomas Mraz 2018-04-23 07:46:16 UTC

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.

Comment 34 Joe Orton 2019-06-21 16:21:45 UTC

Submitted for review upstream, with "htpasswd -2" and "htpasswd -5" selecting SHA-256/512 respectively.

http://svn.apache.org/viewvc?view=revision&revision=1861793

Comment 41 errata-xmlrpc 2020-03-31 20:03:28 UTC

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