NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
crates.io, #79 most downloaded on crates.io
Rustls is a modern TLS library written in Rust.
Latest stable
0.23.46
Last release 10 days ago
12 Nov 2026
Ships fairly regularly
a new release about every 4 weeks
Nearly every release is documented
notes for 60 of the last 60 stable releases
4 versions withdrawn
withdrawn after publishing
10 years old
119 releases · first in 2016
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
[GHSA-h2v8-394m-p7vv](https://github.com/rustls/rustls/security/advisories/GHSA-h2v8-394m-p7vv): The built-in (but disabled by default) Brotli certifi
Your coding agent can read these notes before it upgrades. Set up the MCP server →
GHSA-h2v8-394m-p7vv: The built-in (but disabled by default) Brotli certificate decompression can allocate an attacker-controlled amount of memory up to 1 GiB before authentication *
GHSA-c8m5-c952-6cm4: Debug impls for Tls12ClientSessionValue and Tls13ClientSessionValue include secret data *
GHSA-w44r-93j7-qv28: An unauthenticated ServerHello poisons the per-name key-exchange hints, so later ClientHellos carry only a classical X25519 share. Thank you to @Adam010341 .
GHSA-vp88-798v-h67f: In rustls 0.23.44 and 0.23.45, application data that a client buffers before the handshake completes is sent to the server even when the server rejects Encrypted Client Hello (ECH). Thank you to @ramonmrc18.
* Thanks to OpenAI OutboundDisclosures@openai.com for submitting 13 findings to us, whose fixes are included in this release. ** Thanks to @Mounika2456 for their continued contribution of hardening and compliance fixes
Full Changelog: https://github.com/rustls/rustls/compare/v/0.23.45...v/0.23.46
GHSA-h2v8-394m-p7vv: The built-in (but disabled by default) Brotli certificate decompression can allocate an attacker-controlled amount of memory up to 1 GiB before authentication *
GHSA-c8m5-c952-6cm4: Debug impls for Tls12ClientSessionValue and Tls13ClientSessionValue include secret data *
GHSA-w44r-93j7-qv28: An unauthenticated ServerHello poisons the per-name key-exchange hints, so later ClientHellos carry only a classical X25519 share. Thank you to @Adam010341 .
GHSA-vp88-798v-h67f: In rustls 0.23.44 and 0.23.45, application data that a client buffers before the handshake completes is sent to the server even when the server rejects Encrypted Client Hello (ECH). Thank you to @ramonmrc18.
* Thanks to OpenAI OutboundDisclosures@openai.com for submitting 13 findings to us, whose fixes are included in this release.
** Thanks to @Mounika2456 for their continued contribution of hardening and compliance fixes
Full Changelog: v/0.23.45...v/0.23.46
Bug fix : TLS 1.3 handshake messages incorrectly accepted across encryption level boundaries
Bug fix: TLS 1.3 handshake messages incorrectly accepted across encryption level boundaries
Rustls accepted TLS 1.3 handshake messages sent at the wrong encryption level when they followed a key-changing message in the same record. The handshake transcript is still authenticated, so a network-position attacker cannot use this to alter or complete a handshake; the practical effect is that a peer could send handshake messages that should be encrypted in plaintext without rustls rejecting the connection.
This issue is tracked as GHSA-2mjx-qc3c-rqvc. This issue affects rustls versions 0.23.13 through 0.23.44 inclusive.
Note that this is functionally the same bug as GO-2026-4340.
Full Changelog: v/0.23.44...v/0.23.45
Support for post-quantum secure ML-DSA certificates is now enabled by default in the aws-lc-rs crypto provider. ML-DSA certificates are not supported
Support for post-quantum secure ML-DSA certificates is now enabled by default in the aws-lc-rs crypto provider. ML-DSA certificates are not supported in the public web PKI, but they can be used with private certificate hierarchies.
The built-in KeyLogFile implementation now creates files that are restricted to being read only by the owner.
Bug fix: corrected reachable panic in debug mode (or with overflow-checks) when decrypting a ticket of specific lengths with Rfc5077Ticketer (and ther
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.
Full Changelog: https://github.com/rustls/rustls/compare/v/0.23.42...v/0.23.43
Implemented support for "TLS Ticket Requests" (RFC 9149)
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.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.Update read_buf API to match current nightly by @djc in https://github.com/rustls/rustls/pull/3102
ECH: correct implementation of RFC-recommended padding scheme for SNI names in the inner client hello.
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.Full Changelog: https://github.com/rustls/rustls/compare/v/0.23.39...v/0.23.40
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.Full Changelog: v/0.23.39...v/0.23.40
Adapts to updated nightly for the non-default read_buf feature.
Adapts to updated nightly for the non-default read_buf feature.
Full Changelog: https://github.com/rustls/rustls/compare/v/0.23.38...v/0.23.39
Adapts to updated nightly for the non-default read_buf feature.
Full Changelog: v/0.23.38...v/0.23.39
Backport client: allow skipping selected ALPN validation by @TaeHagen in https://github.com/rustls/rustls/pull/3020
Adds support for ML-KEM-1024 key exchange.
Adds support for ML-KEM-1024 key exchange.
Full Changelog: https://github.com/rustls/rustls/compare/v/0.23.36...v/0.23.37
Adds support for ML-KEM-1024 key exchange.
Full Changelog: v/0.23.36...v/0.23.37
Fix #2825 by allowing P256+SHA512 and P384-SHA512 signatures in certificate chains.
Fix #2825 by allowing P256+SHA512 and P384-SHA512 signatures in certificate chains.
Full Changelog: https://github.com/rustls/rustls/compare/v/0.23.35...v/0.23.36
Fix #2825 by allowing P256+SHA512 and P384-SHA512 signatures in certificate chains.
Full Changelog: v/0.23.35...v/0.23.36
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 OC
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.
Fix docs.rs build after doc_auto_cfg stabilization.
Fix docs.rs build after doc_auto_cfg stabilization.
New feature: foundational support for QUIC multipath draft - #2706 thanks to @flub and @divagant-martian
PeerMisbehaved::TooManyKeyUpdateRequests - #2709Full Changelog: https://github.com/rustls/rustls/compare/v/0.23.32...v/0.23.33
New feature: support verification of P256+SHA512 and P384-SHA512 ECDSA signatures with aws-lc-rs. This is not a recommended combination, but such sign
New feature: support verification of P256+SHA512 and P384-SHA512 ECDSA signatures with aws-lc-rs. This is not a recommended combination, but such signatures exist in the wild. Fixes #2661 and #2477.
Full Changelog: https://github.com/rustls/rustls/compare/v/0.23.31...v/0.23.32
Fixes #2584 -- complete_io() not making progress when used with non-blocking IO. This was a regression in 0.23.30 (now yanked).
complete_io() not making progress when used with non-blocking IO. This was a regression in 0.23.30 (now yanked).Full Changelog: https://github.com/rustls/rustls/compare/v/0.23.30...v/0.23.31
Fixes a bug with the unbuffered connection API that could result in deframing junk data after a close notify alert was received.
Connection::complete_io() to yield a WouldBlock error when both read/write operations are blocked.complete_io() with non-blocking transport by @ctz in https://github.com/rustls/rustls/pull/2578Full Changelog: https://github.com/rustls/rustls/compare/v/0.23.29...v/0.23.30
…the UnsupportedSignatureAlgorithm variant (now deprecated) in order to provide more context.
CertificateError and CertRevocationError to replace the UnsupportedSignatureAlgorithm variant (now deprecated) in order to provide more context._ABSENT_PARAMS PKCS#1 signature algorithms by @ctz in https://github.com/rustls/rustls/pull/2505ClientHello by @ctz in https://github.com/rustls/rustls/pull/2502Vec<Enum> uses in extensions by @ctz in https://github.com/rustls/rustls/pull/2509From<Arc<CertifiedKey>> for SingleCertAndKey by @stormshield-gt in https://github.com/rustls/rustls/pull/2535New feature: expose number of TLS1.3 tickets received via `ClientConnection::tls13_tickets_received()`. Thanks to @Frando.
ClientConnection::tls13_tickets_received(). Thanks to @Frando.ClientHello::named_groups() -- see #2484 for background.secp256r1mlkem768 key exchange. This is not offered by default, but rustls::crypto::aws_lc_rs::kx_group::SECP256R1MLKEM768 can be added to a custom CryptoProvider::kx_groups. Thanks to @cjpatton.ClientHelloPayload by @djc in https://github.com/rustls/rustls/pull/2457secp256r1mlkem768 by @ctz in https://github.com/rustls/rustls/pull/2471clippy::clone_on_ref_ptr lint by @ctz in https://github.com/rustls/rustls/pull/2474x.clone() to Arc::clone(&x) by @ctz in https://github.com/rustls/rustls/pull/2475HandshakeMessagePayload::typ field by @ctz in https://github.com/rustls/rustls/pull/2478named_groups extension in ClientHello by @ctz in https://github.com/rustls/rustls/pull/2488Full Changelog: https://github.com/rustls/rustls/compare/v/0.23.27...v/0.23.28
Add support for connection-level ALPN protocol configuration.
prefer-post-quantum to default features by @ctz in https://github.com/rustls/rustls/pull/2425Bug fix: in certain circumstances we saw std::Write::write_vectored implementations that reported writing more bytes than were available, in violation
std::io::Write::write_vectored implementations that reported writing more bytes than were available, in violation of that method's invariants. This seems to happen on macOS with certain VPN software active. Now we detect and return an error from write_tls calls in this case. See #2316.SignatureSchemes in TLS1.3, so that external providers may support ED448, post-quantum signatures, and others. See #2420.SignatureScheme::supported_in_tls13 by @ctz in https://github.com/rustls/rustls/pull/2420io::Write::write_vectored by @ctz in https://github.com/rustls/rustls/pull/2422Full Changelog: https://github.com/rustls/rustls/compare/v/0.23.25...v/0.23.26
Translate webpki::Error::RequiredEkuNotFound to rustls::CertificateError::InvalidPurpose. This allows rustls-platform-verifier to stop requiring that
webpki::Error::RequiredEkuNotFound to rustls::CertificateError::InvalidPurpose. This allows rustls-platform-verifier to stop requiring that rustls shares its version of its private webpki dependency, which is a semver hazard.Full Changelog: https://github.com/rustls/rustls/compare/v/0.23.24...v/0.23.25
New feature: More detailed and helpful error reporting for common certificate errors, such as name mismatches and certificate expiry. Users who std::D
New feature: More detailed and helpful error reporting for common certificate errors, such as name mismatches and certificate expiry. Users who std::fmt::Display the rustls Error type will take advantage of this automatically. Users handling CertificateError variants individually should note the new variants, such as CertificateError::NotValidForNameContext (compare CertificateError::NotValidForName).
$ cargo -q run --bin tlsclient-mio -- --http wrong.host.badssl.com
TLS error: invalid peer certificate: certificate not valid for name "wrong.host.badssl.com";
certificate is only valid for DnsName("*.badssl.com") or DnsName("badssl.com")
Connection closed
The old CertificateError variants (such as NotValidForName, Expired, etc.) remain usable, and may be produced by both the default and third-party certificate verification traits.
New feature: Allow KTLS handoff for unbuffered API users, by introducing dangerous_extract_secrets(). Thanks to @edef1c.
Bug fix: Unbuffered connections now consume data during the next_record() function, rather than production of the state. This fixes #2031.
Bug fix: Build speed improvement for aws-lc-rs fips users.
Behavior change: Clients no longer offer resumption between different ClientConfigs that share a resumption store but do not share server certificate verification and client authentication credentials. If you share a resumption store between multiple ClientConfigs, please ensure their server certificate verification and client authentication credentials are also shared. Please read the new documentation on the ClientConfig::resumption item for details.
Additionally, if you share a resumption store or ticketer between multiple ServerConfigs, please see the new documentation on ServerConfig about this.
coverage(off) by @ctz in https://github.com/rustls/rustls/pull/2373Full Changelog: https://github.com/rustls/rustls/compare/v/0.23.23...v/0.23.24
Export SingleCertAndKey implementation of ResolvesServerCert (was already used internally).
SingleCertAndKey implementation of ResolvesServerCert (was already used internally).CertifiedKey::from_der() to help create CertifiedKeys with necessary checks.ConnectionState::PeerClosed variant, raised when the peer cleanly terminates their side of the connection with a close_notify alert.PeerClosed state by @ctz in https://github.com/rustls/rustls/pull/2332Support for post-quantum-secure key exchange using X25519MLKEM768 when using the aws-lc-rs provider. This is supported by default, but offered at a lo
Support for post-quantum-secure key exchange using X25519MLKEM768 when using the aws-lc-rs provider. This is supported by default, but offered at a low algorithm negotiation priority.
A new crate feature prefer-post-quantum adjusts the aws-lc-rs provider's DEFAULT_KX_GROUPS order, so X25519MLKEM768 is the most preferred key exchange algorithm. This has some performance impact: handshakes which offer TLS1.3 are larger and slower.
We expect to add this feature to the crate's default features in a future minor release.
The rustls-post-quantum crate now depends on the core rustls crate and activates this feature.
std::io::BufRead is now implemented for Reader, Stream, and StreamOwned. Thanks to @goffrie
sync::Arc alias to support fork for targets with no atomic ptr by @brody4hire in https://github.com/rustls/rustls/pull/2285std feature by @brody4hire in https://github.com/rustls/rustls/pull/2313ChunkVecBuffer::consume larger than length by @paolobarbolini in https://github.com/rustls/rustls/pull/2318ChunkVecBuffer by @ctz in https://github.com/rustls/rustls/pull/2319Full Changelog: https://github.com/rustls/rustls/compare/v/0.23.21...v/0.23.22
Added support for sending the certificate_authorities extension in the ClientHello (see #2265).
Added support for sending the certificate_authorities extension in the ClientHello (see #2265).
certificate_authorities extension in ClientHello by @s-arash in https://github.com/rustls/rustls/pull/2265Support hybrid key exchange optimization: this improves efficiency of hybrid post-quantum key exchanges when the classical half of the hybrid is selec
Release notes:
This release, like 0.23.18, has an MSRV of 1.71. We are aware of a compiler bug in 1.71 that may affect rustls and recommend 1.73 or later.
test_for_each_provider! by @ctz in https://github.com/rustls/rustls/pull/2222clippy::zombie_processes warnings by @ctz in https://github.com/rustls/rustls/pull/2248<pre> blowing out page width by @ctz in https://github.com/rustls/rustls/pull/2255Full Changelog: https://github.com/rustls/rustls/compare/v/0.23.18...v/0.23.20
Note that this is a one-off; there will not be future releases with MSRV 1.63 (for future security fixes or otherwise).
This release is functionally equivalent to 0.23.18, except the MSRV has been relaxed back to 1.63. The next release, 0.23.20, will return to an MSRV of 1.71. This release is intended to give users with conservative MSRV requirements a release that contains the fix for RUSTSEC-2024-0399.
Note that this is a one-off; there will not be future releases with MSRV 1.63 (for future security fixes or otherwise).
Full Changelog: https://github.com/rustls/rustls/compare/v/0.23.18...v/0.23.19
Availability issue: correct a panic in the Acceptor API when a client hello is fragmented over several TLS messages. This was introduced in 0.23.13. I
Release notes:
Acceptor API when a client hello is fragmented over several TLS messages. This was introduced in 0.23.13. It does not affect earlier versions. Thank you to @kvinwang for the report and fix.open_within() by @ctz in https://github.com/rustls/rustls/pull/2221Full Changelog: https://github.com/rustls/rustls/compare/v/0.23.17...v/0.23.18
Performance improvement: by default rustls servers now send fewer TLS1.3 tickets to a client. The old default was 4 tickets, now it is 2. The number c
ServerConfig::send_tls13_tickets.TicketRotator, a version of TicketSwitcher with improved thread scalability by @ctz in https://github.com/rustls/rustls/pull/2193Full Changelog: https://github.com/rustls/rustls/compare/v/0.23.16...v/0.23.17
Add support for RFC 7250 raw public keys.
Improve performance when reading plaintext data in small increments
Full Changelog: https://github.com/rustls/rustls/compare/v/0.23.14...v/0.23.15
Breaking change for `no_std` users: The return type of `CryptoProvider::install_default()` would change depending on the std crate feature. This was u…
no_std users: The return type of CryptoProvider::install_default() would change depending on the std crate feature. This was unintended and is corrected in this release. But that does mean this semver-compatible release contains a breaking API change, albeit only for users who omit the std crate feature. Our apologies in advance.SupportedKxGroup to be version-specific by @ctz in https://github.com/rustls/rustls/pull/2112Full Changelog: https://github.com/rustls/rustls/compare/v/0.23.13...v/0.23.14
Add new `custom-provider` crate feature to disable installation of built-in provider. This may be useful in situations where your application wishes t
custom-provider crate feature to disable installation of built-in provider. This may be useful in situations where your application wishes to ensure consistent use of a custom crypto provider throughout the dependency tree. Thanks to @stormshield-gtmax_early_data_size bytes of early data will be accepted, if it is read while it is being received. Thanks to @tahmid-23 for the report and fix.default_fips_provider() item without aws_lc_rs by @ctz in https://github.com/rustls/rustls/pull/2064ServerConnection::new by @DragonDev1906 in https://github.com/rustls/rustls/pull/2073CryptoProvider provider fns by @ctz in https://github.com/rustls/rustls/pull/2083Full Changelog: https://github.com/rustls/rustls/compare/v/0.23.12...v/0.23.13
Added support for P521 SHA-256/SHA-384 signature verification with aws-lc-rs.
Added support for P521 SHA-256/SHA-384 signature verification with aws-lc-rs.
New feature: API for determining whether a CertifiedKey's certificate and private key matches: `keys_match()`. This is called from existing fallible f
New feature: API for determining whether a CertifiedKey's certificate and private key matches: keys_match(). This is called from existing fallible functions that accept a private key and certificate (for example, with_single_cert()) so these functions now detect this misconfiguration.
This relies on a new -- optional -- member of the SigningKey trait: public_key() -- downstream implementers of this trait can opt-in to this behavior by implementing this method.
New feature: API for determining which key exchange group a connection used: negotiated_key_exchange_group()
New feature: Automatic sending of TLS1.3 key_update messages to avoid exceeding AEAD confidentiality limits. This is complemented with a new API for manual use, refresh_traffic_keys()
Expose common connection items in unbuffered API (docs)
key_update API and automatic key refreshing by @ctz in https://github.com/rustls/rustls/pull/2003key_update review follow-up by @ctz in https://github.com/rustls/rustls/pull/2016CommonState by @ctz in https://github.com/rustls/rustls/pull/2032public_key() for all built-in SigningKey impls by @ctz in https://github.com/rustls/rustls/pull/2039Full Changelog: https://github.com/rustls/rustls/compare/v/0.23.10...v/0.23.11
[draft-ietf-tls-esni-18](https://datatracker.ietf.org/doc/html/draft-ietf-tls-esni-18) encrypted client hello (ECH) is now supported for client applic
ech-client.rs example for a complete end-to-end demonstration using DNS-over-HTTPS to retrieve a server's ECH configuration for building a Rustls ClientConfig using with_ech().Full Changelog: https://github.com/rustls/rustls/compare/v/0.23.9...v/0.23.10
[RFC8879](https://datatracker.ietf.org/doc/html/rfc8879) certificate compression is now supported. Get started by enabling the brotli and/or zlib crat
brotli and/or zlib crate features, which depend on the brotli or zlib-rs crates. We recommend brotli as it has the widest deployment so far.#[allow()] cleanups by @ctz in https://github.com/rustls/rustls/pull/1982Full Changelog: https://github.com/rustls/rustls/compare/v/0.23.8...v/0.23.9
Add support for enforcing CRL expiration, by @jasperpatterson
Full Changelog: https://github.com/rustls/rustls/compare/v/0.23.7...v/0.23.8
send_close_notify is now idempotent, in case it is accidentally called more than once.
send_close_notify is now idempotent, in case it is accidentally called more than once.read_tls now refuses to read further data after a close_notify is received, by returning Ok(0) (ie, an EOF).close_notify received, avoiding a spurious DecryptError on subsequent calls to process_new_packets().Full Changelog: https://github.com/rustls/rustls/compare/v/0.23.6...v/0.23.7
Improve interop with TLS1.2 servers having ECDSA certificates when using aws-lc-rs provider
close_notify (#1950)ECDSA_NISTP521_SHA512 by @ctz in https://github.com/rustls/rustls/pull/1924SignatureScheme::sign by @ctz in https://github.com/rustls/rustls/pull/1936Full Changelog: https://github.com/rustls/rustls/compare/v/0.23.5...v/0.23.6
This release corrects a denial-of-service condition in rustls::ConnectionCommon::complete_io(), reachable via network input. If a close_notify alert i
rustls::ConnectionCommon::complete_io(), reachable via network input. If a close_notify alert is received during a handshake, complete_io() did not terminate. Callers which do not call complete_io() are not affected.handshake_kind()) for learning whether a handshake was resumed or not.no-std support has been extended, allowing use of LimitedCache, ResolvesServerCertUsingSni, ServerSessionMemoryCache, ClientSessionStore, TicketSwitcher and the aws-lc-rs/ring Ticketer when the hashbrown feature is enabled and a compatible no-std Mutex implementation provided.server_name extension validation by @ctz in https://github.com/rustls/rustls/pull/1881VerifierBuilderError by @ctz in https://github.com/rustls/rustls/pull/1884Option from handshake_kind() by @ctz in https://github.com/rustls/rustls/pull/1900complete_io behaviour when close_notify alert is received by @ctz in https://github.com/rustls/rustls/pull/1905Full Changelog: https://github.com/rustls/rustls/compare/v/0.23.4...v/0.23.5
Bug fix: correct cipher suite filtering if a custom certificate verifier offers support for SignatureScheme::ECDSA_SHA1_Legacy.
SignatureScheme::ECDSA_SHA1_Legacy.AcceptedAlert::writeFull Changelog: https://github.com/rustls/rustls/compare/v/0.23.3...v/0.23.4
Bug fix: correct cipher suite selection when ECDHE and FFDHE suites are both offered.
Full Changelog: https://github.com/rustls/rustls/compare/v/0.23.2...v/0.23.3
Bug fix: return correct ConnectionTrafficSecrets variant from dangerous_extract_secrets() when AES-256-GCM is negotiated.
ConnectionTrafficSecrets variant from dangerous_extract_secrets() when AES-256-GCM is negotiated.aws-lc-rs crate feature as alias for aws_lc_rs crate feature.ConnectionTrafficSecrets variant when AES-256-GCM is negotiated. by @Arnavion in https://github.com/rustls/rustls/pull/1834unused_qualifications warnings by @ctz in https://github.com/rustls/rustls/pull/1839merge_group job performance by @ctz in https://github.com/rustls/rustls/pull/1840aws-lc-rs feature as an alias for aws_lc_rs by @joshtriplett in https://github.com/rustls/rustls/pull/1843Full Changelog: https://github.com/rustls/rustls/compare/v/0.23.1...v/0.23.2
Fix build with aws_lc_rs feature enabled but std feature disabled.
aws_lc_rs feature enabled but std feature disabled.Full Changelog: https://github.com/rustls/rustls/compare/v/0.23.0...v/0.23.1
…and [Accepted::into_connection] (which is also a breaking change). Applications should write this data to the peer. See the [server_acceptor] example.
Default cryptography provider changed to aws-lc-rs. Note that this has some implications on platform support and build-time tool requirements such as cmake on all platforms and nasm on Windows.
Support for ring continues to be available: set the ring crate feature.
Support for FIPS validated mode with aws-lc-rs: see the manual section and aws-lc-rs's FIPS documentation. Note that aws-lc-rs in FIPS mode has further build-time requirements as detailed in the FIPS documentation.
Thanks to the aws-lc-rs for their assistance on this.
Support for process-wide selection of CryptoProviders. See the documentation. Note that callers of ClientConfig::builder(), ServerConfig::builder(), WebPkiServerVerifier::builder() and WebPkiClientVerifier::builder() must now ensure that the crate's features are unambiguous or explicitly select a process-level provider using CryptoProvider::install_default(). Otherwise, these calls will panic with:
no process-level CryptoProvider available -- call CryptoProvider::install_default() before this point
We recommend that libraries rely on the process-level provider by default, and that applications use this new API to select the provider they wish to use.
New unbuffered API. UnbufferedClientConnection and UnbufferedServerConnection offer a low-level, event-driven API which does not internally buffer data.
Thanks to the team from Ferrous Systems.
New no_std support. A new (enabled by default) std crate feature now gates all APIs that depend on std. The above unbuffered APIs must be used for no_std support. Note that alloc continues to be required. Work is ongoing to reintroduce certain APIs for no_std users (see #1688) -- please file issues for other no_std use cases.
Thanks to the team from Ferrous Systems.
Performance improvement: internal copying while sending data is reduced. Thanks to the team from the Sōzu project.
Performance improvement: write_vectored now produces less on-the-wire overhead, which will dramatically improve throughput if it is used with a large number of small messages.
Thanks to the team from the Sōzu project.
Acceptor API error handling improvement. If a TLS alert should be sent to inform the peer of a connection failure, this is now made available in the Err() variant returned from Acceptor::accept and Accepted::into_connection (which is also a breaking change). Applications should write this data to the peer. See the server_acceptor example.
Support for FFDHE key exchange: custom CryptoProviders can now support FFDHE key exchange, in accordance with RFC7919. Note that the default providers do not do this.
Thanks to the team from Fortanix.
Support for servers requiring extended_master_secret support from clients. See ServerConfig::require_ems.
Thanks to the team from Fortanix.
Extension ordering in ClientHello messages are now randomised as an anti-fingerprinting measure. We do not foresee any interoperability issues as Chrome has already rolled out the same change. Thanks to @GomesGoncalo.
Breaking change: CipherSuiteCommon::integrity_limit field removed (this was QUIC-specific, it has moved to quic::PacketKey::integrity_limit()).
Breaking change: crypto::cipher::BorrowedPlainMessage and crypto::cipher::OpaqueMessage have been renamed (to OutboundPlainMessage and OutboundOpaqueMessage) and altered to support performance improvements. See the example code.
Breaking change: all protocol enum types (eg. CipherSuite) have had their get_u8/get_u16 accessor removed; use u8::from() / u16::from() instead.
provider-example library no-std compatible (almost) by @japaric in https://github.com/rustls/rustls/pull/1636MessageDeframer: batch discard operations by @japaric in https://github.com/rustls/rustls/pull/1595SupportedProtocolVersion as non-exhaustive by @pvdrz in https://github.com/rustls/rustls/pull/1673verify_server_name by @ctz in https://github.com/rustls/rustls/pull/1698fragment_slice return type by @pvdrz in https://github.com/rustls/rustls/pull/1701ClientHello legacy_record_version commentary by @ctz in https://github.com/rustls/rustls/pull/1705certificate_authorities extension by @ctz in https://github.com/rustls/rustls/pull/1729extended_master_secret extension in TLS 1.2 by @Taowyoo in https://github.com/rustls/rustls/pull/1754aws-lc-rs with default-features = false by @joshtriplett in https://github.com/rustls/rustls/pull/1768require_ems in FIPS mode by @ctz in https://github.com/rustls/rustls/pull/1772write_vectored by @Keksoj in https://github.com/rustls/rustls/pull/1640BorrowedPlainMessage by @ctz in https://github.com/rustls/rustls/pull/1794end_entity variable when verifying CertificateVerify by @thomwiggers in https://github.com/rustls/rustls/pull/1799OpaqueMessage::encode by @Wonshtrum in https://github.com/rustls/rustls/pull/1774no process-level CryptoProvider panic by @ctz in https://github.com/rustls/rustls/pull/1822Full Changelog: https://github.com/rustls/rustls/compare/v/0.22.2...v/0.23.0
This release corrects a denial-of-service condition in rustls::ConnectionCommon::complete_io, reachable via network input. If a close_notify alert is
This release corrects a denial-of-service condition in rustls::ConnectionCommon::complete_io, reachable via network input. If a close_notify alert is received during a handshake, complete_io did not terminate. Callers which do not call complete_io are not affected.
complete_io behaviour when close_notify alert is received (0.22 edition) by @ctz in https://github.com/rustls/rustls/pull/1906Full Changelog: https://github.com/rustls/rustls/compare/v/0.22.3...v/0.22.4
Bug fix: return correct ConnectionTrafficSecrets variant from dangerous_extract_secrets() when AES-256-GCM is negotiated. See #1833
ConnectionTrafficSecrets variant from dangerous_extract_secrets() when AES-256-GCM is negotiated. See #1833SignatureScheme::ECDSA_SHA1_Legacy. See https://github.com/seanmonstar/reqwest/issues/2191Full Changelog: https://github.com/rustls/rustls/compare/v/0.22.2...v/0.22.3
Avoid sending an empty certificate_authorities extension as a TLS1.3 server. This is incorrect and breaks interop with Java (#1727).
certificate_authorities extension as a TLS1.3 server. This is incorrect and breaks interop with Java (#1727).aws-lc-rs provider (#1706).Full Changelog: https://github.com/rustls/rustls/compare/v/0.22.1...v/0.22.2
TLS 1.2 servers now remove session tickets after observing a failure to decrypt, preventing future resumption with the same unusable ticket.
rustls_pki_types crate is now re-exported as rustls::pki_types.rustls::pki_types re-export.quic::PacketKey and quic::HeaderProtectionKey traits are now Send + Sync.MessageDeframer internals.Full Changelog: https://github.com/rustls/rustls/compare/v/0.22.0...v/0.22.1
The deprecated ConfigBuilder ::with_single_cert fn was removed in favour of with_client_auth_cert
CryptoProvider trait. ring is now optional, but remains the default provider.There are some related libraries in the rustls ecosystem. If you depend on these libraries, you'll need at least these versions to be compatible with rustls 0.22:
rustls-pki-types = { version = "1" }
webpki-roots = { version = "0.26" }
rustls-webpki = { version = "0.102" }
rustls-pemfile = { version = "2" }
rustls-native-certs = { version = "0.7"}
WebPkiVerifier to WebPkiServerVerifier and add WebPkiClientVerifier.ServerCertVerifier/ClientCertVerifier so the trait doesn't depend on webpki. Instead the previous implementations are exposed as rustls::crypto::verify_tls12_signature, rustls::crypto::verify_tls13_signature and $PROVIDER.signature_verification_algorithms.supported_schemes(), using the crypto provider of your choice. See tlsclient-mio for an example verifier that has been updated for 0.22.WebPkiServerVerifier::builder() and WebPkiClientVerifier::builder().dangerous_configuration, secret_extraction and quic. The API features those previously gated are now available without a crate feature. Types previously gated on the dangerous_configuration feature now appear in danger modules in the same place.rustls::Certificate has been replaced with CertificateDer from the new rustls-pki-types crate. Likewise, rustls::PrivateKey has been replaced with rustls_pki_types::PrivateKeyDer. These types come in both owned and borrowed variants, like std::borrow::Cow, but some uses, like rustls::RootCertStore, required the owned (<'static>) variant.RootCertStore is now passed around wrapped in an Arc, to improve efficiency when creating a different verifier for different servers/clients but with the same roots.RootCertStore::add_parsable_certificates now takes a impl IntoIterator<Item = impl AsRef<[u8]>>.RootCertStore::add_server_trust_anchors became RootCertStore::extend.Debug bound. Please exercise caution in using #[derive(Debug)] on types that contain secret data.ConfigBuilder<ClientConfig, WantsClientCert>::with_single_cert fn was removed in favour of with_client_auth_cert (https://github.com/rustls/rustls/commit/42cda4658f3f5c865a9248803a8a083633525998)| Old | New |
|---|---|
rustls::CipherSuiteCommon |
rustls::crypto::CipherSuiteCommon |
rustls::SupportedKxGroup |
rustls::crypto::SupportedKxGroup |
rustls::cipher_suite::* |
rustls::crypto::ring::cipher_suite::* |
rustls::Ticketer |
rustls::crypto::ring::Ticketer |
rustls::ALL_KX_GROUPS |
rustls::crypto::ring::ALL_KX_GROUPS |
rustls::ALL_CIPHER_SUITES |
rustls::crypto::ring::ALL_CIPHER_SUITES |
rustls::DEFAULT_CIPHER_SUITES |
rustls::crypto::ring::DEFAULT_CIPHER_SUITES |
rustls::kx_group::* |
rustls::crypto::ring::kx_group::* |
rustls::sign::any_ecdsa_type |
rustls::crypto::ring::sign::any_ecdsa_type |
rustls::sign::any_eddsa_type |
rustls::crypto::ring::sign::any_eddsa_type |
rustls::sign::any_supported_type |
rustls::crypto::ring::sign::any_supported_type |
ALL_CIPHER_SUITES (crypto providers)ALL_KX_GROUPS (crypto providers)DEFAULT_CIPHER_SUITES (crypto providers)SECP256R1 (crypto providers)SECP384R1 (crypto providers)any_ecdsa_type (crypto providers)any_eddsa_type (crypto providers)any_supported_type (crypto providers)CipherSuiteCommon (crypto)ClientCertVerified (server::danger)ClientCertVerifier (server::danger)DangerousClientConfig (client::danger)HandshakeSignatureValid (client::danger)ServerCertVerified (client::danger)ServerCertVerifier (client::danger)SupportedKxGroup (crypto)Ticketer (crypto providers)TLS13_AES_128_GCM_SHA256 (crypto providers)TLS13_AES_256_GCM_SHA384 (crypto providers)TLS13_CHACHA20_POLY1305_SHA256 (crypto providers)TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (crypto providers)TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (crypto providers)TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 (crypto providers)TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (crypto providers)TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (crypto providers)TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 (crypto providers)X25519 (crypto providers)WebPkiVerifier (client::WebPkiServerVerifier)Certificate (rustls_pki_types::CertificateDer)PrivateKey (rustls_pki_types::PrivateKeyDer)SignError (crypto::ring::sign::InvalidKeyError)ActiveKeyExchange (crypto)AeadKey (crypto::cipher)Algorithm (quic)ClientCertVerifierBuilder (server)DangerousClientConfigBuilder (client::danger)expand (crypto::tls13)OkmBlock (crypto::tls13)OutputLengthError (crypto::tls13)ServerCertVerifierBuilder (client)TicketSwitcher (ticketer)WebPkiClientVerifier (server)default_provider() (crypto::ring)default_provider() (crypto::aws_lc_rs)HashAlgorithm (crypto::hash)Hash (crypto::hash)Hkdf (crypto::tls13)HkdfExpander (crypto::tls13)HkdfExpanderUsingHmac (crypto::tls13)HkdfUsingHmac (crypto::tls13)Hmac (crypto::hmac)Iv (crypto::cipher)KeyBlockShape (crypto::cipher)Key (crypto::hmac)KeyExchangeAlgorithm (crypto)make_tls12_aad (crypto::cipher)make_tls13_aad (crypto::cipher)MessageDecrypter (crypto::cipher)MessageEncrypter (crypto::cipher)Nonce (crypto::cipher)Nonce (crypto::cipher)OpaqueMessage (crypto::cipher)Output (crypto::hash)PlainMessage (crypto::cipher)Prf (crypto::tls12)PrfUsingHmac (crypto::tls12)SharedSecret (crypto)Tag (crypto::hmac)Tls12AeadAlgorithm (crypto::cipher)UnsupportedOperationError (crypto::cipher)WebPkiSupportedAlgorithms (crypto)GetRandomFailed (crypto)OtherError (top level)UnsupportedOperationError (crypto::cipher)VerifierBuilderError (client)VerifierBuilderError (server)AllowAnyAnonymousOrAuthenticatedClientAllowAnyAuthenticatedClientBulkAlgorithmCertificateTransparencyPolicysupported_sign_tls13WantsTransparencyPolicyOrClientCertOwnedTrustAnchor - use rustls_pki_types::TrustAnchor instead, and replace from_subject_spki_name_constraints with direct assignment to the struct fields.ConfigBuilder::with_safe_defaults - calls to this can simply be deleted since safe defaults are now implicit.SystemTime - certificate verification traits used to reference this type, but now reference rustls_pki_types::UnixTime instead.Iterator in add_parsable_certificates() by @daxpedda in https://github.com/rustls/rustls/pull/1339with_single_cert -> with_client_auth_cert by @cpu in https://github.com/rustls/rustls/pull/1345session_id in HRR by @ctz in https://github.com/rustls/rustls/pull/1374rustls::SupportedCipherSuite (part 1) by @ctz in https://github.com/rustls/rustls/pull/1398RootCertStore and remove expensiveness warnings by @djc in https://github.com/rustls/rustls/pull/1413rustls::SupportedCipherSuite (part deux) by @ctz in https://github.com/rustls/rustls/pull/1401cargo doc comments on private items by @ctz in https://github.com/rustls/rustls/pull/1419KeyLogFile for all examples. by @cpu in https://github.com/rustls/rustls/pull/1423cargo test for all feature combinations by @ctz in https://github.com/rustls/rustls/pull/1427cargo test by @jsha in https://github.com/rustls/rustls/pull/1438CryptoProvider by @ctz in https://github.com/rustls/rustls/pull/1448DangerousClientConfigBuilder, follow-up doc tweaks by @cpu in https://github.com/rustls/rustls/pull/1488secret_extraction feature. by @cpu in https://github.com/rustls/rustls/pull/1484ConnectionTrafficSecrets by @cpu in https://github.com/rustls/rustls/pull/1497--locked from cargo hack daily test by @cpu in https://github.com/rustls/rustls/pull/1500clap 4.4.6 by @ctz in https://github.com/rustls/rustls/pull/1521core::prelude instead of std::prelude by @japaric in https://github.com/rustls/rustls/pull/1524rustls::internal exports by @ctz in https://github.com/rustls/rustls/pull/1544env::var with env::var_os by @paolobarbolini in https://github.com/rustls/rustls/pull/1572SupportedKxGroup & new variant in Error by @Taowyoo in https://github.com/rustls/rustls/pull/1575std::io::BorrowedBuf et al. by @ctz in https://github.com/rustls/rustls/pull/1582max_fragment_size by @ctz in https://github.com/rustls/rustls/pull/1581encrypted_payload_len to MessageEncrypter by @japaric in https://github.com/rustls/rustls/pull/1579quic crate feature by @ctz in https://github.com/rustls/rustls/pull/1594-Z direct-minimal-versions for minimal versions checks by @ctz in https://github.com/rustls/rustls/pull/1601Full Changelog: https://github.com/rustls/rustls/compare/v/0.21.9...v/0.22.0
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.