Gatt Read/write and insufficient key size error

RE: Gatt Read/write and insufficient key size error

Hung Bui — Fri, 09 Aug 2019 12:26:35 GMT

Yes, It's correct. You neeed authorisation be enabled on the characteristic.

I don't think it will be implemented in near future on the softdevice. Not 100% sure about the Zephyr stack though.

RE: Gatt Read/write and insufficient key size error

Mahendra Tailor — Fri, 09 Aug 2019 09:23:36 GMT

Is it planned to add this feature in a future softdevice?

RE: Gatt Read/write and insufficient key size error

Mahendra Tailor — Fri, 09 Aug 2019 09:19:35 GMT

Hi
Thank you for getting back.
The workaround you suggest requires that authorisation be enabled for read/write.

Is that correct?

Regards

Mahendra

RE: Gatt Read/write and insufficient key size error

Hung Bui — Fri, 09 Aug 2019 08:11:06 GMT

Hi Mahendra,

Currently our stack doesn't have an option to set the key size requirement for each attribute. You can set the security level but not the key size, by the stack.

What you need to do is to handle that by the application.

You can return BLE_GATT_STATUS_ATTERR_INSUF_ENC_KEY_SIZE ( not BLE_L2CAP_CH_STATUS_CODE_INSUFF_ENC_KEY_SIZE as it's for L2CAP channel ) when there is an authorized read request or write request.