Bug 233477

Summary: FIPS 200: Use FIPS 140-2 validated crypto
Product: Red Hat Enterprise Linux 5 Reporter: Chris Runge <crunge>
Component: distributionAssignee: RHEL Program Management <pm-rhel>
Status: CLOSED DUPLICATE QA Contact: Daniel Riek <riek>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.0CC: sgrubb, tao
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-09-25 18:42:00 UTC Type: ---
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: 202601, 233480    

Description Chris Runge 2007-03-22 18:14:29 UTC 
Requirement for FIPS 200

NIST 800-53
SC-13
Use of validated cryptography

"When cryptography is employed within the information system, the system
performs all cryptographic operations (including key generation) using FIPS
140-2 validated cryptographic modules operating in approved modes of operation".

See http://csrc.nist.gov/publications/nistpubs/800-53/SP800-53.pdf for more
information.

NSS is going through FIPS 140-2 validation; we need to ensure the version of NSS
in the distribution matches the validated version.

More difficult is going to be tracking down the other crypto and coming up with
a plan to consolidate and/or validate it. OpenSSL has been through the process
but there are problems with the currently validated version that prohibit us
from shipping it.

I can arrange a conversation with OSSI who has sponsored the FIPS 140-2
evaluation for OpenSSL to discuss synergies.
Comment 2 Steve Grubb 2008-09-25 18:42:00 UTC 
Closing this bug since there is another one for FIPS work.

*** This bug has been marked as a duplicate of bug 444768 ***