Skip to content

Avoid sharing violations when repairing Windows runtime ACLs - #51822

Merged
copyberry[bot] merged 1 commit into
mainfrom
copyberry/codex-internal-to-codex-oss/2e087b51adc0221d0eda061fa0a34d2e98409662
Oct 7, 2026
Merged

copyberry[bot] merged 1 commit into
mainfrom
copyberry/codex-internal-to-codex-oss/2e087b51adc0221d0eda061fa0a34d2e98409662

Conversation

@copyberry

@copyberry copyberry Bot commented Oct 7, 2026 •

Copy link
Copy Markdown

Avoid sharing violations when repairing Windows runtime ACLs

Why

Opening active EXE/DLL files with MAXIMUM_ALLOWED can request access that causes sharing violations during sandbox runtime ACL repair.

What changed

Restrict MAXIMUM_ALLOWED opens to directories that need to suppress child ACL propagation. For files, request READ_CONTROL | WRITE_DAC only when an ACL update is needed.

Preserve the non-inheriting grant behavior from #49690, including existing permissions, deny ACEs, and null DACLs.

Testing

Extend the Windows runtime repair regression test to hold node.exe open with FILE_SHARE_READ throughout repair and revalidation, while checking read/execute access and preserved denials.

## Why

Opening active EXE/DLL files with `MAXIMUM_ALLOWED` can request access that causes sharing violations during sandbox runtime ACL repair.

## What changed

Restrict `MAXIMUM_ALLOWED` opens to directories that need to suppress child ACL propagation. For files, request `READ_CONTROL | WRITE_DAC` only when an ACL update is needed.

Preserve the non-inheriting grant behavior from #49690, including existing permissions, deny ACEs, and null DACLs.

## Testing

Extend the Windows runtime repair regression test to hold `node.exe` open with `FILE_SHARE_READ` throughout repair and revalidation, while checking read/execute access and preserved denials.

GitOrigin-RevId: 2e087b51adc0221d0eda061fa0a34d2e98409662
@copyberry
copyberry Bot force-pushed the copyberry/codex-internal-to-codex-oss/2e087b51adc0221d0eda061fa0a34d2e98409662 branch from 00d22b7 to dd12f89 Compare October 7, 2026 20:47
@chatgpt-codex-connector

Copy link
Copy Markdown
Contributor

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
πŸ“ Code Review πŸ”„ Running since 2026-10-07T20:47:08.848121Z 00d22b7 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with πŸ‘€ while any review is running, comments if it has suggestions, and reacts with πŸ‘ once all reviews finish with no findings.

@copyberry
copyberry Bot merged commit dd12f89 into main Oct 7, 2026
1 check failed
@copyberry
copyberry Bot deleted the copyberry/codex-internal-to-codex-oss/2e087b51adc0221d0eda061fa0a34d2e98409662 branch October 7, 2026 20:47
@github-actions

github-actions Bot commented Oct 7, 2026

Copy link
Copy Markdown
Contributor


Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.


I have read the CLA Document and I hereby sign the CLA


You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.

@github-actions github-actions Bot locked and limited conversation to collaborators Oct 7, 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