You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@mynewt.apache.org by "Christopher Collins (JIRA)" <ji...@apache.org> on 2017/05/11 01:47:04 UTC

[jira] [Created] (MYNEWT-750) BLE Host - Reject pairing attempt from already bonded peer

Christopher Collins created MYNEWT-750:
------------------------------------------

             Summary: BLE Host - Reject pairing attempt from already bonded peer
                 Key: MYNEWT-750
                 URL: https://issues.apache.org/jira/browse/MYNEWT-750
             Project: Mynewt
          Issue Type: Bug
          Components: Nimble
            Reporter: Christopher Collins
             Fix For: v1_1_0_rel


If a device is already bonded, the host should not allow the same device to pair again.  Currently, the host blindly proceeds with the pairing operation.  This should not be allowed because the second peer could be an imposter masquerading as the original.

I propose the following behavior in such a scenario:
# Host notifies application of the duplicate pairing attempt via the gap event callback.  The callback would specify a new event code that specifically indicates a duplicate pairing attempt.
# The gap event callback would return an error code indicating which of the following behaviors to perform:
## Reject the pairing request.
## Delete the original bond and proceed with the pairing operation.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)