Bug 233477 - FIPS 200: Use FIPS 140-2 validated crypto
FIPS 200: Use FIPS 140-2 validated crypto
Status: CLOSED DUPLICATE of bug 444768
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: distribution (Show other bugs)
5.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: RHEL Product and Program Management
Daniel Riek
: FutureFeature
Depends On:
Blocks: 202601 233480
  Show dependency treegraph
 
Reported: 2007-03-22 14:14 EDT by Chris Runge
Modified: 2008-09-25 14:42 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-09-25 14:42:00 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Chris Runge 2007-03-22 14:14:29 EDT
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 14:42:00 EDT
Closing this bug since there is another one for FIPS work.

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

Note You need to log in before you can comment on or make changes to this bug.