Skip to content

Rustls 0.23 - #124

Closed
stblr wants to merge 1 commit into
neonmoe:masterfrom
stblr:rustls-0.23
Closed

stblr wants to merge 1 commit into
neonmoe:masterfrom
stblr:rustls-0.23

Conversation

@stblr

@stblr stblr commented Nov 19, 2025

Copy link
Copy Markdown
Contributor

Since Rustls 0.23, the default cryptography provider was changed from aws-lc-rs to ring which could cause compatibility issues.

This PR also replaces rustls-native-certs with rustls-platform-verifier as recommended by Rustls devs.

@stblr

stblr commented Nov 19, 2025

Copy link
Copy Markdown
Contributor Author

Because Cargo really wants to resolve all dependencies, even optional ones, to create the lock file, and because rustls-webpki 0.102 which is needed for all of this uses weak dependencies which are only available in Rust 1.60 in its Cargo.toml, I don't really see a way to update Rustls while keeping the Rust 1.48 MSRV.

@neonmoe

neonmoe commented Nov 21, 2025

Copy link
Copy Markdown
Owner

That is pretty unfortunate. Maybe it's time to finally make a v3, since there could be dependents that are assuming all 2.x versions work with 1.48, as that's what's promised in the readme, and I wouldn't like to break their builds.

Another option would be to allow multiple versions of rustls, but I imagine that would require conditional compilation based on the version of rustls used, which I don't think can be done.

Open to any ideas. In any case, I'll try to come up with some solution that would allow keeping the msrv, because bumping the major version would be a pretty drastic change. So please hold, I'll come back to this in a while.

@MaxFangX MaxFangX mentioned this pull request Mar 21, 2026
@neonmoe

neonmoe commented Apr 12, 2026

Copy link
Copy Markdown
Owner

Sorry about the wait, I've decided on bumping the major version to 3.0. While doing the other changes, there was a minor conflict introduced, so I went ahead and merged this manually with the conflict fixed: b5571be. Thanks for the PR!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants