GAP Security Mode VS. Characteristic Read/Write Permission

RE: GAP Security Mode VS. Characteristic Read/Write Permission

Nikita — Fri, 22 Aug 2014 15:58:37 GMT

Yes, upon trying to access a non-open characteristic a bonded authentication will be performed.

RE: GAP Security Mode VS. Characteristic Read/Write Permission

Lucas — Fri, 22 Aug 2014 15:10:38 GMT

Ok so essentially what I have proposed should work. I can leave a set of characteristics open and the central can use those as needed. Upon trying to access a non-open characteristic a bonded authentication must performed?

RE: GAP Security Mode VS. Characteristic Read/Write Permission

Nikita — Fri, 22 Aug 2014 03:15:14 GMT

gap_params_init function sets the security level for the GAP as well

Do you mean this one?

ble_gap_conn_sec_mode_t sec_mode;
BLE_GAP_CONN_SEC_MODE_SET_OPEN(&sec_mode);
err_code = sd_ble_gap_device_name_set(&sec_mode,
                                      (const uint8_t *)DEVICE_NAME,
                                      strlen(DEVICE_NAME));
APP_ERROR_CHECK(err_code);

It's write permissions for the Device Name characteristic.