[5.9] Update to swift-crypto 2.4.1 #6433
Merged
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.
Cherry pick #6431 to 5.9
Motivation:
swift-crypto 2.4.1 includes updates in BoringSSL that cause
Unsafe*Pointer<EVP_PKEY>
becomeOpaquePointer
and without this code adjustment SwiftPM fails to build witherror: cannot find type 'EVP_PKEY' in scope
.Modifications:
Unsafe*Pointer<EVP_PKEY>
withOpaquePointer
.