RE: Bonding Troubles

Hieu — Fri, 22 Nov 2024 14:44:15 GMT

Hi jnenick,

Firstly, let me address each of your requirement.

[quote user=""]Only permit usage of application characteristics (TX and RX) when bonded with the connected phone[/quote]

You need to add security requirement to the characteristic. The NUS supports Authentication requirement by enabling CONFIG_BT_NUS_AUTHEN.

If you need other level of security requirement, you will need to run your own custom BLE service. We have instructions to do that in our BLE Fundamentals online course.

[quote user=""]Only permit bonding when a user presses a button on the device[/quote]

Does the device also support a display that can display a 6-digit number?

If yes, and the bonding peer is a mobile device, then you can support pairing with keys.

If not, I am afraid the only solution is to use Just Works pairing. The device only allows pairing/bonding in a specific state that is entered via the button. This state could be entered after a button pressed, or only when the button is held; and it could be exited by timeout, or via another button press.

For more information, please refer to Bluetooth specification, Vol 3, Part H, section 2.3. You can also refer to the online lesson I linked above for an overview.

[quote user=""]When bonding is started do not present a passcode dialog to the user on the phone[/quote]

After a bond is formed, future pairing will not require passkey entry.

[quote user=""]The uart service works great but I'm having a great amount of difficulty adding any measure of security to the project.[/quote]

The Peripheral UART sample supports adding security via the sample specific Kconfig CONFIG_BT_NUS_SECURITY_ENABLED. You can try this first.

Otherwise, the online course I linked have an extensive step by step guide to implement security into an application.

Hieu