Key Encapsulation
NTRU
Number Theoretic Research Unit Cryptosystem
Mechanism
How it works
Parameter Sets
2 variants shipped
Each variant trades security category against key, ciphertext, or signature size. QNSP exposes all variants via the @cuilabs/liboqs-native binding; tenant crypto-policy determines which are allowed.
| Variant | NIST Level | Public Key | Secret Key | Ciphertext | Note |
|---|---|---|---|---|---|
| ntru_hps2048509 / 677 / 821 / 1229 | L1 | 699 B | 935 B | 699 B | |
| ntru_hrss701 / 1373 | L3 | 1,138 B | 1,450 B | 1,138 B |
NIST ACVP
Conformance evidence
QNSP runs the official NIST ACVP test vectors against every shipped algorithm. Live evidence + SHA-3-256 tamper digest at /verify/conformance.
Use Cases
When to use it
- Migration from legacy NTRU deployments
- Research and comparative analysis
Trade-offs
What you give up, what you get
- Not on the NIST standardisation path — defer to ML-KEM for new deployments
- 30+ years of cryptanalytic study
FAQ
NTRU — frequently asked questions
Concise, source-of-truth answers to the questions buyers and engineers ask most about this algorithm.
What is NTRU?
NTRU (Number Theoretic Research Unit Cryptosystem) is a lattice based post-quantum key encapsulation mechanism. It is designed to resist attacks from both classical and quantum computers, and QNSP ships 2 of its parameter sets. It is also known as NTRU-HRSS, NTRU-HPS.
Is NTRU NIST-standardized?
NTRU is not a finalized NIST FIPS standard. QNSP ships it as a non-FIPS post-quantum option, typically to add an independent cryptographic assumption (lattice based) alongside the FIPS-standardized ML-KEM and ML-DSA for defence-in-depth.
What is NTRU used for?
On QNSP, NTRU is used for Migration from legacy NTRU deployments; Research and comparative analysis. It is available from the default crypto-policy tier upward via the liboqs provider.
References