808bits

Red Hat Enterprise Linux 6.2 OpenSSH Client Cryptographic Module

FIPS 140-2 certificate #1791 · 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. This module contains the embedded module Red Hat Enterprise Linux 6.2 OpenSSL Cryptographic Module validated to FIPS 140-2 under Cert. #1758 operating in FIPS mode. When obtained, installed, and initialized as assumed by the Crypto Officer role and as specified in Section 9.1 of the provided Security Policy. Section 1 of the provided Security Policy specifies the precise RPM file containing this module. The integrity of the RPM is automatically verified during the installation and the Crypto officer shall not install the RPM file 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. The module generates cryptographic keys whose strengths are modified by available entropy.

Certificate

Certificate number1791
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-chip standalone
VendorRed Hat®, Inc. · website
Software versions2.1

Module description

The OpenSSH Client cryptographic module provides the client-side component for an SSH protocol version 2 protected communication channel. OpenSSH is the standard SSH implementation and shipped with RHEL 6.2. Its cryptographic mechanisms use the OpenSSL library in FIPS 140-2 mode.

Approved algorithms

AlgorithmCAVP certificate
AES1887, 1888, 1889, 1893, 1894, 1895
DSA592, 593, 597, 598
HMAC1129, 1130, 1134, 1135
RNG989, 990, 994, 995
RSA964, 965, 969, 970
SHS1658, 1659, 1663, 1664
Triple-DES1226, 1227, 1231, 1232

Other algorithms

RSA (key wrapping; key establishment methodology provides between 112 and 160 bits of encryption strength; non-compliant less than 112 bits of encryption strength); Diffie-Hellman (key agreement; key establishment methodology provides between 112 and 160 bits of encryption strength; non-compliant less than 112 bits of encryption strength)

Tested configurations

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

Validation history

DateTypeLab
2012-08-24Initialatsec information security corporation
2012-10-23Updateatsec 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: 2012-08-24, 2012-10-23

Source documents