NCS: Get Public Keys during OOB pairing procedure

RE: NCS: Get Public Keys during OOB pairing procedure

tkirschner — Tue, 17 Jan 2023 11:42:43 GMT

This idea uses LESC, so CONFIG_BT_SMP_OOB_LEGACY_PAIR_ONLY is not enabled. Thanks for pointing me into the right direction. I'll look into the options you've listed.

RE: NCS: Get Public Keys during OOB pairing procedure

Susheel Nuguru — Tue, 17 Jan 2023 11:10:10 GMT

maybe you can edit bt_hci_evt_le_pkey_complete to make it call your application callback handler to copy the pub_key in your app memory area?

RE: NCS: Get Public Keys during OOB pairing procedure

Susheel Nuguru — Tue, 17 Jan 2023 11:07:33 GMT

tkirschner,

[quote user=""]Are the public keys from peers saved anywhere, where they're accessible through the SDK?[/quote]

The keys are available in the same smp.c file in sc_public_key for the peripheral. But .these wont work when you have CONFIG_BT_SMP_OOB_LEGACY_PAIR_ONLY defined in your project. You need to somehow expose sc_public_key to your application (as opposed to this variable being static). I do not think trying to get the memory location of where this is saved is not fail safe idea to get this data as the memory locations might change per device and there is no proper way to get the memory address through pointers other than trying to exposing sc_public_key or pub_key in zephyr\subsys\bluetooth\host\ecc.c

RE: NCS: Get Public Keys during OOB pairing procedure

Hieu — Fri, 13 Jan 2023 00:34:15 GMT

Hi tkirschner,

I will support you with this question. However, I need more time to look into Zephyr's implementation to answer you.

Unless someone from the community already helped you, I will be back with the answer latest by the end of Tue Jan 17.

Hieu