Identification of central devices

Hi

I'm using an nRF5280 with Zephyr and nRF Connect SDK v2.1.0.

My peripheral refuses connections unless there is a bond. In order to accept bonding, it needs to be put into a specific state (i.e. a button press).

Today I received an additional requirement: pairing/bonding shall only be allowed to the exact same device that was paired before (unless the device gets completely reset -> what would delete all stored data as well). The use case is, that the user may (accidentaly or not) remove the bonding on the phone, but still needs a means to regain access to the stored data.

Is there a way to uniquely identify the central device in a different bonding process on my peripheral? The solution needs to work with randomized device addresses of course.

Parents
  • You should probably REJECT that requirement outright - users don't always know what they want.

    There is no way to differentiate an attacker spoofing the address of an existing central from the case where the user deleted the bonding information.

    Thus a proper funtioning BTLE devices has to reject all re-pair attempts unless it was put into pairing mode explicitly.

    TL;DR there is no way to uniquely identify the central without the bonding data.

Reply
  • You should probably REJECT that requirement outright - users don't always know what they want.

    There is no way to differentiate an attacker spoofing the address of an existing central from the case where the user deleted the bonding information.

    Thus a proper funtioning BTLE devices has to reject all re-pair attempts unless it was put into pairing mode explicitly.

    TL;DR there is no way to uniquely identify the central without the bonding data.

Children
Related