About Request hexadecimal key (hex 16 octets) in the provisining between nRF52832 and Jetson nano(ubuntu arm64)

RE: About Request hexadecimal key (hex 16 octets) in the provisining between nRF52832 and Jetson nano(ubuntu arm64)

Hung Bui — Mon, 25 Jan 2021 11:18:09 GMT

Hi Colin,
I'm no expert in encryption and security but you can find the AES_CMAC implemented in the example (light_switch for example ) in aes_cmac() function in aes_cmac.c

RE: About Request hexadecimal key (hex 16 octets) in the provisining between nRF52832 and Jetson nano(ubuntu arm64)

colin.tan — Mon, 25 Jan 2021 03:32:59 GMT

Hi Hung,

I sorry for bother you again, could you tell me what kond of the AES_CMAC algorithm the Nordic Mesh SDK 4.2.0 using for provisioning confirm value compute？

RE: About Request hexadecimal key (hex 16 octets) in the provisining between nRF52832 and Jetson nano(ubuntu arm64)

Hung Bui — Wed, 13 Jan 2021 10:55:30 GMT

Could you give more information about the unprovisioned device ?
Have you tried to test provisioning the stock example in the SDK , the light_switch project for example.
I'm just wondering if you have fetched the STATIC_AUTH_DATA into the firmware of your unprovisioned device.

RE: About Request hexadecimal key (hex 16 octets) in the provisining between nRF52832 and Jetson nano(ubuntu arm64)

colin.tan — Wed, 13 Jan 2021 10:02:24 GMT

By the way， because the Unprovisioned device I developing just support static OOB， so I only tried static authentication with the device。

RE: About Request hexadecimal key (hex 16 octets) in the provisining between nRF52832 and Jetson nano(ubuntu arm64)

colin.tan — Wed, 13 Jan 2021 09:57:05 GMT

Thank you for your reply，I also had tried with 315F65..， but also failed with the same issue。

RE: About Request hexadecimal key (hex 16 octets) in the provisining between nRF52832 and Jetson nano(ubuntu arm64)

Hung Bui — Tue, 12 Jan 2021 16:37:31 GMT

Hi,
I would suspect the endianess was reversed. So if you try again with 315F65.. it may work.

But i'm not sure it's the authentication causing the issue, have you tried to test without static authentication ?