Remove aad parameter from HPKE one-shot public API #14203
+46
−26
Conversation
This file contains hidden or 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
Per RFC 9180 Section 8.1, applications using single-shot APIs should use the info parameter for auxiliary authenticated information rather than aad. This change: - Creates internal _encrypt/_decrypt methods that accept aad for running RFC test vectors - Removes aad parameter from public encrypt/decrypt methods - Updates tests to use internal API for vector validation - Updates documentation to reflect the API change - Adds CHANGELOG entry for HPKE support Fixes #14073
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.
Per RFC 9180 Section 8.1, applications using single-shot APIs should use the info parameter for auxiliary authenticated information rather than aad. This change:
Fixes #14073