Why does the Windows BLE stack ignore a Peripheral security parameter of "bond = 0" if "LESC = 1"?

  • Thread starter Thread starter Elias Simon
  • Start date Start date
E

Elias Simon

Guest
I'm designing a Peripheral and a native Windows interface to control it. Communications need to be encrypted, but neither device needs to store persistent data about the other.

Ideally, the devices would be able to exchange ECDH keys to encrypt communications in the short-term, but Windows seems to store the peer identity regardless. On connections beyond the first, the Windows machine ends up exposing itself to the Peripheral like a spoofed Central. Windows also presents unnecessary UI to the user because of the Bonding.

Is there a way to prevent Windows from Bonding, while still leveraging the LESC feature of ECDH key exchange?

Continue reading...
 
Back
Top