Explicitly don't allow buffers aliasing in ctr-drbg implementation #2458
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 of changes:
In e.g.
CTR_DRBG_init
argumentsentropy
andpersonalization
are effectively xor'dentropy XOR personalization
. If the two arguments were to ever alias, the resulting XOR would be0
and therefore predictable (if the aliasing would turn out to be predictable, of course).This is theoretical, but prevent it explicitly anyway.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and the ISC license.