Bug 1987974

Summary: FIPS policy allows SHA3-224 but not SHA2-224
Product: Red Hat Enterprise Linux 9 Reporter: Alexander Sosedkin <asosedki>
Component: crypto-policiesAssignee: Alexander Sosedkin <asosedki>
Status: CLOSED WONTFIX QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 9.0CC: pvrabec
Target Milestone: beta   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-07-29 17:28:54 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:

Description Alexander Sosedkin 2021-07-29 17:27:58 UTC 
Throughout all the revisions of crypto-policies that ship a FIPS policy,
SHA2-224 has been allowed, while SHA3-224 hasn't been.
FIPS 140-2 allows both [1].

We've decided to keep behavior the same moving forward, citing the following considerations specifically:
1) SHA3-224 is a relatively impractical and unpopular choice of a hash function.
2) We don't believe disabling SHA2-224 just for consistency outweights the compatibility considerations.
3) Since custom crypto policies support has been added, the selection is controllable by the administrator.
4) We don't see customers complaining about SHA3-224 being disabled in FIPS.
   We might reevaluate this decision for future releases if this changes. 

[1] https://csrc.nist.gov/csrc/media/publications/fips/140/2/final/documents/fips1402annexa.pdf