This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

BLE minimal modifications to use pre shared key auth and encryption

Hello,

I have a nRF52 to nRF52 connection. I want to secure it (auth and if possible encryption) with a pre shared key. What are the points that I have to modify please ?

Thank you.

  • A basic device and central with OOB passkey example. Document graphics are probably enough but it's difficult for me to find the corresponding handlers / functions, how to feed them. An example helps me to test and appropriate the knowledge.

  • Hi Fabien, I would suggest you to use our ready-made library : advertising library and device manager library.

    Have you tried our SDK's examples and get familiar with how those libraries work? We have an passkey example with ble_app_gls project. You need to type a 6 digit passkey on the central to encrypt the link.

    For OOB you can try the experimental_ble_app_hrs_pairing_nfc in SDK v11.

    Please be aware that the nRF52 NFC module is only a tag, not a reader, so you can't do NFC reading from the nRF52. You need a peer that can do NFC reading. For example a Windows 10 PC that has NFC and BLE.

    After the 2 device has been paired and bonded, the LTK (Longtermkey) is exchanged can be used for furture connection. Also the address identification of both peer also exchanged and can be used as whitelist to avoid connection from unwanted device. Please have a look at the advertising module. And have a look here.

Related