ChaCha20: Support custom initial counter through 16-byte IV #2
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
ruiliio
force-pushed
the
chacha20_16
branch
2 times, most recently
from
85766b1 to
db6ae05
Compare
Signed-off-by: ruiliio <ruili3422@gmail.com>
Signed-off-by: ruiliio <ruili3422@gmail.com>
Signed-off-by: ruiliio <ruili3422@gmail.com>
Signed-off-by: ruiliio <ruili3422@gmail.com>
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.
Description
Add support for setting an arbitrary initial counter value for ChaCha20 via psa_cipher_set_iv() by passing a 16-byte IV. The first 4 bytes (encoded as little-endian) set the counter, and the remaining 12 bytes set the nonce, as specified in the PSA Crypto API.
Fix #
PR checklist