Skip to content

fix(enforcement): deny impersonated retained caller contexts - #819

Merged
antropos17 merged 2 commits into
masterfrom
codex/vm-qualification-followup-20261009
Oct 9, 2026
Merged

antropos17 merged 2 commits into
masterfrom
codex/vm-qualification-followup-20261009

Conversation

@antropos17

@antropos17 antropos17 commented Oct 9, 2026 •

Copy link
Copy Markdown
Owner

After caller authentication returns, the supervisor thread can acquire an impersonation token before an issued context is checked. Require a clean thread before and after the retained peer/pipe fence so an impersonated check fails before its caller can dispatch an effect.

Add a same-principal Windows native regression with an independently observed thread token and a disposable effect counter. The baseline incorrectly permits one effect; corrected source denies it with zero effects, while clean and reverted-thread controls succeed. The existing primitive remains inactive; full E1.2/E1.5/A1, protected provisioning and resource authority remain unqualified.

Validation:

  • Independent GPT-6.1 Sol review of all five frozen files: scoped PASS; reviewer independently executed both native controls. A later documentation-only clarification received a separate independent Sol PASS.
  • Focused Windows caller/context/endpoint suites: 57 passed, no skips. All Windows sidecars build with warnings as errors. Maintained Windows PowerShell 5.1 guest preflight passed; optimized compositions remain within their existing size caps.
  • Full serial Windows coverage: 8244 passed, nine skipped, 472 files. Local renderer build, formatting, lint, TypeScript, Svelte and production dependency audit passed. Both mutation gates and final counts passed; source bindings and receipts are retained.
  • Final CI run 37883626660 on e22ed53 passed all five required contexts: build, lint, svelte-check, test and audit.

The initial four-worker full Windows coverage run had five failures in an unchanged enrollment-lease fixture that excludes CallerAdmission.cs. Its original receipt is preserved. The same suite passed 31/31 in isolation with coverage and one worker; final full serial coverage passed. Directory ancestor timestamp sensitivity is a hypothesis requiring a controlled native experiment, without a claimed cause or fix in this PR.

The first CI run passed its runtime gates but failed the counts scanner's interpretation of a test-count phrase in the new document. The wording now keeps the same observed counts without triggering that unrelated source-size match; the scanner and declared repository counts are unchanged.

@antropos17
antropos17 merged commit 428f96e into master Oct 9, 2026
5 checks passed
@antropos17
antropos17 deleted the codex/vm-qualification-followup-20261009 branch October 9, 2026 04:29
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