Skip to content

doc: nrf-bm: app_dev: bootloader_keys: Correct conf BOOT_KEYS_REVOCATION and details on MCUboot image configuration #554

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
eivindj-nordic merged 2 commits into from
Dec 9, 2025
Merged

doc: nrf-bm: app_dev: bootloader_keys: Correct conf BOOT_KEYS_REVOCATION and details on MCUboot image configuration #554

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f4e9d12
doc: nrf-bm: app_dev: bootloader_keys: Correct conf BOOT_KEYS_REVOCATION
eivindj-nordic Dec 8, 2025
4a259e7
doc: nrf-bm: app_dev: dfu: Add details on mcuboot image config file
eivindj-nordic Dec 8, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions doc/nrf-bm/app_dev/dfu/bootloader_keys.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,14 +74,14 @@ Runtime revocation
.. note::
The support for this feature is currently experimental.

MCUboot can invalidate image verification keys through the ``CONFIG_BOOT_KMU_KEYS_REVOCATION`` Kconfig option.
MCUboot can invalidate image verification keys through the ``CONFIG_BOOT_KEYS_REVOCATION`` Kconfig option.
Enable this option during the MCUboot build process if there is a risk that images signed with a compromised key might contain critical vulnerabilities.
The revocation of keys is triggered when both the firmware loader and SoftDevice are using a newer key.

Number of available key slots is set by ``CONFIG_BOOT_SIGNATURE_KMU_SLOTS`` Kconfig option. These slots has to be properly provisioned. For more information refer to `Performing KMU provisioning`_.

.. caution::
You must enable the ``CONFIG_BOOT_KMU_KEYS_REVOCATION`` Kconfig option when creating your project.
You must enable the ``CONFIG_BOOT_KEYS_REVOCATION`` Kconfig option when creating your project.
If you have not activated this option initially, you cannot enable it later.
Without the option, this functionality unavailable and potentially exposes your project to security issues.

Expand Down
Loading