I've been playing around further. After including the
@apache-mynewt-nimble/nimble/host/store/config package, when
attempting to bond via my phone I now get request for a passkey (I've
configured the bluetooth device to indicate that it has a display
only). I'm trying to figure out how to tell the nimble stack what the
passkey is. When the BLE GAP callback function is called with
BLE_GAP_EVENT_PASSKEY_ACTION, I've tried to use the ble_sm_inject_io
function to specify a passkey, but this doesn't seem to have any
effect - the bonding still fails. Any thoughts?
On Fri, 6 Jul 2018 at 15:43, Amr Bekhit <amrbek...@gmail.com> wrote:
>
> Hello all,
>
> Is there any documentation regarding the security aspects of Nimble
> (.e.g pairing, bonding, passkeys etc)? The mynewt documentation covers
> the basic advertising and GATT systems quite well, and am happily
> using those, but I'm struggling to find any information on the
> security side of things.
>
> Amr
