You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 37db4f7
Browse filesBrowse the repository at this point in the historyBrowse files
fix(sandbox): a linked tool's install root is granted by one rule; the uv special case goes
- A PATH entry that links to `<root>/bin/<name>` grants `<root>` read-only, so an interpreter's `lib` beside its `bin` is inside the jail whatever installed it; a link not under a `bin` grants its directory as before; a root that is home, an ancestor of it or an agent6 private dir keeps the `bin` grant and the row says so.
- The uv interpreters grant, its constant and its description go; uv's pythons are covered through their shims.
Security review note: the grant widens from a linked tool's `bin` to its install root, read-only, for tools the operator linked onto PATH; the home and private-dir refusals now also apply to resolved paths.
Copy file name to clipboardExpand all lines: docs/security.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -169,7 +169,8 @@ Config, flag, and env var are operator-only; the model reaches neither argv nor
169
169
agent6 warns about such a grant at run start and in `agent6 check sandbox`.
170
170
Under `full`, agent6 hides only its own config dir and state base, plus the paths in `sandbox.hide_paths`
171
171
- the paths kept read-only inside the workspace (`.git` under `protect_git`, a machine bundle) are bound after every grant: a grant that contains the workspace does not make them writable
172
-
- a tool dir is mounted only when its identity clears a default-deny.
172
+
- a symlink into `<root>/bin` grants `<root>` read-only only if no jail PATH directory lies at or under `<root>`; other targets grant their directory.
173
+
A refused root keeps the `bin` grant.
173
174
Refused: a dir at, inside, or containing an agent6 private dir, and `$HOME` or an ancestor of it
174
175
- a fork's execution or a `run --worktree` run (cwd is its linked worktree) also grants the repository's `.git`: a read-only bind under `full`, a Landlock read+exec rule under `partial`, in both cases whatever `protect_git` says.
175
176
The main checkout's `.git` is read-only only under `full` with `protect_git`, so a worktree's is the more confined of the two.
0 commit comments