Ubuntu 16.04 Kernel Crypto API Cryptographic Module
Ubuntu 16.04 Kernel Crypto API Cryptographic Module, from Canonical Ltd., holds FIPS 140-2 certificate #4604 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 and installed, initialized and configured as specified in Sections 9.1 of the Security Policy.
Certificate
| Certificate number | 4604 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Software |
| Embodiment | Multi-Chip Stand Alone |
| Vendor | Canonical Ltd. · website |
| Software versions | 2.0 |
Module description
Quoted from the NIST CMVP entry for this certificate.
The Ubuntu 16.04 Kernel Crypto API module is a software module running as part of the operating system kernel that provides general purpose cryptographic services.
Security level exceptions
- Physical Security: N/A
- Mitigation of Other Attacks: N/A
Approved algorithms (7)
| Algorithm | CAVP certificates |
|---|---|
| AES | C1210, C1211, C1212, C1213, C1214, C1215, C1216, C1220, C1221, C1222, C1303 |
| DRBG | C1217, C1218, C1219, C1220, C1221, C1222 |
| HMAC | C1217, C1218, C1219, C1222 |
| KTS | |
| RSA | C1217, C1218, C1219, C1222 |
| SHS | C1217, C1218, C1219, C1222 |
| Triple-DES | C1220, C1222 |
Allowed algorithms
NDRNG; RSA (key wrapping; key establishment methodology provides between 112 and 149 bits of encryption strength)
Tested configurations
- Ubuntu 16.04 LTS 64-bit running on Supermicro SYS-5018R-WR with Intel Xeon E5 with PAA
- Ubuntu 16.04 LTS 64-bit running on Supermicro SYS-5018R-WR with Intel Xeon E5 without PAA (single-user mode)
Validation history
| Date | Type | Lab |
|---|---|---|
| 2023-09-25 | Initial | 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: 2023-09-25