[TR3FIR-237] Fix AES CCM breaking authentication #18
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
grochowski-withintent
requested review from
DavidZemon,
mattcaron-token,
lukasz-zajac,
BednarzAleksander,
a user,
mchodzi-intent and
piotrkrygier-intent
ghost
approved these changes
Jul 8, 2024
TylerGajewski-Token
approved these changes
Jul 8, 2024
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.
Overview
This change fixes AES CCM breaking our First Time Setup procedure.
Turns out it was down to resetting the peripheral too rarely, since we have only been doing it on the creation of the
Aesstruct, not on creation of every algorithm instance (AesCcmstruct).Changes
Add
rcc::enable_and_resetcall while constructing newAesCcminstance.