HI Szymon, Thanks for the explanation. Am I right in saying that the ENC, AUTHEN and AUTHOR flags are NOT combined together?
i.e. you don't do: BLE_GATT_CHR_F_READ | BLE_GATT_CHR_F_READ_ENC | BLE_GATT_CHR_F_READ_AUTHEN but rather: BLE_GATT_CHR_F_READ | BLE_GATT_CHR_F_READ_ENC or BLE_GATT_CHR_F_READ | BLE_GATT_CHR_F_READ_AUTHEN or BLE_GATT_CHR_F_READ | BLE_GATT_CHR_F_READ_AUTHOR Correct? On Tue, 17 Jul 2018 at 15:39, Szymon Janc <[email protected]> wrote: > > Hi, > > On Tuesday, 17 July 2018 10:59:41 CEST Amr Bekhit wrote: > > Hello, > > > > Can someone explain (or help point to documentation) the ENC, AUTHEN > > and AUTHOR flags that are used in GATT characteristics? I've noticed > > that using them in combination with the normal READ and WRITE flags > > causes the central to request a pin code when it tries to access the > > characteristic, but other than that, what each flag means and how they > > can be combined together is unclear to me. > > ENC means that operation (read or write) on characteristic requires encryption > (MITM protected or not). > > AUTHEN means that operation requires authentication (encryption with MITM > protected key). > > AUTHOR means that operation requires authorization - that gives your > application means to rejected read/write operation based on your own > authorization mechanism (eg user pushing a button). > > > For more details I suggest getting into Bluetooth Core Specification. > > -- > pozdrawiam > Szymon Janc > >
