Repository navigation
Check Security sandbox capabilities during Setup - #967
Merged
Merged
Conversation
The Setup sandbox paragraph changed docs/guide.md without updating its checked-in HTML, causing site-test's documentation freshness check to fail. Validation: cd site && npm test (36 tests passed).
This was referenced Oct 21, 2026
Merged
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Setup now warns about missing Security sandbox capabilities before a session needs them.
The probe uses a temporary local listener, a throwaway HOME and a three-second sandbox deadline. It executes only trusted built-in checks. A passing result covers these capabilities; sessions still enforce the complete Security audit skill policy. A contract test detects changes to that policy's isolation requirements.
Closes #608
Evidence
cargo test --test setup security_sandbox_start_failure_warns_and_still_writes_the_user_config -- --exactfailed because Setup printed no sandbox warning.After: the same test passes and verifies that the config is completed despite bwrap failure, with installation and AppArmor commands printed.
cargo check, all 30 Setup tests,cargo fmt --check, andcargo clippy --all-targets -- -D warningspass.cargo testsuite passes on Linux (exit 0).Test seams
thirdshift setupthrough its CLI, User config, terminal output and sandbox executable on PATH.Review coverage
Independent Standards and Spec reviews against
main(455558de1e4677c699908c3331e8f99354307657). Both reviewed every changed file:docs/guide.md,src/main.rs,src/setup.rs,src/setup/sandbox.rs, andtests/setup.rs. Unread changed files: none. Generated-output exclusions: none.Unaddressed findings
Security review outcome
Merge Danger
Door: two-way
Revert to remove the warning. Setup never installs packages, loads AppArmor policy, changes sysctls, or requests root.
Blast Radius: Setup
Security-enabled Setup performs a brief local capability probe. A failed probe leaves the saved User config usable. macOS reports unavailability; Linux behavior was exercised locally.
Built with codex · gpt-6.1-sol · high