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

Pairing on demand & Automatic bonding

Hi Folks,

I am just asking general information (explanation and/or code samples examples) to set up a secured BLE connection between multiple centrals towards one peripheral working as BLE uart.

Her are my concerns for the moment:

I plan to use preconfigured random static adresses for each central stored in flash memory but also for the peripheral one.

-At this stage, I am asking to myself if I can launch a pairing on demand I mean on a specific hardware action I want to launch the pairing process which store the bond info in peripheral whitelist. I only see pairing at BLE initialisation. Could we launch a pairing on demand when BLE is already active?

-I also want to secure the bond creation during the first pairing phase to avoid an unknow device to bond on a sapre whitelist element so I understand there are many ways like presharing keys , LESC with passkey so that the ones which have the pass can proceed the pairing. Could you please me orientate toward sample code within SdK who do the job?

-Once pairing is ok, I understand that a peripheral whitelist must be fullfilled with the bond information freshly created. Seems perfect. I suppose that bond must be ko if a central or peripheral random static adress changes. Consequenly, I plan to keep both bond information in the whitelist & original random static keys in flash and reload them at start-up.

Is it a proper way to work? I mean in a secure way.

Thank u again for all your advices.

The best.

Sebastien

Parents
  • Hi

    Edvin is out of office for the time being. This case is also rather old, so if you have any further questions I would suggest making a new DevZone ticket and rather link to this one if relevant.

    As for the question on whitelisting, it does indeed seem like you understand the behavior correctly. Devices that are not whitelisted will not be able to connect to a central that is scanning for specific whitelisted devices, and new devices must be added on the central side.

    Best regards,

    Simon

Reply
  • Hi

    Edvin is out of office for the time being. This case is also rather old, so if you have any further questions I would suggest making a new DevZone ticket and rather link to this one if relevant.

    As for the question on whitelisting, it does indeed seem like you understand the behavior correctly. Devices that are not whitelisted will not be able to connect to a central that is scanning for specific whitelisted devices, and new devices must be added on the central side.

    Best regards,

    Simon

Children
No Data
Related