Use CryptoKit to derive the EC public key during PKCS8 import #74
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
kdubb
force-pushed
the
feature/pkcs8-import-export
branch
2 times, most recently
from
c26e992
to
a371c02
Compare
This ensures the PKCS8 import works when the encoded without the optional public key point, since the full public key point and private key are required for `SecKeyCreateWithData`.
kdubb
force-pushed
the
feature/pkcs8-import-export
branch
from
a371c02
to
f4e128f
Compare
|
Kudos, SonarCloud Quality Gate passed! |
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.
This ensures the PKCS8 import works when encoded without the optional public key point, since the full public key point and private key are required for
SecKeyCreateWithData.