Red Hat Enterprise Linux 6.2 Kernel Crypto API Cryptographic Module
Caveat: When operated in FIPS mode with Network Security Services (NSS) Cryptographic Module validated to FIPS 140-2 under Cert. #1837, Section 1 of the provided Security Policy specifies the precise RPM files containing this module. The integrity of the RPMs is automatically verified during the installation and the Crypto officer shall not install the RPM files if the RPM tool indicates an integrity error. Any deviation from the specified verification, installation and initialization procedures will result in a non FIPS 140-2 compliant module
Certificate
| Certificate number | 1901 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Software |
| Embodiment | Multi-chip standalone |
| Vendor | Red Hat®, Inc. · website |
| Software versions | 2.0 |
Module description
The Linux kernel Crypto API implemented in Red Hat Enterprise Linux 6.2 provides services operating inside the Linux kernel with various ciphers, message digests and an approved random number generator.
Approved algorithms
| Algorithm | CAVP certificate |
|---|---|
| AES | 1968, 1969, 1970, 1971, 1972 |
| DSA | 628, 629, 634, 635 |
| HMAC | 1187, 1188, 1199, 1200 |
| RNG | 1033, 1034, 1035, 1036, 1037 |
| SHS | 1725, 1726 |
| Triple-DES | 1278, 1279 |
Other algorithms
DES; Triple-DES (CTR; non-compliant); AES (192 bits, XTS; non-compliant); RNG (X9.31 with stdrng or ansi_cprng; non-compliant)
Tested configurations
- Red Hat Enterprise Linux 6.2 with PAA running on IBM HS22
- Red Hat Enterprise Linux 6.2 without PAA running on HP ProLiant DL585
- Red Hat Enterprise Linux 6.2 without PAA running on IBM HS22 (single-user mode)
Validation history
| Date | Type | Lab |
|---|---|---|
| 2013-02-21 | Initial | atsec information security corporation |
Status timeline
As observed by this tracker's snapshots. NIST publishes no dates for list moves; observation began 2026-08-21, so earlier changes carry no date.
- 2026-08-21: first observed by this tracker, status historical
- Validation dates on record: 2013-02-21