dejima/dejima
1
0
Fork 0
Code Issues 29 Pull Requests Actions Packages Projects Releases Wiki Activity

Stop inviting the isolated mode to be used for untrusted work

Browse Source 
The pointer to security.md said it was worth reading "before using this for
anything you would not run against your own checkout", which reads as an
offer the threat model does not make: its stated premise is that the
project is one you already trust, and nothing about this flag changes that.
It narrows what a session can read of the host and what credential it
carries, which is not the same claim.
This commit is contained in:
branderson
2026-10-11 01:01:49 -07:00
parent a6e1de5f30
commit f0513208a1
1 changed files with 1 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/configuration.md
+1 -2
View File
@@ -1135,8 +1135,7 @@ Withholding that key too, for any launch whose workflow never pushes, is
**Why each of those is the way it is**, and why this is a narrower blast
radius rather than a stronger sandbox, is in
[docs/security.md](security.md#a-session-with-no-project-mounted). Worth
reading before using this for anything you would not run against your own
checkout.
reading before relying on this mode.
## Reading what a session left behind