Skip to content

feat(enforcement): safely start protected guests and bounded agents - #942

Merged
antropos17 merged 19 commits into
masterfrom
codex/protected-guest-start-20261015
Oct 16, 2026
Merged

antropos17 merged 19 commits into
masterfrom
codex/protected-guest-start-20261015

Conversation

@antropos17

@antropos17 antropos17 commented Oct 15, 2026 •

Copy link
Copy Markdown
Owner

Protected VMs could be provisioned while Off but had no protected live guest/agent startup API. This adds an administrative run from the original creation association: trusted offline VHDX hydration into the original disk file ID, one-use native start, fixed hardware/private storage checks, no NICs, and confirmed Off before registration refresh and removal.

Administrative PS Direct targets only that created VM ID. A fresh Users-only account receives an enforced 512 MiB NTFS quota. Its private, pinned executable starts suspended, joins a kill-on-close Job, passes SID/groups/elevation/session/image/birth checks, and resumes with an explicit environment on a private desktop. The Job limits aggregate memory to 512 MiB and execution to two minutes. Success requires whole-Job and desktop closure. Running VHDX protection uses metadata identity and the private High-integrity namespace because VMMS needs exclusive data access. Unknown settlement retains state.

Native state and Hyper-V cmdlet state must agree before admission. A short native probe confirmed approximately 3.1 seconds of cmdlet lag; bounded re-observation never retries the provider and refuses native state loss. The validator derives the Windows vmWorkerProcess capability and recognizes it only on the original GUID's configuration leaves with finite file masks. Normal principal, High-integrity namespace, media and foreign-file checks remain required; no ACL is broadened or repaired. Startup diagnostics export only scoped event IDs and named numeric error fields.

Validation on exact source 5113e3b:

  • 64 local Windows behavior/regression tests passed on the committed functional inputs. All five required contexts passed in CI38847005614.
  • Native38847001856 passed actual firmware start/stop/Off, provisioning, hydration, upgrade/rollback and uninstall. 67 source/payload bindings and five compiled outputs were reconciled.
  • Windows38847307744 passed actual protected OS/agent startup, standard-token checks, enforced quota refusal, private-namespace write denial, argument preservation, descendant cleanup, original disk identity, Off and removal. 237 source/payload bindings and five compiled outputs were reconciled. Raw receipt: 914833 bytes, SHA256 1a57cc9ff55c12b34d0cafb8d2e2f73f069eccc2c5a4996037701ab7215e5ba0.

The user approved only the full guest runner change to windows-2025-vs2026; capacity guards and the 45-minute job limit are preserved. The base image and guest administrative credentials remain trust inputs. This repository administrative API remains separate from ordinary caller launch, provider and production acceptance. The installed-owner dispatcher stays inspection-only; A1-A4 remain UNREVIEWED and launchAllowed=false. Earlier failed observations retain their original results.

@antropos17
antropos17 merged commit 6001f2c into master Oct 16, 2026
11 checks passed
@antropos17
antropos17 deleted the codex/protected-guest-start-20261015 branch October 16, 2026 04:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant