nRF5 SDK is not maintained anymore
More Info: Consider nRF Connect SDK for new designs

Is there any peripheral sample for OOB legacy pairing?

Is there any peripheral sample for OOB legacy pairing?
I'd like to know how to encrypt with temporary key(TK).
I checked the ble_hids_keyboard_pair_nfc sample in the SDK 17.1.0, but I couldn't find the part that generated LP_CONFIRM_R and STK from TK.
I would appreciate any advice.

Parents

0 user75734 over 4 years ago

Hi

Is there a specific reason you want to use "just" legacy OOB pairing? I don't think there are any examples doing exactly this by default, but if you want to make one I would suggest checking out the peer manager usage chapter here.

As for pairing with a temporary key, you might be interested in the ble_app_gls which generates a passkey used for pairing.

Best regards,

Simon
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 user75734 over 4 years ago

Hi

Is there a specific reason you want to use "just" legacy OOB pairing? I don't think there are any examples doing exactly this by default, but if you want to make one I would suggest checking out the peer manager usage chapter here.

As for pairing with a temporary key, you might be interested in the ble_app_gls which generates a passkey used for pairing.

Best regards,

Simon
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

0 user116057 over 4 years ago in reply to user75734

Hi
Thank you for your prompt reply.
The reason for using legacy OOB is that the central device does not support LESC.
I read the part you indecated but I still can't find out about LP_CONFIRM_R and STK generation.
Does nRF52 support ”legacy OOB” in the first place?

Best regards,
wang
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel