Digital Signature
UOV
Unbalanced Oil and Vinegar Signatures
Mechanism
How it works
Parameter Sets
1 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 | Signature | Note |
|---|---|---|---|---|---|
| OV-Is / Ip / III / V (multiple param sets) | L5 | 412,160 B | 348,704 B | 96 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
- Compact signatures (96 bytes) for size-constrained signature transport
- Multivariate diversification away from lattice-based signatures
Trade-offs
What you give up, what you get
- Smallest signatures in the catalogue (96 bytes)
- Very large public keys (hundreds of KB)
- 30+ years of cryptanalysis on UOV foundations
FAQ
UOV — frequently asked questions
Concise, source-of-truth answers to the questions buyers and engineers ask most about this algorithm.
What is UOV?
UOV (Unbalanced Oil and Vinegar Signatures) is a multivariate post-quantum digital signature scheme. It is designed to resist attacks from both classical and quantum computers, and QNSP ships 1 of its parameter sets. It is also known as Oil-and-Vinegar.
Is UOV NIST-standardized?
UOV is not a finalized NIST FIPS standard. QNSP ships it as a non-FIPS post-quantum option, typically to add an independent cryptographic assumption (multivariate) alongside the FIPS-standardized ML-KEM and ML-DSA for defence-in-depth.
What is UOV used for?
On QNSP, UOV is used for Compact signatures (96 bytes) for size-constrained signature transport; Multivariate diversification away from lattice-based signatures. It is available from the default crypto-policy tier upward via the liboqs provider.
References