Red Hat Enterprise Linux OpenSSH Client Cryptographic Module
Red Hat Enterprise Linux OpenSSH Client Cryptographic Module, from Red Hat®, Inc., holds FIPS 140-2 certificate #2633 at overall level 1. The validation is historical: agencies may keep the module in existing systems but not buy it new. Below are its validation history, algorithm certificates and security policy, drawn from the NIST CMVP entry.
Caveat: When operated in FIPS mode with module Red Hat Enterprise Linux 7.1 OpenSSL Module validated to FIPS 140-2 under Cert. #2441 operating in FIPS mode. The module generates cryptographic keys whose strengths are modified by available entropy
Certificate
| Certificate number | 2633 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Software |
| Embodiment | Multi-Chip Stand Alone |
| Vendor | Red Hat®, Inc. · website |
| Software versions | 4.0 |
Module description
Quoted from the NIST CMVP entry for this certificate.
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 7.1. Its cryptographic mechanisms use the OpenSSL library in FIPS 140-2 mode.
Security level exceptions
- Physical Security: N/A
- Mitigation of Other Attacks: N/A
Approved algorithms (1)
Tested configurations
- Red Hat Enterprise Linux 7.1 running on IBM Power8 Little Endian 8286-41A
- Red Hat Enterprise Linux 7.1 running on IBM z13 with CP Assist for Cryptographic Functions (single-user mode)
- Red Hat Enterprise Linux 7.1 running on ProLiant DL380p Gen8 with PAA
- Red Hat Enterprise Linux 7.1 running on ProLiant DL380p Gen8 without PAA
Validation history
| Date | Type | Lab |
|---|---|---|
| 2016-05-12 | Initial | atsec information security corporation |
| 2016-06-17 | Update | 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: 2016-05-12, 2016-06-17