-
CONFIG_SB_PUBLIC_KEY_FILES
¶
Public Key PEM files
Type: string
Help¶
Comma-separated list of absolute paths to public key pem files. The provision hex file will contain a list of hashes of public keys. The first public key hash is the one corresponding to the private signing key used to sign the image. See SB_SIGNING_KEY_FILE. The hashes of the public keys specified in this configuration will be placed after the aforementioned public key hash, in the order they appear in this config. The order is significant since if an image is successfully validated against a public key in the list, all public keys before it in the list will be invalidated. Example value: ~/keys/pk1.pem,~/keys/pk2.pem,~/keys/pk3.pem If config is an empty string, 2 generated debug files will be used.
Default¶
“”
Kconfig definition¶
At <nRF>/subsys/bootloader/Kconfig:95
Included via <Zephyr>/Kconfig:8
→ <Zephyr>/Kconfig.zephyr:9
→ <BuildDir>/Kconfig/Kconfig.modules:1
→ <nRF>/Kconfig.nrf:25
→ <nRF>/subsys/Kconfig:8
Menu path: (Top) → Modules → Nordic nRF Connect → Bootloader → Use Secure Bootloader
config SB_PUBLIC_KEY_FILES
string "Public Key PEM files"
default ""
depends on SECURE_BOOT
help
Comma-separated list of absolute paths to public key pem files.
The provision hex file will contain a list of hashes of public keys.
The first public key hash is the one corresponding to the private
signing key used to sign the image. See SB_SIGNING_KEY_FILE.
The hashes of the public keys specified in this configuration will be
placed after the aforementioned public key hash, in the order
they appear in this config. The order is significant since if an image
is successfully validated against a public key in the list, all
public keys before it in the list will be invalidated.
Example value: ~/keys/pk1.pem,~/keys/pk2.pem,~/keys/pk3.pem
If config is an empty string, 2 generated debug files will be used.
(The ‘depends on’ condition includes propagated dependencies from ifs and menus.)