Red Hat Enterprise Linux 6.6 OpenSSH Server Cryptographic Module
Red Hat Enterprise Linux 6.6 OpenSSH Server Cryptographic Module, from Red Hat®, Inc., holds FIPS 140-2 certificate #2446 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 6.6 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 | 2446 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Software |
| Embodiment | Multi-chip standalone |
| Vendor | Red Hat®, Inc. · website |
| Software versions | 3.1 |
Module description
Quoted from the NIST CMVP entry for this certificate.
The OpenSSH Server cryptographic module provides the server-side component for an SSH protocol version 2 protected communication channel. OpenSSH is the standard SSH implementation and shipped with RHEL 6.6. Its cryptographic mechanisms use the OpenSSL library in FIPS 140-2 mode.
Security level exceptions
- Physical Security: N/A
Approved algorithms (1)
Tested configurations
- Red Hat Enterprise Linux 6.6 running on HP ProLiant DL380p Gen8 with PAA
- Red Hat Enterprise Linux 6.6 running on HP ProLiant DL380p Gen8 without PAA
- Red Hat Enterprise Linux 6.6 running on IBM System x3500 M4 with PAA
- Red Hat Enterprise Linux 6.6 running on IBM System x3500 M4 without PAA (single-user mode)
Validation history
| Date | Type | Lab |
|---|---|---|
| 2015-09-16 | Initial | atsec information security corporation |
| 2016-04-28 | 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: 2015-09-16, 2016-04-28