Update to btstack v1.8.2#2996
Merged
kilograham merged 2 commits intoJun 19, 2026
Merged
Conversation
Contributor
Author
|
ready now |
51fff5e to
6d22f37
Compare
Contributor
Author
|
@kilograham Can we merge this? |
kilograham
approved these changes
Jun 19, 2026
kilograham
left a comment
Contributor
There was a problem hiding this comment.
Yeah last I looked it was a draft 🤣
This file contains hidden or 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
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.
This version enables security in the default configuration of the btstack examples. You will need to delete the device and repeat pairing every time as "bonding" is not enabled.
Disabling bonding helps to allow for repeated testing. It can be enabled by adding SM_AUTHREQ_BONDING to the authentication requirements like this:
sm_set_authentication_requirements(X | SM_AUTHREQ_BONDING)
Fixes #2964