Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use aws-lc-rs in place of ring #825

Merged
merged 4 commits into from
Sep 26, 2024

Conversation

ginglis13
Copy link
Contributor

Issue #, if available:

#824

Description of changes:

Migrate from ring to aws-lc-rs. Testing thus far has been simply cargo test and make integ.

The untrusted crate that tough depends on is downgraded to 0.7.1 as a consequence of aws-lc-rs pinning to this version of the crate; it is now required in tough by the ring-io default feature of aws-lc-rs, which provides aws_lc_rs::io::der.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@ginglis13
Copy link
Contributor Author

^ force pushed a rebase

@ginglis13
Copy link
Contributor Author

^ skip untrusted v0.7.1 in license check; also bring Cargo.lock up to speed

@ginglis13 ginglis13 requested a review from jpculp September 13, 2024 17:51
Enable `prebuilt-nasm` feature for Windows.

Signed-off-by: Gavin Inglis <[email protected]>
Enable `prebuilt-nasm` feature for Windows

Signed-off-by: Gavin Inglis <[email protected]>
aws-lc-rs pins to untrusted v0.7.1; skip this crate in license checks

Signed-off-by: Gavin Inglis <[email protected]>
@ginglis13 ginglis13 force-pushed the migrate-ring-aws-lc-rs branch from f4d2a8b to f8f9b7e Compare September 13, 2024 18:24
@ginglis13 ginglis13 merged commit bbc3509 into awslabs:develop Sep 26, 2024
7 checks passed
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.

3 participants