Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bluetooth: Mesh: Account for ASZMIC in encrypt #29739

Merged
merged 1 commit into from Nov 3, 2020

Conversation

@trond-snekvik
Copy link
Contributor

@trond-snekvik trond-snekvik commented Nov 3, 2020

The decision to set aszmic = 1 in the net_tx structure was made after
the variable was passed to the crypto context, creating a discrepancy
between the two when aszmic is 1.

Extracts transport encryption to a separate function.

Signed-off-by: Trond Einar Snekvik Trond.Einar.Snekvik@nordicsemi.no

The decision to set aszmic = 1 in the net_tx structure was made after
the variable was passed to the crypto context, creating a discrepancy
between the two when aszmic is 1.

Extracts transport encryption to a separate function.

Signed-off-by: Trond Einar Snekvik <Trond.Einar.Snekvik@nordicsemi.no>
Copy link
Member

@jhedberg jhedberg left a comment

Do we want to backport this?

@trond-snekvik
Copy link
Contributor Author

@trond-snekvik trond-snekvik commented Nov 3, 2020

Do we want to backport this?

No need, the bug appeared in #28511, which went in after 2.4

@LingaoM
LingaoM approved these changes Nov 3, 2020
@jhedberg jhedberg merged commit 2fb56ba into zephyrproject-rtos:master Nov 3, 2020
7 checks passed
7 checks passed
@github-actions
Backport
Details
@github-actions
Backport
Details
@github-actions
Backport
Details
@github-actions
Run compliance checks on patch series (PR)
Details
@github-actions
triage
Details
@github-actions
Scan code for licenses
Details
buildkite/zephyr Build #12519 passed (58 minutes, 3 seconds)
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

4 participants