TLS 1.3 · Hybrid key exchange
Enabled by default
Switched from the draft X25519Kyber768Draft00 group to standard X25519MLKEM768 in 131 and removed the legacy draft group.
Browse post-quantum support by protocol and application, with versions, defaults and requirements.
Check hybrid key exchange and handshake signatures in browsers, runtimes and TLS implementations.
TLS 1.3 · Hybrid key exchange
Enabled by default
Switched from the draft X25519Kyber768Draft00 group to standard X25519MLKEM768 in 131 and removed the legacy draft group.
TLS 1.3 · Hybrid key exchange
Enabled by default
Switched to standard X25519MLKEM768 in 131 and removed the draft Kyber group; Edge 147 removed the enterprise policy toggle, keeping hybrid key exchange always enabled.
TLS 1.3 · Hybrid key exchange
Enabled by default
Enabled by default on desktop starting in 132 (manageable via the PostQuantumKeyAgreementEnabled enterprise policy); ESR and mobile releases follow separate rollout schedules.
TLS 1.3 · Hybrid key exchange
Enabled by default
TLS capabilities depend on the OS; upgrading Safari on an older macOS still requires checking OS support.
TLS 1.3 · Hybrid key exchange
Enabled by default
Enabled by default when tls.Config.CurvePreferences is empty, or add tls.X25519MLKEM768 if a custom list is set; the 1.24 standard library does not yet include ML-DSA or SLH-DSA.
TLS 1.3 · Hybrid key exchange
Enabled by default
JDK 24 provides JCA algorithm APIs for ML-KEM and ML-DSA only; TLS 1.3 hybrid key exchange in SunJSSE requires JDK 27.
TLS 1.3 · Hybrid key exchange
Enabled by default
Official 24.5.0+ binaries bundle OpenSSL 3.5, whereas distro builds dynamically linked against system OpenSSL 3.0 lack post-quantum support; algorithm APIs arrive across 24.6–24.8.
TLS 1.3 · Hybrid key exchange
Enabled by default
TLS 1.3 · ML-KEM-only key exchange
Supported
TLS 1.3 · Hybrid SM2-MLKEM key exchange
Supported
Built into the default provider in 3.5+ without extra plugins; many Linux LTS distributions still ship 3.0.x, so services dynamically linking the system library must check the loaded version.
TLS 1.3 · Hybrid key exchange
Enabled by default
Requires the default aws-lc-rs backend and prefer-post-quantum feature; switching to the ring backend or disabling default features turns off post-quantum key exchange.
TLS 1.3 · Hybrid key exchange
Supported
TLS 1.3 · Signatures
Supported
Must be linked against AWS-LC (post-quantum features are unavailable with OpenSSL) and configured with a PQ security policy such as default_pq; ML-DSA authentication requires AWS-LC 1.50.0+.
TLS 1.3 · Hybrid key exchange
Supported
Tracks rolling Git commits rather than numbered releases; TLS hybrid groups are not enabled by default and must be configured by the host application.
TLS 1.3 · Hybrid key exchange
Experimental
TLS 1.3 · Signatures
Experimental
Must be built with the external leancrypto (3.8.10+) or liboqs backend and enabled at runtime through the priority string.
TLS 1.3 · Hybrid key exchange
Enabled by default
Supports X25519MLKEM768 when explicitly enabled in 3.105+ and enables it by default in libssl starting in 3.118; Firefox manages its own rollout and policies.
TLS 1.3 · Hybrid key exchange
Supported
Disabled in default builds; enable the ML-KEM, ML-DSA and hybrid-group compile-time macros and configure the allowed TLS groups.
TLS 1.3 · Hybrid key exchange
Enabled by default
TLS 1.3 · ML-KEM-only key exchange
Supported
Enabled in the default TLS::Policy since 3.7.0; custom policies overriding key_exchange_groups() or minimized builds must explicitly include the ML-KEM modules.
Check SSH components for remote login, file transfer and embedded devices.
SSH · Hybrid sntrup761 key exchange
Enabled by default
SSH · ML-KEM hybrid key exchange
Enabled by default
SSH · Composite signature authentication
Enabled by default
Hybrid key exchange works out of the box since 9.0 (preferring ML-KEM since 10.0); composite signature authentication added in 10.6 requires generating new host or user keys.
SSH · Hybrid sntrup761 key exchange
Enabled by default
SSH · ML-KEM hybrid key exchange
Supported
Prefers NTRU Prime by default since 0.78 and adds ML-KEM hybrid key exchange in 0.83; Saved Sessions with customized algorithm lists may need their Kex order reset after upgrading.
SSH · Hybrid sntrup761 key exchange
Enabled by default
SSH · ML-KEM hybrid key exchange
Enabled by default
All crypto backends prefer sntrup761 and ML-KEM-768 hybrid key exchange by default in 0.12.0+; only mlkem1024nistp384-sha384 requires an OpenSSL 3.5+ or libgcrypt backend.
SSH · Hybrid sntrup761 key exchange
Enabled by default
SSH · ML-KEM hybrid key exchange
Enabled by default
Enabled by default upstream, but router and embedded firmware builds frequently strip DROPBEAR_SNTRUP761 or DROPBEAR_MLKEM768 in localoptions.h to save space.
Check key exchange, crypto dependencies and configuration requirements.
IKEv2 · KEM key exchange
Supported
Not enabled by default; load the built-in ml plugin (or an OpenSSL 3.5+, Botan or wolfSSL backend plugin) and add ke1_mlkem768 or similar additional key exchanges to connection proposals.
TLS 1.3 · Hybrid key exchange
Supported
Relies on the underlying TLS library such as OpenSSL 3.5+ for post-quantum algorithms; use tls-groups to restrict or enforce specific hybrid groups.
No support recorded
The handshake is fixed to Curve25519 without post-quantum key exchange; an optional 32-byte pre-shared key (PSK) can be mixed into session key derivation.
Find KEM, signature and JWT / JWS APIs for your development environment.
ML-DSA
Supported
ML-KEM
Supported
JDK 24 provides JCA algorithm APIs for ML-KEM and ML-DSA only; TLS 1.3 hybrid key exchange in SunJSSE requires JDK 27.
ML-KEM
Supported
Enabled by default when tls.Config.CurvePreferences is empty, or add tls.X25519MLKEM768 if a custom list is set; the 1.24 standard library does not yet include ML-DSA or SLH-DSA.
ML-DSA
Supported
ML-KEM
Supported
SLH-DSA
Supported
Official 24.5.0+ binaries bundle OpenSSL 3.5, whereas distro builds dynamically linked against system OpenSSL 3.0 lack post-quantum support; algorithm APIs arrive across 24.6–24.8.
ML-DSA
Experimental
ML-KEM
Supported
SLH-DSA
Experimental
Relies on OS crypto providers rather than a bundled implementation (OpenSSL 3.5+ on Linux or CNG on Windows); several APIs still carry [Experimental] compiler diagnostics.
ML-DSA
Supported
ML-KEM
Supported
SLH-DSA
Supported
Algorithm APIs are in bcprov, while X.509/CMS and TLS require the bcpkix and bctls modules; FIPS editions (BC-FJA) follow a separate release cycle.
ML-DSA
Supported
ML-KEM
Supported
Bundled with the OS and requires iOS 26 / macOS 26 or later; includes built-in X-Wing hybrid suites in its HPKE API alongside raw primitives.
ML-DSA
Supported
ML-KEM
Supported
Delegates to system CryptoKit on Apple platforms (subject to OS version limits) and uses bundled BoringSSL on Linux and Windows; provides algorithm APIs only, not TLS.
ML-DSA
Supported
ML-KEM
Supported
Pure-Go primitive library providing ML-DSA, ML-KEM-512 and hybrid KEM APIs beyond the Go 1.24 standard library; does not include a TLS stack.
ML-DSA
Supported
ML-KEM
Supported
SLH-DSA
Supported
Built into the default provider in 3.5+ without extra plugins; many Linux LTS distributions still ship 3.0.x, so services dynamically linking the system library must check the loaded version.
ML-DSA
Supported
ML-KEM
Supported
SLH-DSA
Supported
Enabled in the default TLS::Policy since 3.7.0; custom policies overriding key_exchange_groups() or minimized builds must explicitly include the ML-KEM modules.
ML-DSA
Supported
ML-KEM
Supported
Supplies libcrypto algorithm implementations while s2n-tls or rustls controls TLS handshake policy; AWS-LC-FIPS certified branches follow a separate release track.
ML-DSA
Supported
ML-KEM
Supported
Disabled in default builds; enable the ML-KEM, ML-DSA and hybrid-group compile-time macros and configure the allowed TLS groups.
ML-DSA
Supported
ML-KEM
Supported
SLH-DSA
Supported
Version 0.3.0 provides the three standard algorithm families along with X.509 certificate and CMS signature support; enable the corresponding Crypto and PKI build features.
ML-DSA
Supported
ML-KEM
Supported
Tracks rolling Git commits rather than numbered releases; TLS hybrid groups are not enabled by default and must be configured by the host application.
ML-DSA
Experimental
Must be built with the external leancrypto (3.8.10+) or liboqs backend and enabled at runtime through the priority string.
ML-KEM
Supported
Supports X25519MLKEM768 when explicitly enabled in 3.105+ and enables it by default in libssl starting in 3.118; Firefox manages its own rollout and policies.
JOSE · Post-quantum signature encodings
Supported
Contains no built-in algorithm implementation and relies on the host runtime's Web Crypto API (such as Node.js 24.7.0+) for ML-DSA support.
JOSE · Post-quantum signature encodings
Supported
The core module does not bundle post-quantum algorithms; import and register the github.com/jwx-go/mldsa/v4 companion module.
Explore algorithm APIs, experimental protocol integrations and available benchmarks.
ML-DSA
Supported
ML-KEM
Supported
SLH-DSA
Supported
Intended for research, prototypes and interoperability testing; algorithms depend on build options and protocols need integrations.
ML-DSA
Supported
ML-KEM
Supported
SLH-DSA
Supported
Check std / adv implementations, target platforms and hash options; match parameter sets and standard constructions for interoperability.
ML-DSA
Supported
ML-KEM
Supported
Pure-Go primitive library providing ML-DSA, ML-KEM-512 and hybrid KEM APIs beyond the Go 1.24 standard library; does not include a TLS stack.
TLS 1.3 · Hybrid key exchange
Experimental
ML-DSA
Experimental
ML-KEM
Experimental
Experimental OpenSSL provider; match liboqs and OpenSSL versions and check which algorithms OpenSSL provides natively.