WarrenS

What is the release timeline looking like?

> Is it possible to make a new full release now with this fix, and then add any other pending changes to the next full release? In case the release...

Check this out: https://docs.rs/rustls/latest/rustls/crypto/struct.CryptoProvider.html#using-the-per-process-default-cryptoprovider Let me know if that doesn't work and we can go from there. If it does work we can add that one liner to the examples.

> > see above comments that below has to call > > > > > > ``` > > > let crypto_provider = rustls::crypto::aws_lc_rs::default_provider(); > > > crypto_provider.install_default().unwrap(); > >...

> @LockedThread , can we make this call inside our tls setup, so that user does not need to do that? The point of the CryptoProvider system is so that...

> I treat backward-compatible seriously, so I think better to make it v2.0.0 to follow semantic versioning Do that

This might provide a good middle ground: https://github.com/seanmonstar/reqwest/pull/2225 Please also look at this: https://github.com/rustls/hyper-rustls/blob/main/examples/server.rs https://github.com/webrtc-rs/webrtc/issues/567 https://github.com/rustls/rustls/issues/1877 https://github.com/launchbadge/sqlx/pull/3399

> @durch I understand project maintenance happens "[every quarter or so](https://github.com/durch/rust-s3/issues/390#issuecomment-2172383719)", but do you know when you will be back to merge small things like these? ^