• Bug fix: corrected reachable panic in debug mode (or with overflow-checks) when decrypting a ticket of specific lengths with Rfc5077Ticketer (and therefore rustls::crypto::aws_lc_rs::Ticketer). This happens pre-authentication.

  This is not used in the default configuration, but using stateless resumption is common and this affects the aws-lc-rs provider. The ticketer associated with the ring provider is not affected.

• Bug fix: A QUIC client using a CryptoProvider that mixes QUIC-capable and -incapable TLS1.3 suites can panic if the server chooses the QUIC-incapable suite.

• Bug fix: A QUIC client would incorrectly accept a TLS1.2 server hello. A full handshake would require a trusted server that talks TLS1.2 in QUIC.

What's Changed

• 0.23 backports by @ctz in #3182

Full Changelog: v/0.23.42...v/0.23.43

0.23.43 Latest

Latest

Compare

Choose a tag to compare

• Implemented support for "TLS Ticket Requests" (RFC 9149)
  • Client-side: a new optional ClientConfig.send_ticket_request configuration field was added to allow specifying TicketRequest parameters for requesting a specific number of TLS 1.3 session tickets from the server. Defaults to None, which skips sending the client extension and preserves current behavior.
  • Server-side: a new ServerConfig.max_tls13_tickets configuration field was added to allow setting an upper bound on the number of TLS 1.3 tickets sent in response to a client's request. Defaults to 0, which ignores the client's ticket requests extension and preserves current behavior.

What's Changed

• Backport RFC 9149 ticket_request extension by @hz2 in #3132

0.23.42

Compare

Choose a tag to compare

What's Changed

• Update read_buf API to match current nightly by @djc in #3102

0.23.41

Compare

Choose a tag to compare

• ECH: correct implementation of RFC-recommended padding scheme for SNI names in the inner client hello.
• ECH: correct padding of inner client hello when SNI is disabled.
• Alter default of ServerConfig::require_ems based on provider's FIPS status. Prior to this change, the default followed the fips crate feature, which was less helpful for users of external FIPS-approved providers.

What's Changed

• Default require_ems based on CryptoProvider FIPS status by @janrueth in #3034
• 0.23.40: backport ECH padding fixes to 0.23 by @ctz in #3044

Full Changelog: v/0.23.39...v/0.23.40

0.23.40

Compare

Choose a tag to compare

Adapts to updated nightly for the non-default read_buf feature.

What's Changed

• 0.23 branch cleanup by @djc in #3035
• Prepare 0.23.39 by @cpu in #3037

Full Changelog: v/0.23.38...v/0.23.39

0.23.39

Compare

Choose a tag to compare

What's Changed

• Backport client: allow skipping selected ALPN validation by @TaeHagen in #3020

0.23.38

Compare

Choose a tag to compare

Adds support for ML-KEM-1024 key exchange.

What's Changed

• rel-0.23 CI fixes by @ctz in #2933
• Add ML-KEM-1024 key encapsulation mechanism by @DarkmatterVale in #2932

Full Changelog: v/0.23.36...v/0.23.37

0.23.37

Compare

Choose a tag to compare

Fix #2825 by allowing P256+SHA512 and P384-SHA512 signatures in certificate chains.

What's Changed

• 0.23.36: Support P256+SHA512 and P384+SHA512 signatures in certificates by @ctz in #2828

Full Changelog: v/0.23.35...v/0.23.36

0.23.36

Compare

Choose a tag to compare

There was a regression in 0.23.23 and later where an empty value passed in ConfigBuilder::with_single_cert_with_ocsp() resulted in sending an empty OCSP value (instead of not sending anything). Thanks to @vuongDang for reporting and fixing.

What's Changed

• Backport empty OCSP fix for 0.23.35 by @djc in #2734

0.23.35

Compare

Choose a tag to compare

Fix docs.rs build after doc_auto_cfg stabilization.

What's Changed

• Privatise docsrs cfg flag by @cpu in #2718

0.23.34

Compare

Choose a tag to compare