Skip to content

Require the elevated Windows sandbox for network proxies - #32857

Merged
copyberry[bot] merged 1 commit into
mainfrom
copyberry/codex-internal-to-codex-oss/bfa1dda98594e0db61883f8e7f65bd560e3453e6
Jul 13, 2026
Merged

Require the elevated Windows sandbox for network proxies#32857
copyberry[bot] merged 1 commit into
mainfrom
copyberry/codex-internal-to-codex-oss/bfa1dda98594e0db61883f8e7f65bd560e3453e6

Conversation

@copyberry

@copyberry copyberry Bot commented Jul 13, 2026

Copy link
Copy Markdown

Require the elevated Windows sandbox for network proxies

Why

Network proxy enforcement on Windows requires the elevated sandbox backend. Silently selecting that backend for an unelevated configuration makes the effective sandbox differ from the configured mode.

What changed

  • Reject enabled network proxy configurations on Windows unless managed requirements allow only the elevated sandbox and windows.sandbox resolves to "elevated".
  • Preserve the configured sandbox backend during execution and validate proxy compatibility at config loading, sandbox setup, and process launch boundaries.
  • Defer this validation during cloud-config bootstrap so authoritative managed requirements can be loaded first.
  • Do not start or expose disabled Windows proxies, and render transitions to disabled networking as <network enabled="false"></network>.

Testing

  • Cover Windows requirement and sandbox compatibility matrices, bootstrap behavior, backend selection, disabled proxy handling, and environment-context updates.

## Why

Network proxy enforcement on Windows requires the elevated sandbox backend. Silently selecting that backend for an unelevated configuration makes the effective sandbox differ from the configured mode.

## What changed

- Reject enabled network proxy configurations on Windows unless managed requirements allow only the elevated sandbox and `windows.sandbox` resolves to `"elevated"`.
- Preserve the configured sandbox backend during execution and validate proxy compatibility at config loading, sandbox setup, and process launch boundaries.
- Defer this validation during cloud-config bootstrap so authoritative managed requirements can be loaded first.
- Do not start or expose disabled Windows proxies, and render transitions to disabled networking as `<network enabled="false"></network>`.

## Testing

- Cover Windows requirement and sandbox compatibility matrices, bootstrap behavior, backend selection, disabled proxy handling, and environment-context updates.

GitOrigin-RevId: bfa1dda98594e0db61883f8e7f65bd560e3453e6
@copyberry
copyberry Bot force-pushed the copyberry/codex-internal-to-codex-oss/bfa1dda98594e0db61883f8e7f65bd560e3453e6 branch from 2314652 to abbb8c5 Compare July 13, 2026 19:05
@copyberry
copyberry Bot merged commit abbb8c5 into main Jul 13, 2026
14 of 32 checks passed
@copyberry
copyberry Bot deleted the copyberry/codex-internal-to-codex-oss/bfa1dda98594e0db61883f8e7f65bd560e3453e6 branch July 13, 2026 19:06
@github-actions github-actions Bot locked and limited conversation to collaborators Jul 13, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant