Bonding Question

RE: Bonding Question

Petter Myhre — Wed, 14 Sep 2016 12:06:03 GMT

No problem :)

RE: Bonding Question

Mich — Tue, 13 Sep 2016 22:11:40 GMT

Hi Petter,

Thanks for your reply. Yes, I'm using PCA10036. The reason I used SDK 0.9.2 is because I wanted to try the bonding example. I have tried BLE_GAP_CONN_SEC_MODE_SET_ENC_NO_MITM. With this one, I can still see the raw data on my sniffer. Maybe it's just because my sniffer can interpret it since it listens from the beginning. I'll try BLE_GAP_CONN_SEC_MODE_SET_ENC_NO_MITM next time....

Mich.

RE: Bonding Question

Petter Myhre — Tue, 13 Sep 2016 13:55:29 GMT

Why are you using SDK 0.9.2? Do you have preview development kit? PCA10036? ble_app_hrs supports bonding yes, but the accessing the CCCD of the heart rate characteristic doesn't require the link to be encrypted. If you can see the data on the sniffer there are two possibilites, you haven't bonded, so the link is not encrypted, or the sniffer sniffed the pairing process and got the encryption keys.

If you want the CCCD to require the link to be encrypted you can change this in services_init(). Change BLE_GAP_CONN_SEC_MODE_SET_OPEN(&hrs_init.hrs_hrm_attr_md.cccd_write_perm); to

BLE_GAP_CONN_SEC_MODE_SET_ENC_NO_MITM(&hrs_init.hrs_hrm_attr_md.cccd_write_perm); only require Just Works pairing to access the CCCD.

BLE_GAP_CONN_SEC_MODE_SET_ENC_WITH_MITM(&hrs_init.hrs_hrm_attr_md.cccd_write_perm); requre Passkey Entry or OOB pairing to access the CCCD.