Skip to content

dstack v0.6.5

Latest

Choose a tag to compare

@kvinwang kvinwang released this 16 Nov 04:57
· 4 commits to next since this release
350a0a7

dstack 0.6.5 adds KMS-enforced launch tickets: key release can require a secret ticket that the host presents at launch, checked by the contract before the KMS releases anything. The KMS contracts are not compatible with 0.6.4 — DstackKms, every DstackApp and auth-eth must be upgraded together (see Upgrade notes).

Components

Component Release Image
Guest OS mkosi-os-v0.6.5 os_image_hash: 4771a29e03e93f0e2d5e37174cd8bb1112942c9689deb36b16c5df9e183d8623
KMS kms-v0.6.5 ghcr.io/dstack-tee/dstack-kms:0.6.5@sha256:67a5b4433b4d098fd42731defbc31bd3c175a415e2a1868dc5d457b375cb9a11
KMS auth-eth kms-auth-eth-v0.6.5 ghcr.io/dstack-tee/dstack-kms-auth-eth:0.6.5@sha256:9fa32227756f611905e59396dcddeb9a4f98f4e0c95969d4cbe7d7ec61bbe537
Gateway gateway-v0.6.5 ghcr.io/dstack-tee/dstack-gateway:0.6.5@sha256:ce35bc457fa0eafc031c2901c57406a5fb400ad1d81f89747cdc5a00d3113adb
Verifier verifier-v0.6.5 ghcr.io/dstack-tee/dstack-verifier:0.6.5@sha256:a8f4d606ec53bbbf05bb128d618de1de8fbe2f0b8679d326b34710260a290ca4

The 0.5 guest line gets the guest side of launch tickets in v0.5.15.

Highlights

  • Launch tickets. DstackApp.setRequireLaunchTicket / addLaunchTicket gate
    app keys and certificates; DstackKms.setRequireKmsLaunchTicket /
    addKmsLaunchTicket gate the root key import of a joining KMS. The VMM keeps
    the ticket and returns only its hash; vmm-cli launch-ticket new|hash,
    deploy --launch-ticket-file and update --launch-ticket-file manage it.
    See launch tickets.
  • KMS onboarding pins the source to the root CA registered with the
    joiner's auth backend, so the ticket and source_token reach only a KMS
    holding the registered roots; http:// sources are refused.
  • Listener settings of the KMS and gateway move to [listeners.*], with an
    optional read-only KMS [listeners.public] and PROXY protocol support.
  • Audit logs: refused KMS key requests, gateway admin RPCs and CVM
    registrations, and one gateway access line per proxied connection.

Upgrade notes

  1. Contracts and auth-eth together. AuthorizationRequest gains
    launchTicketHash, which changes the authorizeApp / authorizeKms
    selectors and the IAppEpochAuth interface ID (0xd33835bd →
    0xc396c1b0). A 0.6.4 auth-eth with 0.6.5 contracts, or the reverse, denies
    every request, and a 0.6.5 DstackKms treats a 0.6.4 DstackApp as a
    legacy policy limited to app epoch 0. Upgrade the DstackKms proxy, every
    DstackApp proxy and setAppImplementation, then deploy the 0.6.5
    auth-eth; see the KMS release notes.
    Upgraded contracts require no ticket until their owner turns it on.
  2. KMS. Move the listener settings to [listeners.*]; the KMS refuses the
    0.6.4 locations and names where each moved. Upgrade the auth backend before
    the KMS: onboarding needs rootCaPubkey on its GET / and an https://
    source.
  3. Gateway. A hand-written gateway.toml must move its listener settings
    to [listeners.*]; the gateway image's entrypoint writes the new layout.
  4. Guests. Register the 0.6.5 os_image_hash, then deploy. To require app
    tickets, the host needs dstack-vmm 0.6.5 and the guest OS 0.6.5 (or 0.5.15).
    Turn on setRequireKmsLaunchTicket only after every KMS runs 0.6.5.

Full changelog: CHANGELOG.md