Closed joshtriplett closed 7 months ago
This PR should wait for a new major version of aws-lc-rs that drops those deprecated functions.
Thanks for the PR! We don't have plans to publish another major versions on our roadmap. When we eventually do publish a new major version, we will likely drop untrusted
as a dependency.
Unfortunately, (although it's deprecated) I don't see a way for us to merge this without breaking some existing consumers.
As a possible workaround, you could disable default features for aws-lc-rs
and only add back the aws-lc-sys
feature. (The untrusted
crate is only needed when the ring-io
feature is enabled.)
@justsmth Unfortunately, rustls is one of the crates that depends on it with default features enabled.
I've submitted https://github.com/rustls/rustls/pull/1768 to attempt to fix that.
Downstream PR merged. Closing this PR.
Description of changes:
This upgrades the version of the
untrusted
crate to the latest 0.9, to avoid duplicate dependencies when building aws-lc-rs in a project with other dependencies onuntrusted
.Call-outs:
A few deprecated functions take
untrusted::Input
as a parameter directly. This PR should wait for a new major version of aws-lc-rs that drops those deprecated functions. (Alternatively, it'd be possible to have anuntrusted07
feature flag that continues depending onuntrusted
0.7 for the sole purpose of the API of those deprecated funtions, but that doesn't seem worthwhile here.)As far as I can tell, no non-deprecated APIs would be affected, which means future upgrades to untrusted would not have this issue.
Testing:
Builds and passes
cargo test
, with and without thering-io
andring-sig-verify
feature flags set.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and the ISC license.