- add a security level for writing the cccd (reading is always allowed) #62
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 might be related to #10:
It would be good to set the security level for writing a cccd.
Example:
You have a service for bi-directional communication. The service has a notification characteristic for receiving data and a write-no-response (for maximum throughput) for sending data. The communication should be encrypted.
Currently there is no trigger to enforce encryption even if both characteristics have a security level > SecurityLevel.OPEN
Being able to assign e.g. SecurityLevel.JUST_WORKS for writing to the cccd of the notification would trigger a "Insufficient Authentication" response which then results in a pairing/bonding