Role of Keys kdist_central and kdist_periph in sd_ble_gap_authenticate

RE: Role of Keys kdist_central and kdist_periph in sd_ble_gap_authenticate

Hung Bui — Mon, 27 Nov 2017 14:16:56 GMT

Hi Darrew,

It's hard for us to include all arguments into the message sequence chart. We want to mention only those arguments that make the difference between Just Work, Passkey, OOB, Legacy pairing etc.

This is when you should have a look at the example to get the detail of how to set the arguments. Most of the arguments have the definition to explain what they do, as mentioned in the answer above. If you need more detail on how it works, you may need to have a look at the Bluetooth Core Spec.

RE: Role of Keys kdist_central and kdist_periph in sd_ble_gap_authenticate

Darrew — Mon, 27 Nov 2017 09:40:29 GMT

Hi Hung Bui,

It would be more clear to have a Message Sequence Chart that exactly defines the correct and needed arguments on the call to sd_ble_authenticate(). I find sd_ble_authenticate(bond, no_mitm, no_io_caps) ambiguous (it will not work if the correct keys are not distributed!).

Same problem -ambiguity- for sd_ble_gap_encrypt(ediv, rand, ltk) in MSC Central Legacy Pairing > Bonding: Just Works; it would help to mention that those arguments correspond to the peer device i.e. Peripheral.

RE: Role of Keys kdist_central and kdist_periph in sd_ble_gap_authenticate

Hung Bui — Mon, 30 Oct 2017 12:35:09 GMT

Hi Darrew,

Note that inside p_sec_params, the description of kdist_central and kdist_periph say:

 ble_gap_sec_kdist_t   kdist_own;                 /**< Key distribution bitmap: keys that the local device will distribute. */
  ble_gap_sec_kdist_t   kdist_peer;                /**< Key distribution bitmap: keys that the remote device will distribute. */

They are bitmap (flags) telling which key the peers will distribute and expect to be distributed.