Huawei EulerOS 2.0 OpenSSH Client Cryptographic Module
Huawei EulerOS 2.0 OpenSSH Client Cryptographic Module, from Huawei Technologies CO., Ltd., holds FIPS 140-2 certificate #4246 at overall level 1. The validation is active, with a sunset date of 2026-09-21. Below are its validation history, algorithm certificates and security policy, drawn from the NIST CMVP entry.
Caveat: This module contains the embedded module Huawei EulerOS 2.0 OpenSSL Cryptographic module validated to FIPS 140-2 under Cert. #4235 operating in FIPS mode. When operated in FIPS mode.
Certificate
| Certificate number | 4246 |
|---|---|
| Standard | FIPS 140-2 |
| Status | active |
| Sunset date | 2026-09-21 |
| Overall level | 1 |
| Module type | Software |
| Embodiment | Multi-Chip Stand Alone |
| Vendor | Huawei Technologies CO., Ltd. · website |
| Software versions | 1.1 |
Module description
Quoted from the NIST CMVP entry for this certificate.
The Huawei EulerOS 2.0 OpenSSH Client Cryptographic Module is a binary implementing the Secure Shell (SSH) protocol in the EulerOS 2.0 Operating System user space. The module interacts with other entities acting as SSH servers via the SSH protocol. The module only supports SSHv2 protocol.
Security level exceptions
- Physical Security: N/A
- Mitigation of Other Attacks: N/A
Approved algorithms (13)
| Algorithm | CAVP certificates |
|---|---|
| AES | A903 |
| CVL | A1079 |
| DRBG | A903 |
| DSA | A903 |
| ECDSA | A903 |
| ENT | |
| HMAC | A903 |
| KAS | |
| KAS-SSC | A903 |
| KTS | |
| RSA | A903 |
| SHS | A903 |
| Triple-DES | A903 |
Tested configurations
- Huawei EulerOS 2.0 on FusionServer RH2288 with Intel Xeon E5-2690 v3 processor without PAA (single-user mode)
- Huawei EulerOS 2.0 on Taishan200 with Huawei Kunpeng 920 processor without PAA (single-user mode).
Validation history
| Date | Type | Lab |
|---|---|---|
| 2022-06-09 | Initial | DEKRA Testing and Certification S.A.U |
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 active
- Validation dates on record: 2022-06-09