chacha20: adding 64-bit counter support #359
Open
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.
Addresses #334
The constant booleans in the backends should be evaluated at compile-time... but there's a slight chance that I could write a test for the
ChaCha20Rng
that fails onaarch64
with neon. The originaladd64
macro does what the name suggests, it adds vectors in a 64-bit fashion, meaning that it could perform addition incorrectly when the counter should be 32 bits and the counter is exceeding theu32::MAX
.This shouldn't be an issue with the
ChaCha20
cipher sincecipher
panics when the counter will exceedu32::MAX
, butChaCha20Rng
wraps around and is currently supposed to use a 32-bit counter. I'm going to write one more test to see if I can get it to fail, and if it fails, then I'll probably need to changeadd64
to accept a boolean for performing 32-bit or 64-bit addition.