• State Verified Answer
  • Replies 3 replies
  • Subscribers 68 subscribers
  • Views 1448 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 234717
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Bond does not work after the bond info delete on NRF connect.

alan.kim

Hello. my name is Alan. I'm a newbie about BLE bonding.

because our new project needs a bonding feature,
I referred to the Heartrate example(ble_app_hrs) to apply bonding to the BLE UART example(ble_app_uart).

But when I flashed the ble_app_hrs example on pca10028, I found a fault.


Fault :
After a bonding using NRF Connect(Android), I deleted the bond info;
when I ask bond again, the bonding does not work.


This symptom is not resolved when the device is rebooted. It's only resolved when the firmware is flashed again.

I'm using s130 2.0.1 with nrf51822.

Parents
  • +1

    Check the handling of PM_EVT_CONN_SEC_CONFIG_REQ in the pm_evt_handler() function (and the comment). FYI:I refer to the btle hrs peripherial example in SDK12.3 version.

    Nordic example code explicitly forbids re-bonding here, your application might have other security needs.

    Note that this case would look exactly like a man-in-the-middle attack, hence the reject in the example code.

Reply
  • +1

    Check the handling of PM_EVT_CONN_SEC_CONFIG_REQ in the pm_evt_handler() function (and the comment). FYI:I refer to the btle hrs peripherial example in SDK12.3 version.

    Nordic example code explicitly forbids re-bonding here, your application might have other security needs.

    Note that this case would look exactly like a man-in-the-middle attack, hence the reject in the example code.

Children
Related