briansmith/ring#2414

Currently ring is the default backend for ureq via rustls. This is something we might need to revise. This is not a breaking change because we got the TlsConfig abstraction between us and the crypto provider.

We also clearly point out that the default crypto provider might change:

ureq does not guarantee to default to ring indefinitely. rustls as a feature flag will always work, but the specific crypto backend might change in a minor version.

I'm hopeful there one day will be a TLS library that is 100% Rust, but the natural choice at this point would be to switch rustls to aws-lc-rs.

I'd love to hear if any users of ureq have thoughts on this.