[jira] [Commented] (MYNEWT-750) BLE Host - Ignore pairing attempt from already bonded peer
[ https://issues.apache.org/jira/browse/MYNEWT-750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052364#comment-16052364 ] ASF subversion and git services commented on MYNEWT-750: Commit 9572c52fa2a0c67b6a2a15ec3dca4501fd24a29b in incubator-mynewt-core's branch refs/heads/master from [~ccollins476] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=9572c52 ] MYNEWT-750 BLE Host - Persist SC flag for bonds. > BLE Host - Ignore pairing attempt from already bonded peer > -- > > Key: MYNEWT-750 > URL: https://issues.apache.org/jira/browse/MYNEWT-750 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) > Components: Nimble >Reporter: Christopher Collins >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > (Pull request: https://github.com/apache/incubator-mynewt-core/pull/287) > 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: > ## Retry: Return BLE_GAP_REPEAT_PAIRING_RETRY after deleting the conflicting > bond. The stack will verify the bond has been deleted and continue the > pairing procedure. If the bond is still present, this event will be reported > again. > ## Ignore: Return BLE_GAP_REPEAT_PAIRING_IGNORE. The stack will silently > ignore the pairing request. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-750) BLE Host - Ignore pairing attempt from already bonded peer
[ https://issues.apache.org/jira/browse/MYNEWT-750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052365#comment-16052365 ] ASF subversion and git services commented on MYNEWT-750: Commit 6e380728c1382e679e2c6967e6820dfc4f48b116 in incubator-mynewt-core's branch refs/heads/master from [~ccollins476] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=6e38072 ] MYNEWT-750 - Authenticated flag incorrect. We would persist the authenticated flag if either peer supported authentication. We should only persist it if both support it. > BLE Host - Ignore pairing attempt from already bonded peer > -- > > Key: MYNEWT-750 > URL: https://issues.apache.org/jira/browse/MYNEWT-750 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) > Components: Nimble >Reporter: Christopher Collins >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > (Pull request: https://github.com/apache/incubator-mynewt-core/pull/287) > 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: > ## Retry: Return BLE_GAP_REPEAT_PAIRING_RETRY after deleting the conflicting > bond. The stack will verify the bond has been deleted and continue the > pairing procedure. If the bond is still present, this event will be reported > again. > ## Ignore: Return BLE_GAP_REPEAT_PAIRING_IGNORE. The stack will silently > ignore the pairing request. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-750) BLE Host - Ignore pairing attempt from already bonded peer
[ https://issues.apache.org/jira/browse/MYNEWT-750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052363#comment-16052363 ] ASF subversion and git services commented on MYNEWT-750: Commit cb7782d7b4f322799510d293a23a65061244f6c8 in incubator-mynewt-core's branch refs/heads/master from [~ccollins476] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=cb7782d ] MYNEWT-750 Fix some coding style issues. > BLE Host - Ignore pairing attempt from already bonded peer > -- > > Key: MYNEWT-750 > URL: https://issues.apache.org/jira/browse/MYNEWT-750 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) > Components: Nimble >Reporter: Christopher Collins >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > (Pull request: https://github.com/apache/incubator-mynewt-core/pull/287) > 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: > ## Retry: Return BLE_GAP_REPEAT_PAIRING_RETRY after deleting the conflicting > bond. The stack will verify the bond has been deleted and continue the > pairing procedure. If the bond is still present, this event will be reported > again. > ## Ignore: Return BLE_GAP_REPEAT_PAIRING_IGNORE. The stack will silently > ignore the pairing request. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-750) BLE Host - Ignore pairing attempt from already bonded peer
[ https://issues.apache.org/jira/browse/MYNEWT-750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052366#comment-16052366 ] ASF subversion and git services commented on MYNEWT-750: Commit b6d96411b6af18360c5a8fc4f8d31d473b99118a in incubator-mynewt-core's branch refs/heads/master from [~ccollins476] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=b6d9641 ] MYNEWT-750 BLE Host - Ignore pair from bonded peer If a device is already bonded, ;he 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. New behavior in such a scenario: 1. Host notifies application of the duplicate pairing attempt via the gap event callback. The callback specifies a new event code (BLE_GAP_EVENT_REPEAT_PAIRING) that specifically indicates a duplicate pairing attempt. 2. The gap event callback returns an error code indicating which of the following behaviors to perform: a. Retry: Return BLE_GAP_REPEAT_PAIRING_RETRY after deleting the conflicting bond. The stack will verify the bond has been deleted and continue the pairing procedure. If the bond is still present, this event will be reported again. b. Ignore: Return BLE_GAP_REPEAT_PAIRING_IGNORE. The stack will silently ignore the pairing request. > BLE Host - Ignore pairing attempt from already bonded peer > -- > > Key: MYNEWT-750 > URL: https://issues.apache.org/jira/browse/MYNEWT-750 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) > Components: Nimble >Reporter: Christopher Collins >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > (Pull request: https://github.com/apache/incubator-mynewt-core/pull/287) > 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: > ## Retry: Return BLE_GAP_REPEAT_PAIRING_RETRY after deleting the conflicting > bond. The stack will verify the bond has been deleted and continue the > pairing procedure. If the bond is still present, this event will be reported > again. > ## Ignore: Return BLE_GAP_REPEAT_PAIRING_IGNORE. The stack will silently > ignore the pairing request. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-750) BLE Host - Ignore pairing attempt from already bonded peer
[ https://issues.apache.org/jira/browse/MYNEWT-750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052367#comment-16052367 ] ASF subversion and git services commented on MYNEWT-750: Commit 729c34e4e2f692a9c5fc4a8d4024b91eff856358 in incubator-mynewt-core's branch refs/heads/master from [~ccollins476] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=729c34e ] MYNEWT-750 Fix build when SM disabled. > BLE Host - Ignore pairing attempt from already bonded peer > -- > > Key: MYNEWT-750 > URL: https://issues.apache.org/jira/browse/MYNEWT-750 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) > Components: Nimble >Reporter: Christopher Collins >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > (Pull request: https://github.com/apache/incubator-mynewt-core/pull/287) > 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: > ## Retry: Return BLE_GAP_REPEAT_PAIRING_RETRY after deleting the conflicting > bond. The stack will verify the bond has been deleted and continue the > pairing procedure. If the bond is still present, this event will be reported > again. > ## Ignore: Return BLE_GAP_REPEAT_PAIRING_IGNORE. The stack will silently > ignore the pairing request. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-750) BLE Host - Ignore pairing attempt from already bonded peer
[ https://issues.apache.org/jira/browse/MYNEWT-750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052368#comment-16052368 ] ASF subversion and git services commented on MYNEWT-750: Commit 79fcf1d2a81d3487f237d696c69d6a904bb94ec5 in incubator-mynewt-core's branch refs/heads/master from [~ccollins476] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=79fcf1d ] MYNEWT-750 Handle repeat pairing in e.g. apps. > BLE Host - Ignore pairing attempt from already bonded peer > -- > > Key: MYNEWT-750 > URL: https://issues.apache.org/jira/browse/MYNEWT-750 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) > Components: Nimble >Reporter: Christopher Collins >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > (Pull request: https://github.com/apache/incubator-mynewt-core/pull/287) > 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: > ## Retry: Return BLE_GAP_REPEAT_PAIRING_RETRY after deleting the conflicting > bond. The stack will verify the bond has been deleted and continue the > pairing procedure. If the bond is still present, this event will be reported > again. > ## Ignore: Return BLE_GAP_REPEAT_PAIRING_IGNORE. The stack will silently > ignore the pairing request. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MYNEWT-758) BLE Host - OOB security for SC
[ https://issues.apache.org/jira/browse/MYNEWT-758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Szymon Janc updated MYNEWT-758: --- Fix Version/s: (was: v1_1_0_rel) v1_2_0_rel > BLE Host - OOB security for SC > -- > > Key: MYNEWT-758 > URL: https://issues.apache.org/jira/browse/MYNEWT-758 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) > Components: Nimble >Reporter: Christopher Collins >Assignee: Szymon Janc > Fix For: v1_2_0_rel > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MYNEWT-766) LE Periodic scanning
[ https://issues.apache.org/jira/browse/MYNEWT-766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Szymon Janc updated MYNEWT-766: --- Fix Version/s: (was: v1_1_0_rel) v1_2_0_rel > LE Periodic scanning > > > Key: MYNEWT-766 > URL: https://issues.apache.org/jira/browse/MYNEWT-766 > Project: Mynewt > Issue Type: Sub-task > Security Level: Public(Viewable by anyone) > Components: Nimble >Reporter: Szymon Janc >Assignee: Łukasz Rymanowski > Fix For: v1_2_0_rel > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MYNEWT-716) LE Periodic Advertising
[ https://issues.apache.org/jira/browse/MYNEWT-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Szymon Janc updated MYNEWT-716: --- Fix Version/s: (was: v1_1_0_rel) v1_2_0_rel > LE Periodic Advertising > > > Key: MYNEWT-716 > URL: https://issues.apache.org/jira/browse/MYNEWT-716 > Project: Mynewt > Issue Type: Sub-task > Security Level: Public(Viewable by anyone) > Components: ble, Nimble >Reporter: Szymon Janc >Assignee: Szymon Janc > Fix For: v1_2_0_rel > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (MYNEWT-785) Remove support for 1MHz clock in nimble. We stick to Low Power RTC
Łukasz Rymanowski created MYNEWT-785: Summary: Remove support for 1MHz clock in nimble. We stick to Low Power RTC Key: MYNEWT-785 URL: https://issues.apache.org/jira/browse/MYNEWT-785 Project: Mynewt Issue Type: Sub-task Security Level: Public (Viewable by anyone) Components: Nimble Reporter: Łukasz Rymanowski Assignee: Andrzej Kaczmarek Fix For: v1_1_0_rel -- This message was sent by Atlassian JIRA (v6.4.14#64029)
