Module Name
Red Hat Enterprise Linux 7 OpenSSH Client Cryptographic Module
Validation Dates
04/12/2021
Caveat
When operated in FIPS mode with module Red Hat Enterprise Linux 7 OpenSSL Module validated to FIPS 140-2 under Cert. #3867 operating in FIPS mode
Security Level Exceptions
- Physical Security: N/A
- Mitigation of Other Attacks: N/A
Embodiment
Multi-Chip Stand Alone
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 7. Its cryptographic mechanisms use the OpenSSL library in FIPS 140-2 mode.
Tested Configuration(s)
- Red Hat Enterprise Linux 7 running on Dell PowerEdge R630 with an Intel(R) Xeon(R) E5 with PAA
- Red Hat Enterprise Linux 7 running on Dell PowerEdge R630 with an Intel(R) Xeon(R) E5 without PAA (single-user mode)
FIPS Algorithms
| AES |
Certs. #C1378, #C1379, #C1380, #C1381, #C1382, #C1383, #C1384, #C1385, #C1386 and #C1419 |
| CVL |
Certs. #C1378, #C1379, #C1385, #C1386 and #C1423 |
| DRBG |
Certs. #C1378, #C1379, #C1380, #C1381, #C1382, #C1383, #C1384, #C1385, #C1386 and #C1419 |
| ECDSA |
Certs. #C1378, #C1379, #C1385 and #C1386 |
| HMAC |
Certs. #C1378, #C1379, #C1380, #C1381, #C1382, #C1383, #C1384, #C1385, #C1386 and #C1419 |
| RSA |
Certs. #C1378, #C1379, #C1385 and #C1386 |
| SHS |
Certs. #C1378, #C1379, #C1380, #C1381, #C1382, #C1383, #C1384, #C1385, #C1386 and #C1419 |
| Triple-DES |
Certs. #C1378, #C1379, #C1385 and #C1386 |
Allowed Algorithms
Diffie-Hellman (CVL Certs. #C1378, #C1379, #C1385 and #C1386 with CVL Cert. #C1423, key agreement; key establishment methodology provides between 112 and 202 bits of encryption strength); EC Diffie-Hellman (CVL Certs. #C1378, #C1379, #C1385 and #C1386 with CVL Cert. #C1423, key agreement; key establishment methodology provides between 112 and 256 bits of encryption strength); NDRNG
Software Versions
rhel7.20190626
) or https:// don't prove our archive is authentic, only that you securely accessed it. Note that we are working to fix that :)
