Secured NUS

RE: Secured NUS

Simon — Mon, 09 Sep 2019 11:51:08 GMT

You can use scan filtering on the central side, which makes it possible to perform filtering based on name, address, uuid and appearance. You can set the advertising name of the advertising device to a agreed upon name, and put this name into the scan filter, and only this device will be able to initiate a connection.

Read more about scan filtering in this Devzone ticket, where I explain it in more details.

Best regards,

Simon

RE: Secured NUS

Fabien Comte — Wed, 04 Sep 2019 15:20:28 GMT

Hello,

Thank you for your help. I will read that asap.

RE: Secured NUS

Fabien Comte — Wed, 04 Sep 2019 15:19:46 GMT

Hello,

Thank you for your help. How can I be sure that the remote is a valid one please ? What is the best solution id both devices never connected before (bounding) but must recognise that it's an allowed device on the field ?

RE: Secured NUS

awneil — Tue, 03 Sep 2019 10:13:19 GMT

RE: Secured NUS

Simon — Tue, 03 Sep 2019 07:45:45 GMT

Here are the different methods to secure a connection. The just work method requires no human intervention. Take a look at this thread, where I explained how to implement paring (pairing two BLE devices is equivalent of securing the connection) on a BLE connection.

Best regards,

Simon