Issues

Issues

• Make cc-eventlog / verification core usable as a downstream dependency

  Dstack-TEE/dstack#1515 · opened on Nov 4, 2026

• kms: canary bounties that revoke an OS image when a boundary is shown broken

  Dstack-TEE/dstack#1486 · opened on Oct 26, 2026

• kms: record OS image version and dev flag on-chain in the next-gen contract

  Dstack-TEE/dstack#1384 · opened on Sep 24, 2026

• auth-simple: duplicate app keys differing in case silently shadow the tighter entry, and a backend migration moves policy authority with no observable signal

  Dstack-TEE/dstack#1301 · opened on Sep 20, 2026

• contracts: DstackKms.initialize accepts a zero appImplementation, which docs/specification.md §3.1 says must revert

  Dstack-TEE/dstack#1300 · opened on Sep 20, 2026

• contracts: setKmsQuote and setKmsEventlog are the only owner mutations that emit no event, so the published KMS evidence can be rewritten silently

  Dstack-TEE/dstack#1299 · opened on Sep 20, 2026

• contracts: the three DstackKms allowlist setters still accept bytes32(0), and #1268's OS-image fix depends on allowedOsImages[0] being false

  Dstack-TEE/dstack#1298 · opened on Sep 20, 2026

• contracts: the documented app upgrade is add-only, so the withdrawn compose hash stays bootable with identical keys

  Dstack-TEE/dstack#1297 · opened on Sep 20, 2026

• GCP TDX image identity rests on one lane: MRTD/RTMR0-2 are never compared, and PCR7/PCR12 are not quoted although AWS NitroTPM binds both

  Dstack-TEE/dstack#1296 · opened on Sep 20, 2026

• dstack-mr diagnose lists RTMR0 ACPI inputs the generator does not consume (hpet, host_share_mode) and omits two it does

  Dstack-TEE/dstack#1295 · opened on Sep 20, 2026

• validate_v2_preimages is documented as binding RTMR replay to displayed fields, but inspects the event list that is not replayed

  Dstack-TEE/dstack#1294 · opened on Sep 20, 2026

• contracts: an app can never be deregistered, so the KMS owner's only revocation lever is the global OS-image allowlist

  Dstack-TEE/dstack#1293 · opened on Sep 20, 2026

• Verifier result contract is not platform-uniform: the same fields mean different things on each TEE variant, and nothing tells the relying party

  Dstack-TEE/dstack#1292 · opened on Sep 20, 2026

• The os-image-hash RTMR3 event records the key provider's answer, is emitted only on the KMS path, and has no reader

  Dstack-TEE/dstack#1291 · opened on Sep 20, 2026

• contracts: removeDevice is inert while allowAnyDevice is true, and both the mapping and the audit event report a revocation that changed no decision

  Dstack-TEE/dstack#1290 · opened on Sep 20, 2026

• sign_csr stamps an app-info certificate extension whose device_id and os_image_hash the issuer never verified

  Dstack-TEE/dstack#1289 · opened on Sep 20, 2026

• KMS key derivation: the disk-key HKDF context is an unframed concatenation, and only one of the two BootInfo producers maintains the width invariant it relies on

  Dstack-TEE/dstack#1288 · opened on Sep 20, 2026

• KMS root keys: state the no-rotation compromise, its blast radius, and the indirection that would make recovery possible

  Dstack-TEE/dstack#1287 · opened on Sep 20, 2026

• Rate-limit expensive RPCs to prevent resource exhaustion

  Dstack-TEE/dstack#1273 · opened on Sep 20, 2026

• vmm: boot and periodic log rotation copy files on async workers

  Dstack-TEE/dstack#1270 · opened on Sep 20, 2026

• verifier: performance findings — a quadratic pre-signature replay, five parses of one blob, and two binaries named dstack-mr

  Dstack-TEE/dstack#1261 · opened on Sep 20, 2026
  1

• guest OS: performance findings — boot-path forks, per-request /proc walks, and an inert worker setting

  Dstack-TEE/dstack#1260 · opened on Sep 20, 2026

• kms: performance findings — eight serialized round trips on every CVM boot

  Dstack-TEE/dstack#1259 · opened on Sep 20, 2026

• gateway: performance findings from a hot-path sweep

  Dstack-TEE/dstack#1258 · opened on Sep 20, 2026
  1

• dstack review for CCC TAC

  Dstack-TEE/dstack#1218 · opened on Sep 14, 2026
  1