fix: explicitly choose aws_lc_rs as the crypto provider #266
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Yeah, good chat w.r.t ring vs aws-lc-rs ... still failing tests so we'll need to dig into:
|
mmalenic
force-pushed
the
feat/c4gh-misc
branch
from
7d3fbd7
to
5b25d56
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
aws_lc_rsas the crypto provider in all application binariesI can't figure out which crate is suddenly enabling
ringas a dependency inrustls(is it reqwest?), but I think it's probably worthwhile to specify this explicitly anyway.This fixes failed build from #265.