Is your feature request related to a problem? Please describe.
This crate currently hardcodes ring as its only supported crypto implementation. The ring crate is in maintenance mode and much of the ecosystem has moved over to the better supported aws-lc-rs crate.
This is a challenge for my team, as we maintain a number of Rust services in production. We ban ring from our dependency tree to ensure we're using a single crypto provider across the board. That gives us less risk, less complexity, and faster builds.
Describe the solution you'd like
Support using aws-lc-rs as a rustls crypto provider.
There are a number of ways to enable this. Two notable options are a 'no provider' feature that allows users to set the global rustls crypto provider, or by providing a specific aws-lc-rs feature.
Additional context
This may be incoming by default in a future reqwest version. More info in Sean McArthur's blog post here.
Is your feature request related to a problem? Please describe.
This crate currently hardcodes
ringas its only supported crypto implementation. Theringcrate is in maintenance mode and much of the ecosystem has moved over to the better supportedaws-lc-rscrate.This is a challenge for my team, as we maintain a number of Rust services in production. We ban
ringfrom our dependency tree to ensure we're using a single crypto provider across the board. That gives us less risk, less complexity, and faster builds.Describe the solution you'd like
Support using
aws-lc-rsas arustlscrypto provider.There are a number of ways to enable this. Two notable options are a 'no provider' feature that allows users to set the global rustls crypto provider, or by providing a specific
aws-lc-rsfeature.Additional context
This may be incoming by default in a future
reqwestversion. More info in Sean McArthur's blog post here.