docs(readme): reframe security model around trust zones - #4
Merged
Conversation
The old section was a list of implementation details (RLIMIT_CORE, Aho-Corasick, SIGTERM timings) that told a reader how Airlock works but not why it matters. Recast it as three trust zones: the daemon running unsandboxed as the user, the agent in a sandbox shaped for an agent, and each tool in its own sandbox shaped for that tool. Two points were previously implicit and are now stated outright: the daemon deliberately runs outside any sandbox (it needs the user's real logins to mint scoped tokens), and per-tool sandboxing is the property most comparable setups lack. The low-level mitigations survive as a single paragraph; the full detail stays in SECURITY.md.
The "different jobs" paragraph implied a tool needs only a credential, which glosses over tool config files. Spell out that those can be redirected to a project-local path (CLOUDSDK_CONFIG, KUBECONFIG) so a sandboxed gcloud or kubectl never sees the user's privileged global login, only the minted token.
Drop the "run tool X" aside and the closing "union" sentence, which overstated the point; soften "nothing else" to "usually" since tools vary in what they need.
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
1 participant
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
Rewrites the README Security model section to be less about implementation details and more about what the design buys you.
RLIMIT_CORE/PR_SET_DUMPABLE/ Aho-Corasick / SIGTERM timings to a single "under the hood" paragraph; full detail remains in SECURITY.md.No code changes; SKILL.md / ARCHITECTURE.md / SECURITY.md are unaffected.
🤖 Generated with Claude Code
https://claude.ai/code/session_014f2HrLhH3agvULQo6HaZ5x