Allow requiring pairing for GATT notifications/indications #43
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
The 'properties' macro had too much complexity/flexibility that wasn't being used, making it difficult to add a new feature.
In BlueZ versions greater than 5.61, the `encrypt-authenticated-notify/indicate`, `secure-notify/indicate`, and `encrypt-notify/indicate` flags are available to require certain levels of security for server-initiated updates. This commit introduces a breaking API change to support these flags. See BlueZ commit 61576a8e78c321d67412c6a49ef293c94ec8a235 for details.
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.
Add support for the x-indicate and x-notify flags in BlueZ 5.62. This requires a breaking API change