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/06/26 21:48:00 UTC

[jira] [Resolved] (MYNEWT-751) BLE Host - Policy for SM key overflow

     [ https://issues.apache.org/jira/browse/MYNEWT-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christopher Collins resolved MYNEWT-751.
----------------------------------------
    Resolution: Fixed

> BLE Host - Policy for SM key overflow
> -------------------------------------
>
>                 Key: MYNEWT-751
>                 URL: https://issues.apache.org/jira/browse/MYNEWT-751
>             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/279)
> The BLE host needs a way to handle the case where a security store write fails because the maximum number of entries have already been written.  Currently, the host simply fails to persist the record and returns an error code.
> I propose the following behavior in such a scenario:
> # Host checks that there is sufficient storage for a bond before it starts a pairing operation.  Any currently-active pairing procedures should be included in the total number of bonds.
> # If there is insufficient space, host notifies application of the issue via a callback.
> # The callback would return an error code indicating which of the following behaviors to perform:
> ## Reject the pairing request.
> ## Proceed with the pairing operation (presumably the application would delete a security record to make room before returning from the callback).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)