Repository navigation
Protect .aws directories under sandbox writable roots - #48176
Merged
copyberry[bot] merged 1 commit intoSep 25, 2026
Merged
copyberry[bot] merged 1 commit into
copyberry[bot] merged 1 commit into
Conversation
## Why AWS profiles can select credential helpers that the application executes. Granting write access to a containing directory should therefore keep `.aws` protected by default. ## What changed Add `.aws` to the protected metadata paths alongside `.git`, `.agents`, and `.codex`, including workspace roots and additional writable roots. Preserve explicit user rules that override the default protection. ## Testing Extend policy and sandbox tests to cover `.aws` protection. Add macOS coverage for existing and absent `.aws` directories, deletion and replacement attempts, and symlink targets. Verify that Linux sandbox writes to protected configuration files fail while sibling files remain writable. GitOrigin-RevId: 31ea287bd0dd9b13aff893783fba9ca3aed0c89d
copyberry
Bot
force-pushed
the
copyberry/codex-internal-to-codex-oss/31ea287bd0dd9b13aff893783fba9ca3aed0c89d
branch
from
September 25, 2026 19:14
a2fe896 to
1d804e9
Compare
copyberry
Bot
deleted the
copyberry/codex-internal-to-codex-oss/31ea287bd0dd9b13aff893783fba9ca3aed0c89d
branch
September 25, 2026 19:14
danielchristiancazares
deployed
to
issue-triage
September 25, 2026 19:35 — with
GitHub Actions
Active
danielchristiancazares
deployed
to
issue-triage
September 25, 2026 19:35 — with
GitHub Actions
Active
danielchristiancazares
deployed
to
issue-triage
September 25, 2026 19:35 — with
GitHub Actions
Active
danielchristiancazares
deployed
to
issue-triage
September 25, 2026 19:36 — with
GitHub Actions
Active
This branch was successfully deployed
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Protect
.awsdirectories under sandbox writable rootsWhy
AWS profiles can select credential helpers that the application executes. Granting write access to a containing directory should therefore keep
.awsprotected by default.What changed
Add
.awsto the protected metadata paths alongside.git,.agents, and.codex, including workspace roots and additional writable roots. Preserve explicit user rules that override the default protection.Testing
Extend policy and sandbox tests to cover
.awsprotection. Add macOS coverage for existing and absent.awsdirectories, deletion and replacement attempts, and symlink targets. Verify that Linux sandbox writes to protected configuration files fail while sibling files remain writable.