Hi Amr, Nimble does support OOB for Legacy and Secure Connections Pairing. In both cases you just need to provide OOB (TK) data exchanged by other means e.g. NFC to the NimBLE stack using "int ble_sm_inject_io(uint16_t conn_handle, struct ble_sm_io *pkey)".
For Secure Connection make sure to set MYNEWT_VAL BLE_SM_SC to 1. Hope that helps Best Łukasz On Thu, 25 Apr 2019 at 22:19, Amr Bekhit <amrbek...@gmail.com> wrote: > Hello all, > > I'm interested in using OOB pairing over NFC to connect my peripheral > device to a master (an Android phone in this case). The NFC Forum has a > specification ( > > https://nfc-forum.org/our-work/specifications-and-application-documents/application-documents/ > ) > which dictates how two NFC-capable BLE devices can exchange key > information. As far as I can tell from the specification, for BLE, the > peripheral can send its temporary key (TK) via NFC to the central. > Presumably, both parties would then enter that key into their Bluetooth > stacks and continue the connection process from that point on using just > BLE. > > Regarding this, I have the following question. Using the nimble stack, how > can we get the peripheral to > a) generate a TK and then enter that TK into the stack. > b) continue the connection from that point forwards? > > I noticed that the aforementioned specification document doesn't seem to > mention BLE Secure Connections - the TK is an aspect of BLE legacy pairing. > Does anyone know if there is a version of the standard that works with BLE > Secure Connection keys? Perhaps the assumption is that NFC pairing provides > the required identify verification and MITM protection that is provided by > BLE SC and so BLE Legacy can be used with the same level of security? > > Amr >
