Bluetooth: Mesh: Fix dev key selection in SAR Cfg Client #69600
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
For dev key encrypiton, BT_MESH_KEY_DEV_REMOTE should be used instead of BT_MESH_KEY_DEV regardless of whether the destination is a local element or remote. BT_MESH_MSG_CTX_INIT_DEV macro selects correct key. Signed-off-by: Pavel Vasilyev <[email protected]>
zephyrbot
requested review from
akredalen,
alxelax,
Andrewpini,
jhedberg and
LingaoM
Andrewpini
approved these changes
Feb 29, 2024
jhedberg
approved these changes
Feb 29, 2024
alxelax
approved these changes
Feb 29, 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.
For dev key encrypiton, BT_MESH_KEY_DEV_REMOTE should be used instead of BT_MESH_KEY_DEV regardless of whether the destination is a local element or remote.
BT_MESH_MSG_CTX_INIT_DEV macro selects correct key.