Skip to content

v0.5.14

Choose a tag to compare

@kvinwang kvinwang released this 13 Nov 13:04
fe05e53

Maintenance release for the 0.5 line. It adds the guest side of the 0.6.4 KMS key epoch migration, so 0.5 guests keep booting after the KMS rotates its root key epoch or an app's key epoch. It ships in the meta-dstack v0.5.14 guest OS image. KMS, Gateway and Verifier are unchanged, so there are no new component releases.

We recommend upgrading to dstack 0.6.4. The 0.5 line receives fixes only.

Why upgrade before a rotation

A 0.6.4 KMS answers a key request that names no epoch with the keys of the current epochs. After a rotation, a 0.5.13 or older guest gets keys that open neither its data disk nor its encrypted env, and fails to boot. Upgrade every 0.5 guest to 0.5.14 before activating a new root epoch or advancing an app epoch.

Guest setup (dstack-util)

  • Data disk: when the current key does not unlock the disk, the guest fetches the key of the epochs recorded on the disk from the KMS and re-keys the LUKS2 keyslot to the current epochs. Each step is crash-safe, and the disk records the new epochs in a dstack-kms LUKS token. A disk that was never rotated is left untouched (#1574).
  • Encrypted env: the guest accepts SealedEnv (HPKE) envelopes. If the current key cannot open a legacy encrypted env, it uses the keys of older epochs. A migrated env is re-sealed to the current epochs and handed to the VMM with UpdateSealedEnv, which also closes the env update window before applications start (#1574).
  • Historical key requests: these pin the KMS root CA established at boot and do not extend RTMR3 (#1574).
  • LUKS2 header validation: the 0.6.4 parser replaces the luks2 crate check. It keeps every existing check, additionally requires the two header copies to agree, and accepts the single dstack epoch token and, during a migration, a second keyslot (#1574).

Operational notes

  • Persisting the migrated env needs dstack-vmm 0.6.4. The 0.5.14 image declares sealed_env support so the VMM can store it. Under an older VMM the guest repeats the env migration on every boot.
  • Keep old-epoch policy until migration finishes. Do not revoke the policy of old epochs until every VM has migrated its disk and stored env.
  • Downgrades: a migrated disk or env cannot be opened by an older image.
  • App GetKey results change after a rotation. They are derived from the current epochs, and 0.5.14 does not expose historical application keys. Applications that need old keys should upgrade to 0.6.4, which serves them over the v1 API.

Full commit log: v0.5.13...v0.5.14