Error OOB static key NRF connect

RE: Error OOB static key NRF connect

TobiasM — Mon, 27 Jan 2020 12:21:31 GMT

Hi Michael,

my answer comes a little bit late, but I still ran into the same problem and after some testing and good guesses I've managed to deconstruct the issue here. I was using the nRF Connect v3.3.0 app to connect to the nRF52 DK which was using a hardcoded OOB key.

The OOB value for nRF Connect in hex is: h1h2 .. h16|h17 .. h32 (16 byte)

The bug causes the software to discard the last 8 bytes h17-h32 and interprets the first 16 hex values as byte values. Also, little endian is applied which leads to the following corresponding TK (again in hex):

0x0|h16|0x0|h15|..|0x0|h2|0x0|h1

Further is every hex value a-f interpreted as 0 (letters are always 0). Therefore, we can deduce that you cannot input your chosen key. If you take

0x05, 0x04, 0x03, 0x02, \

0x01, 0x00, 0x09, 0x08, \

0x07, 0x06, 0x05, 0x04, \

0x03, 0x02, 0x01, 0x00

instead (note that for the TK you need change the little endian format again), the corresponding OOB key in the Connect app would be 5432109876543210|0 .. 0 but in fact the 0 .. 0 string can be any value.

I hope this will help everyone who is struggling at this point and hopefully this will get fixed soon, after already 3 years.

Best regards

Tobias Moser

RE: Error OOB static key NRF connect

Peter Kenyon — Wed, 12 Jun 2019 08:56:28 GMT

yep me too - same problem

RE: Error OOB static key NRF connect

gsegment — Mon, 03 Jun 2019 15:43:58 GMT

Hi, I have the same problem with OOB and nRF Connect Desktop. Is there any fix?

RE: Error OOB static key NRF connect

gsegment — Mon, 03 Jun 2019 15:43:10 GMT

Hi, did you find a solution?

RE: Error OOB static key NRF connect

FormerMember — Fri, 30 Sep 2016 12:33:36 GMT

I see the same problem when I test it here, it may be a bug somewhere..

RE: Error OOB static key NRF connect

michaeld — Tue, 27 Sep 2016 14:46:58 GMT

Yes I have tried that but no success.

RE: Error OOB static key NRF connect

Ulrich Myhre — Tue, 27 Sep 2016 14:45:43 GMT

Have you tried it the other way around? 00112233... Most of the data in BLE is little-endian, so it depends on the application if they wrap it around or not.