doc: app_dev: key revocation #543
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
changelog-entry-required
|
You can find the documentation preview for this PR here. |
peknis
requested changes
Dec 4, 2025
michalek-no
force-pushed
the
doc-revok
branch
from
0adc8b2 to
64e23d7
Compare
|
Would this be worth a changelog entry? |
michalek-no
removed
the
changelog-entry-required
Contributor
Author
nope, removed. |
peknis
approved these changes
Dec 4, 2025
michalek-no
force-pushed
the
doc-revok
branch
from
64e23d7 to
0daa795
Compare
github-actions
bot
added
the
changelog-entry-required
eivindj-nordic
approved these changes
Dec 4, 2025
nvlsianpu
requested changes
Dec 4, 2025
| MCUboot can invalidate image verification keys through the ``CONFIG_BOOT_KMU_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. | ||
|
|
Contributor
There was a problem hiding this comment.
can you add info that (repharse): Keys must be provisioned in selected amount (Kconfig property?), refer to Performing KMU provisioning_ for HowTo.
adds description for key revocation feature. Signed-off-by: Mateusz Michalek <[email protected]>
michalek-no
force-pushed
the
doc-revok
branch
from
0daa795 to
3b5e76d
Compare
michalek-no
removed
the
changelog-entry-required
nvlsianpu
approved these changes
Dec 4, 2025
| .. note:: | ||
| The support for this feature is currently experimental. | ||
|
|
||
| MCUboot can invalidate image verification keys through the ``CONFIG_BOOT_KMU_KEYS_REVOCATION`` Kconfig option. |
Contributor
There was a problem hiding this comment.
Any reason we dont use the Kconfig reference here (and below)?
Suggested change
| MCUboot can invalidate image verification keys through the ``CONFIG_BOOT_KMU_KEYS_REVOCATION`` Kconfig option. | |
| MCUboot can invalidate image verification keys through the :kconfig:option:`CONFIG_BOOT_KMU_KEYS_REVOCATION` Kconfig option. |
(It is not linking properly at the moment,though we are using it elsewhere).
There was a problem hiding this comment.
We only use that format if the option is available in the Kconfig search.
Contributor
There was a problem hiding this comment.
Ok, can come back to this if it works after #401.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
adds description for key revocation feature.