How to: 4.2 security and OOB

RE: How to: 4.2 security and OOB

Petter Myhre — Thu, 19 May 2016 14:26:46 GMT

OOB should be set on both sides. Like under OOB bonding here.

When you bond you will get the BLE_GAP_EVT_AUTH_KEY_REQUEST event on both sides, and you include the OOB key with sd_ble_gap_auth_key_reply() on both sides.

Please check this and this.

RE: How to: 4.2 security and OOB

Jari — Thu, 19 May 2016 12:55:54 GMT

I have been looking at the “migrate from Device Manager to Peer Manager”. I am net to Nordic devices and I know nothing about the Device manager. I need to generate the OOB data on the peripheral device. I guess the NFC examples pretty much covers that.

I need to handover this OOB data to the Peer Manager on the central device – how do I do that on s132?

I need to setup the Security parameters (pm_sec_params_set): I guess that oob should be set on the Central device as it is supposed to receive OOB date and that oob is NOT set on the Peripheral device as it will not receive any OOB data.

RE: How to: 4.2 security and OOB

Petter Myhre — Wed, 18 May 2016 15:30:36 GMT

You can use the Peer Manager to handle bonding. What is failing? What have you done? Have you tried to follow this tutorial?