【Mesh Security Materials Generation】Is it possible to generate mesh security materials by users?

[xiaolongba]

Hello Nordic Experts,

I almost finished the development for my mesh project with nRF52840. But I faced some tricky issues when in mass production. that is the time for provisioning is too long. my purpose is below:

1.  the devices can be communicated with each other after downloading the FW, in other words, these devices with the default security materials, such as netkey,appkey,iv index etc.
2. at this moment, users dont need to do the provisioning process when they got the device unless they would like to change netkey or appkey or others

so my questions as follows:

1. Is it possible to generate the mesh security materials by users? Nordic can provide such one tool to customer?

2. could you point out the location for these mesh security materials in the internal flash?

Note: what does mesh security material mean is netkey,appkey,devkey,iv index,unicast address etc.

thanks.

[Mttrinh]

Hi,

1. We do have our nRF Mesh app for iOS and Android, assuming that you have support for PB-GATT and Proxy feature. The sample app is for development/protoyping purposes targeting developers to make debugging easier, so it is recommeded that you create your own app. The nRF Mesh app is open-source and can be used as a reference. It can be found on our Github, see here and here.

2. You can use this function mesh_stack_persistence_flash_usage() to get which flash areas used by the mesh stack to store the provisioning data.

[xiaolongba]

Hi Mttrinh

Big thanks for your detailed replies, regarding the ways to generate mesh security materials you mentioned above is not what I expected. Actually, I would like to generate this info with one specified pc tool or lib that can be used for my own pc tool for mass production. Is it possible?

[Mttrinh]

Hi, 

I might have mistunderstood your question, by "generating the mesh security materials" do you mean provisioning the device?

[xiaolongba]

Hi Bro,

what do the mesh security materials mean is  netkey,appkey,unicast address, iv index, etc. and I would like to generate these parameters with the PC tool and store them into the internal flash through UART, so I don't need to provision unprovisioned devices one by one at this moment. so they can communicate with each other after power on.

[xiaolongba]

also, I found the corresponding mesh security materials after calling the function mesh_stack_persistence_flash_usage() , the details as below:

the first red highlighted is Netkey, the second one is devkey, the third one is appkey, But I dont know what do the others mean? could you explain to me what are they? and where is the iv index & unicast address etc?

thanks in advance.