s130 slave NUS service, No CCCD discovered

RE: s130 slave NUS service, No CCCD discovered

sowmya — Mon, 14 Dec 2015 13:30:50 GMT

Okay will check on this. Thank you for the link.

RE: s130 slave NUS service, No CCCD discovered

Anders Strand — Mon, 14 Dec 2015 13:27:02 GMT

If you want MITM protection, you need a out-of-band (oob) method of key exchange. See the bluetooth dev pages.

RE: s130 slave NUS service, No CCCD discovered

sowmya — Mon, 14 Dec 2015 13:03:11 GMT

Hi, I replaced the code with

    BLE_GAP_CONN_SEC_MODE_SET_OPEN(&cccd_md.read_perm);
    BLE_GAP_CONN_SEC_MODE_SET_OPEN(&cccd_md.write_perm);

and added event handling for secondary parameter request and system attribute missing, and it is working.

But the thing is peripheral is not having the bonding i.e., MITM is false. Can we enable peripheral MITM in S130? I checked with relay example and it is also the same.

RE: s130 slave NUS service, No CCCD discovered

Anders Strand — Mon, 14 Dec 2015 12:58:36 GMT

Hi. Have you tried bonding before enabling services? The line

BLE_GAP_CONN_SEC_MODE_SET_ENC_NO_MITM(&cccd_md.write_perm);

Means that the device will require pairing before the MCP will be able to enable notifications (write cccd).