Bluetooth: CSIP: Use bt_crypto_aes_cmac instead of own #67151
Merged
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
zephyrbot
requested review from
asbjornsabo,
Casper-Bonde-Bose,
fredrikdanebjer,
jhedberg,
kruithofa,
larsgk,
MariuszSkamra and
sjanc
larsgk
previously approved these changes
Jan 15, 2024
Instead of reimplementing the aes_cmac function, CSIP will now use the bt_crypto_aes_cmac function. Signed-off-by: Emil Gydesen <[email protected]>
Thalley
force-pushed
the
coverity_248341
branch
from
ffe9deb to
f72baa5
Compare
|
Rebased to solve merge conflicts |
jhedberg
approved these changes
Jan 16, 2024
kruithofa
approved these changes
Jan 16, 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.
Instead of reimplementing the aes_cmac function, CSIP will now use the bt_crypto_aes_cmac function.
fixes #65604