How to exact Link Keys from Nordic nRF5340 Audio EDK?

RE: How to exact Link Keys from Nordic nRF5340 Audio EDK?

Tommy_Li — Mon, 15 Apr 2024 05:09:06 GMT

Hi Ottowei:

Could you please provide some ellisys .btt files which contain broadcast audio or unicast audio for study.

We are a small company, we cant afford the ellisys sniffer, but we still want to the see the air packet of le audio.

Thanks in advance.

RE: How to exact Link Keys from Nordic nRF5340 Audio EDK?

Ottowei — Fri, 12 May 2023 05:22:41 GMT

Hi Elfving,

I appreciate your comments.

Few more questions:

What are the roles you use? In both termnial and Ellisys Sniffer, the bluetooth address does not appear to be the same.

Does your Pixel 7 series phone serve as the gateway (source) for connecting two headsets (nRF5340 audio Board)?

Or do you use only one nRF5340 audio gateway to connect another nRF5340 audio headset?

As a side note, this experiment is only intended to evaluate LC3 package quality.

RE: How to exact Link Keys from Nordic nRF5340 Audio EDK?

Elfving — Thu, 11 May 2023 11:12:09 GMT

Hello Otto,

Have a look at the response from Jowan below, which 100% correct.

If you go for the first option you can find the long term key in the log in the log

which you can then post in the Ellisys sniffer security panel.

Regards,

Elfving

RE: How to exact Link Keys from Nordic nRF5340 Audio EDK?

Jpittevils — Thu, 11 May 2023 07:21:16 GMT

You've got two options I think.

Either do

CONFIG_BT_LOG_SNIFFER_INFO=y
CONFIG_BT_DEBUG_LOG=y

This will print out the randomly generatied keys to the console so you can enter them manually in the sniffer.

Or you can do

CONFIG_BT_TINYCRYPT_ECC=y
CONFIG_BT_USE_DEBUG_KEYS=y

Then the connection will use pre-determined keys that the sniffer should have stored in its memory and then it can decrypt the packets without any more input needed from you.