Different bonding configuration with different devices

RE: Different bonding configuration with different devices

Kenneth — Tue, 15 Sep 2020 07:32:42 GMT

I understand the use case now, however I don't see a good solution here no. You may consider not bonding at all, and instead encrypt all data in the application (instead of relying on encryption on link layer), this could somewhat do what you want.

Kenneth

RE: Different bonding configuration with different devices

Federico — Mon, 14 Sep 2020 20:22:40 GMT

I was thinking it might be technically feasible to connect and write to an open characteristic requesting to clear or set the bonding bit, before attempting to pair. It doesn't seem like a good solution though.

Regarding your question, we expect some of the windows devices to connect to a lot of peripheral devices, and never connect again. So it seems rather pointless to store the bonding information. Also, we're not sure whether we can programmatically delete bonded BLE devices in windows, which brings a whole lot of other problems (like LTK lost on the peripheral). So not bonding at all could solve that.

RE: Different bonding configuration with different devices

Kenneth — Mon, 14 Sep 2020 13:29:22 GMT

1. In principle it should be possible to dynamically adjust the bonding bit, however how would you know that it was a Windows 10 peer that connected? I do not see how you would be able to control this, if you were, you could also control the bonding bit.

2. Windows 10 will connect and establish the highest common supported security level/mode, which make sense I think.

3. That would violate the BLE spec.

Can you elaborate why you don't want Windows 10 to bond?