808bits

Red Hat Enterprise Linux 5 Kernel Crypto API Cryptographic Module

FIPS 140-2 certificate #1387 · Red Hat®, Inc. · data as of 2026-08-28
Historical. RNG SP800-131A Revision 1 Transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode. When obtained, installed, and initialized as assumed by the Crypto Officer role and specified in Section 9.1 of the provided Security Policy. This module contains the embedded module Network Security Services (NSS) Cryptographic Module validated to FIPS 140-2 under Cert. #815 (Approved algorithms retested on listed operating environment) operating in FIPS mode. 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 number1387
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-chip standalone
VendorRed Hat®, Inc. · website
Software versions1.0

Module description

The Linux kernel Crypto API implemented in Red Hat Enterprise Linux 5 provides services operating inside the Linux kernel with various ciphers, message digests and an approved random number generator.

Approved algorithms

AlgorithmCAVP certificate
AES1224
DSA406, 449
HMAC715, 812
RNG679
SHS1125
Triple-DES882

Other algorithms

DES, Triple-DES (CTR mode; non-compliant)

Tested configurations

  • Red Hat Enterprise Linux 5.4 (single-user mode)

Validation history

DateTypeLab
2010-08-12Initialatsec 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: 2010-08-12

Source documents