adding to secure_dfu_test_images, need private key?

[gringlediscus]

I have looked at secure_dfu_test_images\ble\ for nrf52832 and would like to create a blinky_application_s132.zip (corresponding to hrs_application_s132.zip) to do some testing of DFU update of just the application.  I can update the 'without_bonds' application to hrs_appliation.  Now that I have hrs_application I would like to update that image with something simple such as blinky_application.  To do so, I believe I need to use the signature, hte same private key that was used for the bootloader, right?
I cannot find the private key file from which the public key was created. Am I on the right track?  Is the private key file available?

[Pawel Niedbala]

You have to generate a pair of keys: a private key as well as a public key on your own, for example in command window using nrfutil tool, cmd:

    nrfutil keys generate priv.pem

    nrfutil keys display --key pk --format code priv.pem --out_file publ.c

Public key is a component of secure bootloader, so you should use your generated key instead of the default one when compiling the project, while corresponding private key is used when you prepare update file in .zip format.

[gringlediscus]

Thank you Pawel.