Windows 10 LESC?

[Rocky]

Has anyone been able to use the LE Secure Connections feature with Windows?

I see that there are some planned improvements in the Windows 10 creators update, but don't see any mention of BLE 4.2 or LESC. I am working on a product that currently uses the BLED112 dongle with Windows, but this dongle doesn't support 4.2/LESC. In fact, I don't see any dongles on the market that support 4.2.

Any tips or thoughts on how to implement LESC on a Windows machine would be greatly appreciated.

[bjorn-spockeli]

Hi TJ, 

you can use our pc-ble-driver library together with a nRF52840 Dongle to implement LESC on Windows. 

Best regards

Bjørn

[Rocky]

Hi,

Yes, I see that the the nRF52840 is now released and working with the pc-ble-driver.  I usually use the Python wrapper (pc-ble-driver-py), but the support for this is lagging and I don't think it yet works with the nRF52840.  Perhaps I could switch to C/C++ and implement using the pc-ble-driver directly.

Do you have any thoughts or examples on how I could implement a central that supports LESC using pc-ble-driver?  It seems like this would require quite a bit of additional code to get working.  For example, wouldn't I need to port one of the crypto libraries and some of the SDK libraries like nrf_crypto, and security_manager to the Windows build?

Any other suggestions are welcome.  My goal is to create a PC test station to be used to test the security implementation (LESC) on a peripheral.

[bjorn-spockeli]

Hi TJ, 

You are right that you will need to generate the public and private DH encryption keys. We use the pc-ble-driver in nRF Connect for Desktop, which supports LESC paring.  Not quite sure how we solve this in nRF Connect. I will contact the devs and see if they can shed some light on this. 

Bjørn

[Rocky]

Another options I considered is writing Javascript plugins for nRF Connect.  It seems like the Javascript lib is updated more frequently than the Python lib.  Do you know if the Javascript implementation supports LESC?

[bjorn-spockeli]

HI TJ, 

I just spoke with the nRF Connect devs. 

nRF Connect for Desktop uses the JS implementation of pc-ble-driver, pc-ble-driver-js.  The JS implementation uses the micro-ecc library to generate the private and public keys used for LESC, however, its been wrapped in a C++ API in pc-ble-driver-js, see https://github.com/NordicSemiconductor/pc-ble-driver-js/blob/master/src/driver_uecc.cpp. 

They suggested to look at this test for a simple example on how this is used in the source. 

Best regards

Bjørn

[_Mickey]

Hi Rocky,

Have you solved this problem? i had same problem,  Now I can successfully generate Public key and private key, but in the BLE_GAP_EVT_LESC_DHKEY_REQUEST event, I get the wrong public key, but in the NRF Sniffer, the public key is correct. I don't know what went wrong

Code:

Correct Public key

Wrong Public Key