feat(exec_allow): whitelist trusted commands with approval + TLS guardrails #180
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.
Summary
exec_allow
config section plus runtime matcher so simple commands (e.g.uv run test*
,docker compose
) can bypass the sandbox while we continue validating that every argv path stays under writable rootsconfirm = true
on those rules so risky escapes still pause for user approval before leaving the sandboxSSL_CERT_FILE
wheninject_ssl_cert_file = true
, sourcing fromCODEX_DEFAULT_SSL_CERT_FILE
or common CA bundle paths sogh
and other TLS clients keep working after the bypassTesting