Change IV length range for XChaCha20 cipher#1084
Open
james-kwong wants to merge 1 commit intokrzyzanowskim:mainfrom
Open
Change IV length range for XChaCha20 cipher#1084james-kwong wants to merge 1 commit intokrzyzanowskim:mainfrom
james-kwong wants to merge 1 commit intokrzyzanowskim:mainfrom
Conversation
Updated the valid range of initialization vector lengths for the XChaCha20 cipher from 12 bytes to 24 bytes, which is the correct value. Signed-off-by: James Kwong <161430705+james-kwong@users.noreply.github.com>
Owner
|
why? this need more merit to discuss |
Author
|
I thought the ChaCha20 cipher used a 12 byte nonce, whereas XChaCha20 used 24 bytes? |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Updated the valid range of initialization vector lengths for the XChaCha20 cipher from 12 bytes to 24 bytes, which is the correct value.
Checklist: