proof: Write Restricted Code SID is load-bearing#48
Closed
marksverdhei wants to merge 10 commits into
Closed
Conversation
Reconcile the queued dependency updates across Cargo, Bazel, pnpm, and CI metadata. Harden timing-sensitive integration fixtures, add deterministic cross-call synchronization, and update strict-clippy compatibility without changing production behavior beyond the dependency refresh. Acting-Agent: chloe
Run non-cancelled post-merge Windows coverage on both integration branches and update the fork guide to consistently name clanker as the default branch. Acting-Agent: chloe
Normalize Windows paths in app-server and avatar assertions, give shell-command unit tests hosted-runner headroom, and use the Restricted Code SID instead of Everyone for restricted-token initialization without weakening world-writable path isolation. Acting-Agent: chloe
Use a temporary absolute project path for the memory scope fixture and compensate path-normalized TUI snapshots for the Windows drive-prefix width before rendering. Linux snapshot geometry remains unchanged. Acting-Agent: Chloe
Exercise the actual WRITE_RESTRICTED token against protected ACL fixtures. Everyone-only write access must remain denied, while an ACL explicitly granting Restricted Code must allow the hosted-runner compatibility path. Acting-Agent: Chloe
Guard the restricted-token impersonation so a failing assertion cannot leave the Windows test thread impersonated. Explicit successful reversion remains checked. Acting-Agent: Chloe
Use the Write Restricted Code SID for write-restricted process compatibility without allowing Everyone-only writes. Normalize Windows fixtures centrally and give asynchronous hook, rollback, and ConPTY tests deterministic readiness and deadline contracts. Acting-Agent: chloe
Resolve private desktop names from the process window station, inherit the caller desktop for default launches, and grant the restricted logon SID the station and desktop rights required by user32 initialization.\n\nActing-Agent: chloe
Canonicalize the temporary home before deriving a project key so Windows path identity matches the storage contract.\n\nActing-Agent: chloe
Remove only SID 70 from the production restricting-SID list while retaining the executable ACL regression. The const-level dead-code allowance is an inert proof-branch compile aid.\n\nExpected result: Everyone-only denial passes and the Write Restricted Code allow assertion fails.\n\nActing-Agent: chloe
Contributor
Author
|
Superseded before evidence by the security-amended candidate 2577171. No result from this stale-parent proof will be used. Acting-Agent: Chloe |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Remove SID 70 from the exact PR #46 candidate while retaining the protected-ACL executable regression unchanged. This draft exists only to run hosted Windows CI and will not merge.\n\nExpected proof: the Everyone-only denial remains green, then the Write Restricted Code allow assertion fails with AccessDenied.\n\nActing-Agent: chloe