bonding ble nus example with android phone

RE: bonding ble nus example with android phone

Simonr — Thu, 24 Sep 2020 10:55:13 GMT

Hi Will

Please note that a static passkey when using legacy pairing will be susceptible to eavesdropping, but a MITM attacker won't be able to decrypt the connections of already bonded devices. The LESC module is not designed to be used with a static passkey, but it should be safe from MITM attacks as long as the static key isn't leaked somehow.

There shouldn't be any differences in adding this passkey protection to the multiprotocol example you're using. I would suggest checking out the example code my colleague has uploaded in this thread that adds bonding using a static key to the ble_app_uart example. It should not be very different from your project I think.

Best regards,

Simon

RE: bonding ble nus example with android phone

Will_008700 — Wed, 23 Sep 2020 13:11:57 GMT

In fact I need MITM protection with a fixed pin for pairing (for example 123123) with a fixed size,

could you help me for implementing these authentification level ? thanks

RE: bonding ble nus example with android phone

Will_008700 — Wed, 23 Sep 2020 12:17:17 GMT

Hi Simon

ok I see

in fact I'm using multiprotocol / ble zigbee / ble_zigbee_dynamic_light_switch_nus example and I've implemented some codes for targeted our requirements, peripherals... do you think that is possible to include "glucose application solution" in my current solution?

RE: bonding ble nus example with android phone

Simonr — Wed, 23 Sep 2020 11:54:33 GMT

I think it would be easier for you to add the Nordic UART Service (NUS) to one of the examples already using bonding and a passkey. I suggest using the Glucose application (which implements a passkey as well) as reference, and edit the project to use the Nordic UART Service instead of the Glucose service, as this should be less work than adding all the necessary security to the UART example.

Best regards,

Simon