Best practices to secure a BLE NRF51 to NRF51 link ?

[Fabien Comte]

Hello,

I want to secure a link between 2 NRF51 (man in the middle and privacy with AES).

How to do that ? (I can use a static key in this application)

Most of the codes i found are partials and not up to date (timeout does not exist in structure, ...). Documentation is good but difficult to apply without an exemple to start and I not found any exemple in SDK.

Thank you.

edit 29.09.2015: traces.txt

edit 03.10.2015: traces.txt

[Petter Myhre]

I took at look at your traces. BLE_GAP_EVT_SEC_PARAMS_REQUEST is handled by the device manager, device_manager_peripheral.c. If you search for BLE_GAP_EVT_SEC_PARAMS_REQUEST in all files in the project you will get three hits. Two in ble_gap.h and one in device_manager_peripheral. When this event is received the device manager will respond with sd_ble_gap_sec_params_reply() with the security parameters that is set in the start of main.c Where I have written pemy:

[Petter Myhre]

//pemy start //#define SEC_PARAM_MITM 0 /< Man In The Middle protection not required. */ #define SEC_PARAM_MITM 1 /< Man In The Middle protection not required. */ //#define SEC_PARAM_IO_CAPABILITIES BLE_GAP_IO_CAPS_NONE /< No I/O capabilities. */ #define SEC_PARAM_IO_CAPABILITIES BLE_GAP_IO_CAPS_KEYBOARD_ONLY /< No I/O capabilities. */ //end

This tells the central that the peripheral requires man in the middle protection and that it only has keyboard as IO capability (even though it doesn't really have a keyboard)

[Fabien Comte]

Done and done as in your code but you dont show how to manage BLE_GAP_EVT_SEC_PARAMS_REQUEST and BLE_GAP_EVT_AUTH_KEY_REQUEST is never fired ???

[Fabien Comte]

Any idea of test to do ?

[Fabien Comte]

Maybe i have a clue, mu project is build with device_manager_central.c but you talk about device_manager_peripheral.c How to merge both because i am peripheral and central (S130) ?