Manual key provisioning for nrf54l15

[Nilesh]

Hi All,

I have a question and slight confusion as referring to couple of links.

Performing KMU provisioning: Here we are highlighting provisioning of private key up to 3 counts

and 

Exercise 2 - DFU with custom keys - Nordic Developer Academy: Here we are highlighting provisioning of public key

So, creating slight confusion here.

I believe it's a private key only that is provisioned. However, a concern here as we are manually provisioning private key means we cannot use this method during production.

Maybe I am missing something here. 

Can anyone please help?

Thanks!

[Nilesh]

Hi, 

I found out that, manual key provisioning works with public key as well. Provided that public key should be extracted from generated keypair.

Means, private key which is used to sign the image its public key can be provisioned.

Kindly suggest if this is correct understanding and doing.

Thanks!

[Nilesh]

Hi, 

I am still waiting for the update in case anyone knows about it, please suggest.

Priyanka can you please support on this ?

Thanks!!

[Priyanka]

Hi Nilesh,

Apologies for the delay as it was a long weekend here in Norway.

From both the links, you can see that it is the public key that is being provisioned. The private key is used to sign firmware images and must remain secure and confidential. 

So,  If you see references to provisioning a .pem file, just make sure that it is the public key portion being uploaded, not the private key itself. 

-Priyanka

[Nilesh]

Hi Priyanka, 

Thanks for the confirmation. Yes, with public key provisioning it works.

Confusion started due to mix information at different links.

Now it is clear, and I am good to close this ticket now.

Thanks,

Nilesh

[Igor]

Priyanka 
Why does the exercise provision private_key.pem?

west ncs-provision upload -s nrf54l15 -k private_key.pem

Can you please arrange to fix this mess.

Thank you.