secure connect 52832

RE: secure connect 52832

FormerMember — Wed, 14 Mar 2018 09:56:54 GMT

I would recommend you to install micro-ecc and test the example, it only takes a few minutes to do so.

The NFC data is set in nfc_ble_pair_init() -->nfc_ble_pair_data_set().

RE: secure connect 52832

AndSin — Tue, 13 Mar 2018 11:12:47 GMT

is it really difficult to make two examples (central and periphary) for a secure connection using oob? I can not use the proposed examples because they require an additional library.But it's easy to do two main files with all the settings.Please do it. On your site a huge number of questions on this topic.

RE: secure connect 52832

AndSin — Tue, 13 Mar 2018 10:15:22 GMT

but... where oob is initialized? (in global struct or functions?)

RE: secure connect 52832

AndSin — Tue, 13 Mar 2018 10:09:11 GMT

Yes look up (log from nRF)

<info> app: BLE_GAP_EVT_SEC_PARAMS_REQUEST, bond 1 mitm 1 oob 1

RE: secure connect 52832

FormerMember — Tue, 13 Mar 2018 09:31:40 GMT

PM_EVT_CONN_SEC_PARAMS_REQ is "peer managers" handling of the event BLE_GAP_EVT_SEC_PARAMS_REQUEST. If you are using peer_manager, which we recommend, handling of the pairing/bonding is done by that module and not something that you should take care of. What you need to do is to make sure that the application has the correct security settings according to what security level you want to use, and that pairing/bonding will be initiated.

RE: secure connect 52832

FormerMember — Tue, 13 Mar 2018 09:19:29 GMT

In the nRF-nRF connction, there is no security setup in the connection. From the above log, I suspect that the peripheral (BlueGiga) initiates pairing by sending a "security request", where the nRF52832 ble_app_hrs peripheral doesn't.

In the case with BlueGiga, does the central receive the event BLE_GAP_EVT_SEC_REQUEST?

RE: secure connect 52832

AndSin — Mon, 12 Mar 2018 14:16:18 GMT

where the oob data is stored ?

what should the program respond to the event (on periph device) on PM_EVT_CONN_SEC_PARAMS_REQ

sd_ble_gap_sec_params_reply(current_connection, BLE_GAP_SEC_STATUS_SUCCESS, ???, ???)

RE: secure connect 52832

AndSin — Mon, 12 Mar 2018 10:48:17 GMT

This is LOG nRF52832(central) connect to BlueGiga: (all working GOOD)

I'm using and correct project (central/ble_app_hrs_c).

<info> app: Try connect to MAC:4D24C9800700

<info> app: Connected to a previously bonded device.

<info> app: Connected

<info> app: GATT ATT MTU on connection 0x0 changed to 23.

<info> app: BLE_GATTC_EVT_EXCHANGE_MTU_RSP

<info> app: BLE_GAP_EVT_SEC_PARAMS_REQUEST, bond 1 mitm 1 oob 1

<info> app: BLE_GAP_EVT_AUTH_KEY_REQUEST

<info> app: Data length for connection 0x0 updated to 27.

<info> app: BLE_GAP_EVT_DATA_LENGTH_UPDATE

<info> app: Connection secured: role: 2, conn_handle: 0x0, procedure: 0.

<info> app: BLE_GAP_EVT_CONN_SEC_UPDATE

<info> app: Connection secured: role: 2, conn_handle: 0x0, procedure: 1.

<info> app: BLE_GAP_EVT_AUTH_STATUS 0

This is LOG nRF52832 connect to nRF52832 (for second device I'm using and correct project periph/ ble_app_hrs)

<info> app: Try connect to MAC:6B12F8E4DEDC

<info> app: Connected

<info> app: BLE_GATTS_EVT_EXCHANGE_MTU_REQUEST

<info> app: GATT ATT MTU on connection 0x0 changed to 247.

<info> app: BLE_GATTC_EVT_EXCHANGE_MTU_RSP

<info> app: Data length for connection 0x0 updated to 251.

<info> app: BLE_GAP_EVT_DATA_LENGTH_UPDATE

<info> app: BLE_GAP_EVT_CONN_PARAM_UPDATE_REQUEST

<info> app: BLE_GAP_EVT_CONN_PARAM_UPDATE

At which stage a secure connection is established. Which command (EVT) is used for this code.

RE: secure connect 52832

FormerMember — Mon, 12 Mar 2018 09:10:31 GMT

In the SDK there are a some examples showing how to do OOB pairing using NFC. The examples are located in the ble_central/experimental and ble_peripheral/experimental folder, and explained here.