Information Security 2 min read

OpenSSL 3.2 Alpha Release Introduces New Features and Protocol Support

The OpenSSL 3.2 Alpha has been released, adding client‑side QUIC support, TLS certificate compression, deterministic ECDSA, expanded Ed25519/Ed448 capabilities, AES‑GCM‑SIV, Argon2 with thread‑pool, HPKE, raw public‑key TLS, TCP Fast Open, pluggable post‑quantum signatures, Brainpool curves, SM4‑XTS, and optional Windows certificate‑store integration.

Laravel Tech Community
Laravel Tech Community
Laravel Tech Community
OpenSSL 3.2 Alpha Release Introduces New Features and Protocol Support

OpenSSL 3.2 Alpha has been released, bringing a substantial set of new features and protocol enhancements.

Notable additions include:

Support for client‑side QUIC with multiple streams (RFC 9000).

TLS certificate compression (RFC 8879) with zlib, zstd, and Brotli.

Deterministic ECDSA (RFC 6979).

Extended Ed25519 support to include Ed25519ctx, Ed25519ph, Ed448 and Ed448ph (RFC 8032).

AES‑GCM‑SIV cipher suite (RFC 8452).

Argon2 password‑hashing (RFC 9106) and thread‑pool functionality.

Hybrid Public Key Encryption (HPKE) (RFC 9180).

Raw public‑key usage in TLS (RFC 7250).

TCP Fast Open support (RFC 7413) when the operating system permits.

Provider‑based pluggable signature schemes in TLS, enabling third‑party post‑quantum algorithm providers.

Brainpool curves support in TLS 1.3.

SM4‑XTS cipher.

Optional use of the Windows certificate store as a trusted root source, disabled by default and activatable via an environment variable, with potential future default enablement.

Readers are encouraged to like and share the article if they found it useful.

protocolssecurityOpenSSLTLScryptographyAlpha release
Laravel Tech Community
Written by

Laravel Tech Community

Specializing in Laravel development, we continuously publish fresh content and grow alongside the elegant, stable Laravel framework.

0 followers
Reader feedback

How this landed with the community

login Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.