Support for Passkey Entry (pairing) #712
Open
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
added 5 commits
November 21, 2017 17:39
… (i.e., from noble), so the peripheral device needs to require MITM for this to work.
projectbtle
changed the title
|
Any progress on merging that? |
|
Hi all, Thanks for tackling this issue, is there something preventing it to be merged? |
|
Please forward change to downstream fork: |
|
Has anybody else been able to test the functionality? |
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.
Modified the IO capabilities in pairing request to KeyboardOnly. MITM is not required from our end (i.e., from noble), so the peripheral device needs to require MITM for this to work. If the peripheral does not require MITM, then the code defaults to Just Works.