crypt.go: add function to verify key for specific keyslot - #574
Merged
frederic-hoerni merged 2 commits intoSep 25, 2026
Merged
frederic-hoerni merged 2 commits into
frederic-hoerni merged 2 commits into
Conversation
In order to be able to prevent removing keyslots for which we have the only key for the containers, we need to be able to check specific keyslots. We typically only know the key that got registered in keyring during boot. And they come from sealed key that we usually cannot unseal again later. If we remove any of those keyslots because an unexpected keyslot was used for activation, then we lose ability to act on the container, until we reboot and a different keyslot gets used. Unexpected keyslot might used if we for example lose power or hard reset in the middle of reprovision.
frederic-hoerni
requested changes
Sep 23, 2026
frederic-hoerni
approved these changes
Sep 23, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
In order to be able to prevent removing keyslots for which we have the only key for the containers, we need to be able to check specific keyslots.
We typically only know the key that got registered in keyring during boot. And they come from sealed key that we usually cannot unseal again later. If we remove any of those keyslots because an unexpected keyslot was used for activation, then we lose ability to act on the container, until we reboot and a different keyslot gets used.
Unexpected keyslot might used if we for example lose power or hard reset in the middle of reprovision.