Repository navigation
docs: KMS emergency key rotation protocol design - #1516
Merged
1 commit merged intoNov 11, 2026
Merged
1 commit merged into
1 commit merged into
Conversation
kvinwang
force-pushed
the
docs/kms-emergency-key-rotation
branch
2 times, most recently
from
November 6, 2026 05:59
e6ba6a9 to
f15613a
Compare
kvinwang
force-pushed
the
docs/kms-emergency-key-rotation
branch
7 times, most recently
from
November 6, 2026 12:19
02818c8 to
4e30a90
Compare
This was referenced Nov 6, 2026
kvinwang
force-pushed
the
docs/kms-emergency-key-rotation
branch
8 times, most recently
from
November 7, 2026 03:03
3287a9b to
5a8ba5b
Compare
Describe recovery from KMS root-key exposure using a fleet-wide maintenance window: per-epoch roots registered on DstackKms, a single GetAppKey epoch selector (absent = epoch 0, -1 = latest), LUKS2 keyslot rotation with an epoch token, in-CVM env re-encryption, full-history KMS onboarding with a rotation mode, and a clean gateway reset. Signed-off-by: Kevin Wang <wy721@qq.com>
kvinwang
force-pushed
the
docs/kms-emergency-key-rotation
branch
from
November 8, 2026 09:21
a2ab826 to
4b05277
Compare
This was referenced Nov 8, 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
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.
Design draft for recovering from a KMS root-key compromise. Not implemented; this is for design review.
Key points:
DstackKms; every KMS keeps the full key history.GetAppKeystays atapi_version = 1and gains an epoch selector (absent = epoch 0, orlatest); historical epochs are served only untilmigration_until.luksChangeKey) and record the epoch in a token; the volume key is unchanged.