Default link key showing in the bin file

[Saksham Jain]

Hello team,

In our bin file, we are seeing "ZigBeeAlliance09" as String and how to avoid this string in the bin file? I am using SEGGER SES ID tool to generate bin file.

Code: external/zboss/include/zb_config.h:158:#define ZB_ZGP_DEFAULT_LINK_KEY "ZigBeeAlliance09"

" D @  @(  @( @ ÿÿ @ D ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ Ö Á” I• Y• i• å” Í” Ñ” Õ” 8ã 8ã %02x unknown ZigBeeAlliance09 ÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞß ZGP "!ÿÿÿÿÿÿÿÿ"

We have issue on clearing the cyber security clearance. So please guide us to avoid string in the bin file.

[Elfving]

Hello,

What SDK and version are you using? As you are using SEGGER SES IDE I assume you are using nRF 5 SDK?

Do you want to use a different install code than the default "ZigBeeAlliance09"? 

Regards,

Elfving

[Saksham Jain]

I am using SEGGER V8.12a. NRF5

No, I want to remove the install code from the bin file. (Or we can hide like that, so it is not visible in the bin file, if I open in the notepad.

[Elfving]

What version of the nRF5 SDK are you using?

[Saksham Jain]

nRF5 SDK v16.0.0., nrf5_sdk_for_thread_and_zigbee_v4.2.0_af27f76.zip

[Elfving]

This is nothing to worry about. It's actually required by the spec that the default global trust center link key is the ZigBeeAlliance09 key (from Zigbee spec 4.2.1.2.1 Security Keys):

It's just the link key used for joining centralized security networks (networks with a trust center/coordinator), but it is not the Zigbee network key

Here you see an example where I have set the nwk key to aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa. The ZigbeeAlliance09 key is used to encrypt the the application layer in the first Transport Key. This is the command where the TC sends the network key.

After the device has received the nwk key, it will switch to using this.

It also receives a device specific TC link key (in the second Transport Key command), which will be used for any application layer encryption

Regards,