-
Notifications
You must be signed in to change notification settings - Fork 83
Process container: permissive UI policy values are not grantable #1245
Copy link
Copy link
Open
Labels
Backend-ProcessContainerWindows ProcessContainer behavior, including BaseContainer and AppContainer isolation tiers.Windows ProcessContainer behavior, including BaseContainer and AppContainer isolation tiers.Issue-BugSomething is not working as intended.Something is not working as intended.OS-WindowsApplies specifically to Windows hosts or Windows behavior.Applies specifically to Windows hosts or Windows behavior.Priority2High-impact issue affecting key functionality; prioritize for the next appropriate release.High-impact issue affecting key functionality; prioritize for the next appropriate release.Release v1.0Issues tracked for the version 1.0 releaseIssues tracked for the version 1.0 release
Description
Activity
Metadata
Metadata
Assignees
Labels
Backend-ProcessContainerWindows ProcessContainer behavior, including BaseContainer and AppContainer isolation tiers.Windows ProcessContainer behavior, including BaseContainer and AppContainer isolation tiers.Issue-BugSomething is not working as intended.Something is not working as intended.OS-WindowsApplies specifically to Windows hosts or Windows behavior.Applies specifically to Windows hosts or Windows behavior.Priority2High-impact issue affecting key functionality; prioritize for the next appropriate release.High-impact issue affecting key functionality; prioritize for the next appropriate release.Release v1.0Issues tracked for the version 1.0 releaseIssues tracked for the version 1.0 release
Relevant area(s)
Windows
Brief description of your issue
Permissive UI policy values are not grantable in the process container. Setting
processContainer.ui.desktopSystemControltotrue,processContainer.ui.systemSettingstodisplay,parameters, orall, orui.clipboardto a permissive value still leaves the capability blocked inside the sandbox.This is 36 failing assertions in the 2026-09-23 nightly run, on every Windows job:
Two things narrow this down:
processContainer.ui.isolationis fully bidirectional on all four hosts.isolation=desktop -> HANDLES=allowedpasses,isolation=handles -> HANDLES=blockedpasses, and the negative control passes. So the UI plumbing works in general.resolve_ui_restrictions(src/core/wxc_common/src/ui_policy.rs:68-122) computes the mask correctly, so the loss is below that layer. It reproduces on both the job object path (T3) and the PSEC spec path (T1), which suggests it is not specific to either mechanism.Steps to reproduce
tests/scripts/run_processcontainer_ui_policy_matrix_test.ps1on any supported Windows host.Expected behavior
docs/process-container/UIPolicy_Schema.md:95anddocs/process-container/os-version-support.md:177-182document all three of these as supported on every build, so a permissive value should leave the capability usable.Actual behavior
The UI probe reports the capability blocked no matter what was configured:
Either enforcement is wrong or the support matrix is. If the matrix is wrong, the docs should say these are always denied and the tests should be updated to match.