Repository navigation
v0.5.13
Security maintenance release of the 0.5 guest OS. It contains guest-side fixes backported from dstack 0.6, and makes RTMR[1] independent of the host's QEMU version.
We recommend upgrading to dstack 0.6.4. If you stay on 0.5, upgrade to this image. The OS image hash changes, so the new os_image_hash must be whitelisted in your KMS / DstackKms contract before CVMs can boot with it.
OS image hashes
| Image | os_image_hash |
|---|---|
dstack-0.5.13 |
7924e18cd7b8bb5b96a75c2eed847917cfb740bb3082e4b07e042385979ab309 |
dstack-dev-0.5.13 |
f2649ed001abed3b8684ba15e6f421f0155b29e222f68a2ef3bf280787bdbfee |
dstack-nvidia-0.5.13 |
d55fdef0fc97b8e9c2d94d569cb9756e0df5215529c240ab955b561105635b36 |
dstack-nvidia-dev-0.5.13 |
58b6f2bae657f2a7651c17cafb9954178dcc5e245d60b6dc549f0c630b662297 |
metadata.json keeps ovmf_variant: pre202505 and adds kernel_header_normalized: true.
meta-dstack changes (v0.5.12 → v0.5.13)
- Normalize the kernel setup header so RTMR[1] does not depend on the QEMU version (#84, backport of Dstack-TEE/dstack#1189 and #1229). QEMU 10.2 and later no longer write the boot-loader fields of the setup header for confidential guests, so 0.5.12 and earlier images measure a different RTMR[1] on those hosts and fail KMS verification. The shipped
bzImagenow carries the values QEMU 10.1 and earlier write, and an OVMF patch writes the same values before measuring, so the measurement is the same on every QEMU version and KMS/VMM releases that do not knowkernel_header_normalizedstill compute it. - Bump version to 0.5.13; the
dstacksubmodule now points to the 0.5.13 release commit.
dstack submodule changes (v0.5.12 → v0.5.13)
Guest security fixes: refuse to boot when an encrypted env cannot be decrypted, validate the gateway's WireGuard fields before rendering the wg-quick config, require TLS key possession from attested servers such as the KMS, and rustls-webpki 0.103.16 for the emSign CA compromise. See dstack v0.5.13 release notes.
Full commit log: v0.5.12...v0.5.13