Update to CryptoKit 2023 final API #199
Merged
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
Motivation This patch brings us up-to-date with CryptoKit's final 2023 API form. Modifications Slight tweak to exporter secrets for HPKE to match final spec. New representation for SecureBytes when empty. Result We're ready for the future
Lukasa
added
the
⚠️ needs-major-version-bump
glbrntt
approved these changes
Sep 13, 2023
FranzBusch
approved these changes
Sep 13, 2023
dnadoba
approved these changes
Sep 13, 2023
|
API breakage is expected. |
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.
Motivation
This patch brings us up-to-date with CryptoKit's final 2023 API form.
Modifications
Slight tweak to exporter secrets for HPKE to match final spec. New representation for SecureBytes when empty.
Result
We're ready for the future