Skip navigation links
Bouncy Castle Cryptography Library 1.87

Package org.bouncycastle.crypto.constraints

Crypto-services-constraint framework: lets callers limit which cryptographic primitives the lightweight API will produce (by key size, by allowlist, by purpose, or - for the quantum-vulnerable public-key algorithms - by the NIST IR 8547 transition timetable).

See: Description

Package org.bouncycastle.crypto.constraints Description

Crypto-services-constraint framework: lets callers limit which cryptographic primitives the lightweight API will produce (by key size, by allowlist, by purpose, or - for the quantum-vulnerable public-key algorithms - by the NIST IR 8547 transition timetable). Plugs into CryptoServicesRegistrar. The post-quantum algorithms report to the framework with the classical security strength NIST assigns to their parameter set, so a BitsOfSecurityConstraint of 192 refuses ML-KEM-512, ML-DSA-44 and the 128-bit SLH-DSA sets as it does a 2048-bit RSA key. QuantumVulnerableConstraint can also log, or refuse outright, the quantum-vulnerable algorithms, and the Properties.CONSTRAINTS_QUANTUM_VULNERABLE property installs one as the default constraint. The framework is described in section 5.8 of the specifications document.
Skip navigation links
Bouncy Castle Cryptography Library 1.87