This repository has been archived by the owner on Mar 5, 2024. It is now read-only.
Fix to AES-CMAC bug #34
Open
Conversation
This file contains 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
cmac_mode: s/const static/static const/
…ed if the second to last call to update `leftover` and the final update call `remaining` equalled the size of the AES block.
mczraf
force-pushed
the
master
branch
2 times, most recently
from
4fb05d5
to
323cd15
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
My colleague @mpp-anasa and I discovered that in certain scenarios where
tc_cmac_updateis called multiple times, an extra padding block can be created causing an invalid MAC to be generated.I've included a modified version of the 512bit test that will fail on the existing version.