Compare commits

...
Author SHA1 Message Date
Vasanthdev2004 0f2cdb5eeb Merge remote-tracking branch 'origin/main' into feat/windows-sandbox-identity 2026-10-25 19:20:04 +05:30
Vasanthdev2004 1767f2dacf Merge remote-tracking branch 'origin/main' into HEAD 2026-10-21 15:59:33 +05:30
Vasanthdev2004 34129dfb5a docs(sandbox): fix the comment on windowsSandboxRuntimeRootPath
The doc comment above windowsSandboxRuntimeRootPath named
setupWindowsSandboxRuntimeRoot and said the root was created there, but
this function only resolves the candidates; the setup function below it
does the creation. It also said applyWindowsACLPlan skips a target that
does not exist, when it fails the whole run on one, which is why setup
creates every candidate first.
2026-10-21 12:48:58 +05:30
Vasanthdev2004 703884b6a1 fix(sandbox): unwind ACL rollback by path, not by apply order
Rollback walked its snapshots backwards on the assumption that they were
sorted ascending by path, so descendants came off before their
ancestors. The snapshots are in apply order, though, and the deferred
pass appends a group whose target only appeared during the first pass,
which is usually an ancestor of the groups before it (.git after
.git\config), so the ancestor was restored first. Sort a copy by path key
before the walk. Reported by CodeRabbit.
2026-10-17 18:10:40 +05:30
Vasanthdev2004 bf096f05a7 Merge remote-tracking branch 'origin/main' into feat/windows-sandbox-identity 2026-10-17 17:27:01 +05:30
Vasanthdev2004 422e0d3c82 chore: follow the Twigpine module path
main moved the module to github.com/Twigpine/zero in #1105. Rename this
branch's imports to match, including the two in internal/workspaceindex
that main itself still carries until #1153 lands.
2026-10-17 11:50:48 +05:30
Vasanthdev2004 bcddd92eae Merge remote-tracking branch 'origin/main' into feat/windows-sandbox-identity 2026-10-17 11:50:43 +05:30
Vasanthdev2004 16e30a9f18 fix(sandbox): keep the git carveouts in a workspace inside another repository
This reverses 26958ac6 on measurement rather than on argument.

That commit skipped the config and hooks carveouts when an ancestor owned the
git metadata, so Zero would not create a control directory competing with the
ancestor's for git's discovery walk. The consequence it named does not
reproduce: a .git holding only config and hooks is not a valid repository, so
rev-parse still answers with the ancestor, status still works, and a
core.fsmonitor written into that config is never executed. A new test drives
real git and fails if a future git changes that.

What the skip cost is much larger. With no carveout on the root nothing denied
writes to <root>/.git at all, so a sandboxed command could assemble a
repository there by hand, with mkdir and a few file writes and not one git
command among them, and put core.fsmonitor in its config. Zero runs
git -C <workspace> status outside the sandbox from three places, and git
executes it. Main does not have that exposure, because main plans the
carveouts here.

The nested-repository refusal stays. It recognises git creating a repository
and cannot recognise mkdir, so it is the layer that explains itself to an
operator rather than the boundary. The boundary is the deny ACE, back where it
can be enforced at write time.

The setup guard in the refusal test now asserts the opposite of what it did:
it requires config and hooks to be denied, and fails if they disappear again.
2026-09-22 13:20:57 +05:30
Vasanthdev2004 281bc65c71 fix(sandbox): evaluate before planning in sandbox exec, and refuse a nested clone as nested
Two findings from jatmn on the nested-repository guard.

`zero sandbox exec` is documented as taking the path a shell tool takes. A
shell tool is evaluated by the engine and then planned; this went straight to
BuildCommandPlan, so nothing that lives in Evaluate applied. In a workspace
governed by an ancestor repository that is the nested-repository guard, which
is the only thing standing in for the git carveouts setup deliberately does
not plan there, and `zero sandbox exec -- git init` created the repository
with a writable config and hooks. The command now asks the engine first, with
the argv rendered as command text that keeps one argument one word, and a
denial is a denial. Running it from a terminal counts as the approval a
session prompts for and lifts only what that approval lifts.

`git clone` is both a network command and a repository-creating one, and the
network gate ran first. Under the default NetworkDeny a clone in a governed
workspace came back as a network prompt, asking for an approval that could
never make the command runnable, and the reason that decides it was never
shown. The nested-repository refusal does not depend on policy, permission or
mode, so it now comes first.

The rule's limit is written down where the rule is. It refuses git creating a
repository. It is not containment of the .git pathname: a repository
assembled with mkdir and a few writes, an archive or a script is not
recognised, and no static reading of a shell command can recognise all of
them. A test pins that limit so it is not read as coverage.
2026-09-21 14:00:19 +05:30
Vasanthdev2004 df9989eba1 fix(sandbox): resolve git aliases the way git does before the nested-repository guard
The guard classified the first whitespace-separated field of an alias value,
so an expansion carrying its own -c option (alias.a=-c alias.b=init b) or
quotes (alias.a="init") reached init unseen, and both spellings created a
repository in a nested workspace.

Alias values are now split with the rules of split_cmdline (quotes anywhere
in a word, backslash escapes outside single quotes), run through the in-alias
option handling git applies (-c and --config-env push definitions the next
lookup sees, pager switches are skipped, anything else is fatal in git and is
refused here), and followed with per-path cycle detection. Definitions from
the environment the call sets (GIT_CONFIG_COUNT with GIT_CONFIG_KEY_n and
GIT_CONFIG_VALUE_n, and GIT_CONFIG_PARAMETERS) and from --config-env are read
as well; a definition that cannot be read statically refuses. The attached
-cNAME=VALUE spelling is no longer recognised: git rejects it as an unknown
option and nothing runs.

Reported by @gnanam1990.
2026-09-18 12:18:36 +05:30
Vasanthdev2004 56ce081107 Merge remote-tracking branch 'origin/main' into feat/windows-sandbox-identity 2026-09-18 12:02:11 +05:30
Vasanthdev2004 378b38c363 fix(sandbox): resolve an inline git alias chain to its end and fail closed when it has none
The depth cap gave up with false, so a five-link alias chain ending in init
passed the nested-repository guard and git created the repository. The
resolver now follows the chain until a terminal subcommand with the visited
names kept, and under this guard a cycle, a dangling alias or an empty
expansion is a refusal rather than a pass: an alias the analyzer cannot follow
to its end is not evidence that nothing gets created. A five-link chain ending
in status stays allowed.
2026-09-15 14:03:14 +05:30
Vasanthdev2004 738881bc11 Merge remote-tracking branch 'origin/main' into feat/windows-sandbox-identity 2026-09-15 14:02:22 +05:30
Vasanthdev2004 17f55f4e5e test(sandbox,peermsg): resolve the fixture temp physically so the unix regressions run under macOS's /var symlink 2026-09-15 10:32:41 +05:30
Vasanthdev2004 6e980a8aa6 test(sandbox): a created chain step now carries the identity rollback checks 2026-09-15 10:23:57 +05:30
Vasanthdev2004 9b72d0da6a test(sandbox): check the replacement survives before reading the rollback's own report 2026-09-15 10:21:40 +05:30
Vasanthdev2004 c753df3020 fix(sandbox): create the runtime candidates the unelevated plan grants
The unelevated command's plan lists both runtime candidates, but nothing on
that tier created the one this process did not select, so with a fresh usable
cache the runner refused its own plan with "windows ACL target does not exist"
and the command never launched, on every retry. The parent now creates the
missing candidates before the runner starts, where TEMP is still the
operator's, using setup's own ownership and no-follow checks, and leaves an
existing candidate as it is so the grant the previous command applied is not
stripped and reapplied on every launch. A file or reparse point at a
candidate's name is refused by name.
2026-09-15 10:20:19 +05:30
Vasanthdev2004 d3aab2c113 fix(sandbox): put a runtime root's grant back when a setup retry fails
Preparing the runtime candidates rewrote an existing root's DACL with a
protected owner-only descriptor before the ACL transaction had a baseline, so
a retry that failed on the second candidate, or in the apply, returned with the
earlier setup's capability grant gone while the old marker still claimed
success. Setup now snapshots each existing candidate's DACL and identity before
preparation and restores it, protection state included, on every failure that
follows, and after the transaction's own rollback when a later step fails.
2026-09-15 10:20:19 +05:30
Vasanthdev2004 3ef649094d fix(sandbox): bind materialization rollback to the objects it created
The materialization record verified the anchor's identity but recorded the
created children by name, so after setup created .git/config another process
could rename it aside, put an ordinary file at that name beneath the unchanged
anchor, and have a later setup failure delete the replacement. Each created
directory and the leaf file now carry the identity read from the handle that
created them; rollback refuses to descend through a created component that is
no longer that object, and the delete disposition is set on a handle whose
identity was checked, so nothing renamed in between can be the thing removed.
2026-09-15 10:20:19 +05:30
Vasanthdev2004 b7e97c7645 fix(sandbox): validate the runtime root's parent before the lease and open the lease relative to it
prepareSandboxRuntimeLease created the parent by pathname and opened the lease
beside it before ensureRuntimeTreeDirs validated the owned path, so a link or
junction planted at the fallback anchor's reusable v1 child sent the .lease
into another directory and only then failed validation. The parent is now
walked and created without following links, and the lease is opened relative
to a no-follow handle on that validated directory, so a component swapped in
after the check cannot move the open either. Pinned on both platforms with a
redirected v1 and an untouched control.
2026-09-15 10:20:18 +05:30
Vasanthdev2004 b0ffba6391 test(sandbox): own every runtime root a fixture can produce; clean up the second native account by its real key
Tests that redirected only the workspace still ran real setup, preparation and
reclamation against the developer's cache and temp, because those roots come
from separate resolver inputs. isolateSandboxRuntimeRoots now gives each such
fixture its own cache root and temp root, so the preferred candidate and the
fallback both land inside the fixture, and the principal-setup stub redirects
temp as well as cache.

The native round-trip test provisioned its second account under the key derived
from its config but cleaned up with an unrelated literal, which the ownership
guard refused, and registered that cleanup only after the secret read and the
logon could have failed. It now derives the key from a fixture-owned workspace,
registers cleanup as soon as ownership exists, deletes only what it created,
and reports cleanup failures.

peermsg.EnsurePrivateDir closed the descriptor it started with rather than the
one it ended on, leaking the final descriptor on every fallback-runtime
preparation; the deferred close now closes the descriptor currently owned, and
a watermark test pins it at three depths on the success and refusal paths.
2026-09-15 10:10:57 +05:30
Vasanthdev2004 b9d86cee59 test(sandbox): fake the rollback deletion in the mocked fixture; align the smoke's command profile with setup
The mocked provisioning fixture faked creation and ownership but left the
inverse attached to the operating system, so an injected failure after a
faked create reached the real NetUserDel on the current user's C:\ws
principal. The deletion is a seam now, the fixture fakes and records it, and
the created and adopted cases assert exactly which removals were requested.

The real elevated smoke passed its bare profile to the command builder while
the setup builder folded runtime roots into its own, so every command
disagreed with the marker. The command side now carries the augmented
profile, and a portable test pins that the two plans hash the same.
2026-09-15 10:07:44 +05:30
Vasanthdev2004 7330a17f99 fix(sandbox): refuse principal provisioning in the helper, not only in the argument builder
BuildWindowsSandboxSetupArgs refused to serialize a principal opt-in while no
launch path exists, but both shipped entrypoints reach runWindowsSandboxSetup
through the parser, and a handwritten --sandbox-principal 1 passed the caller
check and proceeded to account, secret and ACL provisioning for a principal
nothing can run. The helper now makes the same refusal before its first effect.
The seam harness opens the launch seam for the fixtures that test the flow
behind it, and a new test drives the refusal with the seam closed.
2026-09-15 10:07:44 +05:30
Vasanthdev2004 926a1ebc41 fix(sandbox): resolve an inline git alias before deciding it is not init
In an ancestor-governed workspace with no local .git, the nested-repository
refusal read the literal subcommand token, so git -c alias.bootstrap=init
bootstrap created a repository the profile carves nothing out for. The
classifier now resolves the alias.NAME=EXPANSION settings given on the command
line to the subcommand git will run, following a short alias chain, and treats
a shell alias as creation under this one guard because it cannot be classified.
Harmless aliases and ordinary git use are unchanged.
2026-09-15 10:07:43 +05:30
Vasanthdev2004 5de72bfa4a test(sandbox): pin principal mode in the transport tests and give the derivation test a private root
The two caller-identity transport tests left PrincipalOptIn unset, so with
ZERO_WINDOWS_SANDBOX_IDENTITY=1 in the host environment they stopped at the
launch refusal before reaching the assertions they exist for. They now pin
the mode they need; the opt-in tests keep exercising environment inheritance.

TestTeardownPathDerivationCreatesNothing snapshotted the shared temp directory,
which every other package under test writes to concurrently, and asserted
resolver purity only after preparation had legitimately created the fallback
anchor. It now observes a private root and asserts purity at the boundary
between resolution and preparation.
2026-09-15 09:58:30 +05:30
Vasanthdev2004 c38fcabe67 Merge origin/main into feat/windows-sandbox-identity
Resolves the ACL conflicts with #1040 by keeping both: the anchor that main
attaches to a derived carveout, and the file materialization this branch adds.
The plan apply now opens its target without the branch's blanket ancestor
redirection check and relies on main's anchor containment instead, so a
workspace reached through a junction keeps working and a junction on the
derived tail is still refused. The rollback re-open relies on the recorded
object identity where it has one and keeps the blanket check where it does not.
2026-09-15 09:55:48 +05:30
Vasanthdev2004 8319484383 test(sandbox): compare carveout roots through the profile's own canonicalization
PermissionProfileFromPolicy stores normalizeProfilePath(root), which resolves
symlinks, so comparing against a raw t.TempDir() path matched locally and failed
on both CI runners: macOS reaches the temp directory through /var -> /private/var,
and the Windows runner's profile directory has a short-name expansion. The
carveouts were present in both failures; only the lookup missed them.
2026-09-13 19:23:47 +05:30
Vasanthdev2004 48f6a88fe4 Merge remote-tracking branch 'origin/main' into HEAD 2026-09-13 15:25:48 +05:30
Vasanthdev2004 ecbedb9112 fix(sandbox): keep a nested workspace's own git carveouts
gitMetadataWriteCarveoutSpecs asked the ancestor question unconditionally, so
a workspace nested inside another repository lost its hooks and config
carveouts even when it owned its own .git. That metadata is the workspace's,
not the ancestor's, and nothing compensated: workspaceGovernedByAncestorRepository
answers the same question by testing for a local .git, so it reported such a
workspace as not governed and the initialization refusal never fired. Commands
received plain workspace write access over a live .git/config and .git/hooks,
which is the configuration that decides what git executes.

The ancestor branch is now gated on the lstat error, which makes the condition
literally the test workspaceGovernedByAncestorRepository applies and the shared
doc comment already claimed. It cannot reintroduce the competing-control-directory
problem it was written for, because the carveouts only materialize where .git
already exists and git's discovery walk therefore already stops at this
workspace. A permission failure on the lstat keeps today's behaviour.

Reported by @jatmn.
2026-09-13 15:25:06 +05:30
Vasanthdev2004 08005ef5b3 test(sandbox): pin every selectable runtime root to the granted set
The runtime-root tests all iterate whatever windowsSandboxRuntimeCandidates
returns, so they hold for any self-consistent candidate set, including one
missing an entry. Dropping the temp-derived fallback from that set left all
three green while leaving the root prepareSandboxRuntime falls back to
ungranted, which is the third part of anandh8x's review finding: setup grants
only the initially derived root, so the fallback is not provisioned either.

The new test drives sandboxRuntimeRootFor for both outcomes, the ordinary
cache-derived selection and the one a machine makes when the cache root is
unusable, and asserts each is in the set setup grants. Driven through the
selector rather than by re-deriving the fallback, so it stays true if the
selection rule changes. Removing either candidate now fails it with the path
it would have refused.
2026-09-12 21:30:32 +05:30
Vasanthdev2004 4d3f5dc8cd fix(sandbox): clone is repository creation too, and the dual-role tests stay on test-owned roots
commandCreatesGitRepository knew only init and init-db, while risk.go routes the nested-repository refusal through that flag alone. git clone <url> . into a workspace governed by an ancestor repository lands a root .git whose config and hooks setup never planned carveouts for, the same state init produces, and with network allowed and the shell grant given it came back as an ordinary allow. clone now sets the flag; the network prompt is a separate gate and granting it does not answer this one. The regression drives Engine.Evaluate in a nested workspace with network allowed and the grant given, for the root-target spelling, a global-option spelling and a subdirectory target, with ordinary git operations, git submodule update --init and a standalone workspace as controls.

The dual-role rollback tests handed real setup C:\sandboxhome and C:\ws. The principal and ACL seams intercept the identity work, not the filesystem work: setup materializes runtime candidates under the user cache and TEMP and writes ledgers below the sandbox home, so an ordinary run wrote to the live cache, failed on drive-root permissions, or left host state behind; this box still has a C:\sandboxhome from the old form. windowsSandboxTestConfig now takes the test, uses t.TempDir for home and workspace, redirects sandboxUserCacheDir and TMP/TEMP, and asserts afterwards that the fixed paths were neither created nor changed by the run and that the redirected cache is not the live one. The offline-membership caller follows. Reported by @gnanam1990.
2026-09-12 12:04:32 +05:30
Vasanthdev2004 76d607ecdc Merge origin/main into feat/windows-sandbox-identity
Brings in #1006 (narrow restricted-token SIDs, fail closed on DenyRead) and the rest of main since the last rebase.

Four files conflicted, all unions with #1006:

- windows_acl.go: WindowsACLEntry carries NoInherit (main) beside MaterializeFile (branch); both new actions kept.
- windows_acl_apply_windows.go: DenyWrite mask takes the SYNCHRONIZE strip from main; DenyDelete and RevokeCapability cases both kept.
- windows_acl_test.go: branch assertions re-applied inside ForWorkspaceWriteProfile; the branch test #1006 rewrote under a new name comes back whole beside it.
- windows_setup.go: marker schema stays at 7, which is above main.

Main deleted windowsExplicitAccessEntries in favour of prepareWindowsACLPathGroupEntries, which the branch used for the pre-materialization validity check and in the rename-guard test. Both now call the new builder with a nil DACL, and the rule that a DenyDelete ACE never inherits moves into that builder so no plan can make it inherit.

TestElevatedSetupRefusesAVolumeRootReadGrant now expects the #1006 gate's message, since that gate refuses the same denyRead profile before setup reaches the volume-root refusal; the outcome assertions (refused, never applied) are unchanged, and the SETUP INVALID guard still proves the plan carries the volume-root grant.
2026-09-12 10:35:24 +05:30
Vasanthdev2004 a2e9558262 fix(sandbox): remove a failed secret through the handle that created it
Everything between creating the secret leaf and writing it is
handle-relative and no-follow. The failure path was not: it called
os.Remove on the pathname, which is the one resolution the rest of the
function exists to avoid, and it did not even work. The leaf is created
with FILE_SHARE_READ alone, so a delete by name while that handle is open
is a sharing violation. The error was discarded and the directory unwind
did not cover the file, so a failed provisioning left an empty secret
behind that a later run would read as a stale password.

The handle is closed first and the leaf is then deleted relative to the
pinned parent, the way rollbackWindowsACLMaterialization already removes
what it created. Closing first rather than widening the share mask keeps
the secret unshareable for delete while it exists, which is the narrower of
the two ways to make this work. A cleanup that still cannot finish is
joined into the returned error rather than dropped.

Two seams for the failure paths, since neither is reachable otherwise: the
DACL step, and the delete. My first attempt at the second held a real
second handle on the leaf to block the delete, and it blocked nothing, so
the test passed while proving the opposite of what it claimed.
2026-09-11 10:17:32 +05:30
Vasanthdev2004 8b7ffa4f46 fix(sandbox): treat only a regular .git as the worktree pointer
The rebase kept this branch version of the carveout set, which took the
pointer branch for anything that was not a directory. Main pins the
narrower rule and its tests caught the difference on every platform: a
symlink named .git, dangling or not, and a special entry such as a fifo
are not the gitdir pointer git writes for a linked worktree, so they keep
the legacy child carveouts rather than being handed single-object
protection for not being a directory.

Also picks the runtime-root candidate by excluding the shared fallback
rather than by path prefix. A CI runner spells one directory two ways, so
os.UserCacheDir and t.TempDir disagreed on a path they both meant and the
new junction test failed its own setup check there while passing here.
2026-09-11 10:17:32 +05:30
Vasanthdev2004 a45d4000e1 fix(sandbox): keep the injectable lstat seam through the carveout specs
Main and this branch fixed the linked-worktree .git pointer independently.
The branch version carries the shape each carveout needs, which the Windows
ACL plan uses to materialize .git/config as a file, so it is the one that
survives the rebase. What it lacked was the seam main's worktree tests
drive: an lstat that fails is a real state with its own required answer and
no filesystem it can be staged on. Threaded through the spec function so
both entry points share one implementation.
2026-09-11 10:17:32 +05:30
Vasanthdev2004 b12b2d71a4 fix(sandbox): build the elevated secret and runtime directories no-follow
The secret file was created relative to a pinned parent handle, but the
parent CHAIN was still made with os.MkdirAll. That walks a pathname, so a
junction planted above a component that does not exist yet sent an elevated
create to the other side of it, and the no-follow open that followed then
found an ordinary directory at the requested name because the redirection
had already happened one level up. The runtime-root candidates had the same
create, under the invoking user's own cache tree.

Both now use makeWindowsACLDirChainNoFollow, which anchors on the deepest
existing ancestor and creates each component relative to the handle above
it, and both unwind exactly what they created when a later step fails. The
secret leaf is created relative to the chain's own deepest handle rather
than reopening its parent by name, so the whole operation resolves the path
once.
2026-09-11 10:17:32 +05:30
Vasanthdev2004 9abab7318d test(cli): assert the shutdown status and that nothing outlives the run
The grace tests proved a handler ran and that escalation waited out the bound,
but never looked at the status, which is the only part of this a caller can see
and the part the report was about: 137 rather than 143.

An untrapped child now has to come back as 128+SIGTERM. That is the assertion the
other two cannot make between them, since one traps the signal and the other
ignores it, so a first phase that was still SIGKILL would leave both passing. The
graceful child exits 42 from its handler and the status has to be 42, and the
stubborn child's has to be 128+SIGKILL so "ask nicely and give up" cannot pass
either.

Plan cleanup is ordered after termination by a defer in runSandboxExec wrapped
around this call, which holds only while nothing survives the return. The
stubborn child records its pid and the run has to leave it reaped, so a refactor
that lets Wait come back with the tree still up fails here rather than deleting
the policy-report file underneath a live command.
2026-09-11 10:17:32 +05:30
Vasanthdev2004 d376b7f2f0 fix(sandbox): refuse git init in a workspace inside another repository
A workspace governed by an ancestor repository gets no git carveouts at all.
gitMetadataWriteCarveoutSpecs returns nothing for it, on every backend, and that
is deliberate: naming <root>/.git/config and <root>/.git/hooks makes the Windows
plan create, and the bubblewrap helper mount, a control directory that competes
with the ancestor's for git's discovery walk inside a repository Zero does not
own.

So there is no protection here to extend to a repository created during the
command. It lands under the plain workspace write grant with nothing denying
credential.helper or core.hooksPath, and on Windows nothing denying DELETE on
.git either. The serialized plan never changed, so the cached setup marker stays
valid and the next run does not notice.

Refuse it instead. The protection would have to be established at a moment the
sandbox is no longer at, and reporting success while the guarantee is absent is
worse than refusing.

The condition is the workspace, not the directory the command names. Resolving
that would mean tracking -C and cwd through the script, which is the same
option-parsing surface that let "git -C sub clone" past the network gate.
Refusing a git init aimed elsewhere too is the conservative side of that trade,
and the reason text says so. The detection shares gitSubcommand with the network
gate, so those global options cannot bypass this gate either, and it covers
init-db.

The refusal sits ahead of the persistent grant, session grant and allow-permission
returns in Evaluate: a broad approval to run shell commands is not an approval to
create an unprotectable repository.
2026-09-11 10:17:32 +05:30
Vasanthdev2004 95c8ac6245 fix(sandbox): stop git's global options hiding the subcommand
firstSubcommand skips words beginning with "-" but not the value that follows
one, so the network classifier read the wrong word:

    git clone https://x                  network=true
    git -C sub clone https://x           network=FALSE
    git -c user.name=x clone https://x   network=FALSE

Both spellings are ones an ordinary user types by habit, and both walked
straight through the network gate. "--opt=value" happened to survive because it
is a single token.

git now gets a subcommand parser that knows which of its global options consume
the next word. The keys are lowercase because the analyzer lowercases every
word before this point, which also means -C and -c arrive identically; that is
fine, since both consume a value and nothing here needs to tell them apart.

Found while building the nested-repository check, which needs to recognise
"git init" through the same options. Reported separately rather than folded in,
because it is a live gate bypass rather than part of that finding.

The regression drives AnalyzeCommand rather than the helper, since the gate
reads the analysis and a helper-level assertion would not have caught this. It
keeps local-only spellings classified local, so the fix cannot be "call
everything network".
2026-09-11 10:17:32 +05:30
Vasanthdev2004 c887961869 fix(cli): give a cancelled sandboxed command a graceful phase
The shutdown comments described a graceful signal followed by escalation while
the code did neither. Cancel called KillProcessTree, which is SIGKILL on Unix
and taskkill /T /F on Windows, and WaitDelay only starts counting AFTER Cancel
returns, so it could never postpone a kill that had already happened. A
directed SIGTERM reached the child as 137 rather than 143, with no chance to
flush output, drop a lock file, or run a shutdown handler. The comment
described a policy the code did not implement.

Cancel now calls execution.TerminateProcessTree, the two-phase policy the
background package already uses: SIGTERM, poll for the grace, then SIGKILL what
is still alive. On Windows that resolves to the single-phase kill, which is
correct rather than lazy, since there is no signal to send a child owning no
console. WaitDelay becomes a backstop for the case where the tree is gone but
Wait is still blocked on a pipe a grandchild holds open.

The process-group tradeoff from the previous round is untouched: the child
stays in Zero's group, so terminal and supervisor group delivery is unchanged.

Regressions run a child that traps the signal and records that its handler ran,
and a stubborn child that ignores it and must still die after the bound rather
than before it. Verified on real Linux rather than only cross-compiled, since
the graceful phase does not exist on Windows and a Windows-only run would prove
nothing about it.
2026-09-11 10:17:32 +05:30
Vasanthdev2004 a186eb46d7 fix(sandbox): decide the runtime base on a canonical spelling
The Windows Smoke leg failed on my own new tests with "has no operator-owned
base to descend from" for a perfectly ordinary tree.

runtimeCandidateBase decides ownership with a containment test, and containment
runs on spellings. A runner's temp is C:\Users\RUNNER~1\..., an 8.3 short name
that compares unequal to the long form of the same directory the cache root
resolves to. The same class of mismatch prepareSandboxRuntime already documents
for its own comparison.

ensureRuntimeTreeDirs now canonicalizes before asking, the same way the rest of
the runtime state does.

The tests were the other half of it: a bare t.TempDir() only lands under the
user cache directory on a machine where temp happens to sit there, which is
true on my box and false on the runner. They now pin the cache root
themselves, so they are about the descent rather than about where temp lives.
2026-09-11 10:17:31 +05:30
Vasanthdev2004 8099409f7c fix(cli): terminate the sandboxed command when the wrapper is cancelled
runSandboxPlannedCommand started the backend wrapper with a bare
exec.Command().Run(): no context, no signal forwarding, no shutdown path. A
terminal masks that, because terminals signal the whole foreground process
group, but a supervisor or task runner sending SIGTERM to the `zero sandbox
exec` PID killed only Zero. The wrapper and everything under it kept running,
doing filesystem and network work after the caller considered the task
cancelled, and the deferred plan cleanup never ran because the process was
gone.

The CLI's shared shutdown context is threaded in, Cancel kills the tree, and
WaitDelay bounds how long a child that ignores the first signal can hold the
wrapper open and skip cleanup.

DELIBERATELY WITHOUT execution.ConfigureProcessGroup, which the obvious fix
would add. Putting the child in its own process group closes this hole and
opens a worse one: it severs every kernel-delivered group signal, so a
supervisor escalating to a group kill, and a terminal delivering Ctrl+C to its
foreground group, would stop reaching the child. That was measured, not
assumed: with the group change a group-directed kill left both the child and
its grandchild alive, where today it reaps them. Keeping the child in Zero's
group leaves group delivery exactly as it is, while the directed-signal case,
which reached nothing at all before, now reaches the child.

The remaining gap is a grandchild on the directed-signal path, which the group
path still covers. Closing that too needs a job object on Windows and a group
Zero owns on Unix, which is the trade above and a separate decision.

The existing 128+signal mapping for a child that exits by signal is untouched;
that is a different direction of signalling.
2026-09-11 10:17:31 +05:30
Vasanthdev2004 4234357774 test(sandbox): reproduce the raced leaf at the instant it can actually happen
The first version of this regression used the anchor-stage swap hook, which
fires before the directory chain exists. Creating the parent there made the
chain the RACER's, not this run's, so createdAnything() was false, the ordinary
restore path ran, and the test passed with the fix reverted.

The mixed ownership the finding is about needs the chain to be ours and only
the leaf to be theirs, which is reachable at exactly one instant: after
makeWindowsACLDirChainNoFollow returns and before createWindowsACLChildFile
runs. windowsACLRacedLeafHook makes that instant addressable.

Reverting the disposition check now fails it with the deny ACE still on the
racer's file.
2026-09-11 10:17:31 +05:30
Vasanthdev2004 9608817f47 fix(sandbox): restore a raced leaf whose parent this run created
rollbackWindowsACLSnapshots branched on createdAnything(), which is an OR
across the whole materialization record. When this run creates the parent chain
and a racer wins the leaf, that predicate is true while the ACL-bearing file
belongs to somebody else: Chain carries Made:true and FileMade is false.

The rollback then could not remove the parent, because it was no longer empty,
and the unconditional skip meant the existing no-follow, identity-validated
restore never ran either. A file that existed before setup started was left
wearing an aborted setup's DACL, and the failure was loud about the directory
it could not remove while silent about the descriptor it never put back.

rollbackWindowsACLMaterialization now reports whether the ACL-BEARING TARGET is
among what it removed: the file leaf when FileMade is set, the deepest chain
entry otherwise. Anything it cannot prove it removed reports false, which
routes the caller to the restore that is already no-follow and TargetID-guarded
and refuses on a mismatch rather than forcing.

All three conservative properties are unchanged and none needed new code:
nothing new is ever deleted, so a raced leaf is still never removed; there is
still no pathname fallback; and a rollback that could not remove the parent
still says so while now also restoring the leaf.

The regression is the mixed-ownership case rather than a wholly created
directory becoming non-empty, driven through applyWindowsACLPlan with the leaf
created inside the existing swap hook so the race is deterministic.
2026-09-11 10:17:31 +05:30
Vasanthdev2004 673b84d644 test(sandbox): drive the runtime-tree descent through its entry point
The helper tests call ensureRuntimeTreeDirs directly, so reverting
prepareSandboxRuntime to the old pathname loop left every one of them green.
The defect was in what the entry point called, so it needs a test that goes
through the entry point.
2026-09-11 10:17:31 +05:30
Vasanthdev2004 69c68b18a2 fix(sandbox): stop following sandbox-controlled runtime descendants
The runtime root is deterministic so setup and later runners agree on one path,
and the sandboxed command is granted write access to cache, data and tmp. So it
can replace one of them with a symlink or a Windows junction on its way out.
Preparation then ran os.MkdirAll and os.Chmod on raw pathnames, which follow,
and the HOST Zero process, the ordinary user rather than the confined
principal, created package-cache directories inside a target the previous
command chose.

ensureFallbackRuntimeAnchor proves the per-user anchor and says nothing about
the reusable root or anything beneath it, so it never covered this.

Preparation now descends from the operator-owned base through retained
no-follow handles: NtCreateFile with OBJ_DONT_REPARSE and
FILE_OPEN_REPARSE_POINT on Windows, openat and mkdirat with O_NOFOLLOW plus
fchmod on the descriptor elsewhere. fchmod rather than chmod is the half that
matters off Windows, since chmod follows symlinks. The deterministic naming
contract is untouched.

Deliberately NOT peermsg.EnsurePrivateDir, which is the obvious patch and the
wrong one: it ends in a protected-DACL write that strips the sandbox
principal's grant elevated setup installed on the runtime tree, bringing back
the bare access denials from npm and go that the grant exists to prevent. That
would have passed every unit test on an unprovisioned box. This descent
validates and creates; it does not re-secure.

Two precisions worth recording. The Windows chmod is dropped rather than ported,
because it only toggles READONLY and was measured landing on the junction rather
than its target, so it bought nothing. And the exposure on the cache-derived
root predates this PR, byte-identical to main; what this PR added was making the
fallback root deterministic and persistent too, extending the same shape to it.
2026-09-11 10:17:31 +05:30
Vasanthdev2004 daf58c8962 fix(sandbox): keep a linked worktree's .git typed as a file through planning
gitMetadataWriteCarveoutSpecs types a linked worktree's or submodule's .git as
a pointer FILE. That typed result is flattened to a path before ACL planning,
and gitMetadataCarveoutIsFile tried to recover the shape by deriving suffixes
under a sentinel root whose .git never exists. The derivation therefore always
took the directory branch and produced exactly one file-shaped suffix,
.git\config, which a bare <root>\.git can never match. Both planners emitted
MaterializeFile:false for a path stage one had already typed correctly.

The window that turns a wrong plan into damage is the caller-to-elevated-helper
gap. The profile is built in the user's shell and the plan is applied in a
separately launched helper, across the UAC prompt, so a concurrent
`git worktree remove`, `git submodule deinit`, or hostile local process can
delete the pointer in between. The applier then creates a DIRECTORY at the
pointer path and the worktree is broken, persistently, because the runner
discards the rollback closure.

The carveout SET already carries the answer, so no type change is needed.
gitMetadataWriteCarveoutSpecs is the only producer of ReadOnlySubpaths, and it
emits a bare .git in exactly one case: the pointer. The directory case emits
.git\hooks and .git\config and never their parent. So the shape is read off
which carveout this is rather than guessed from a pathname.

The regression drives BuildWindowsACLPlan and applyWindowsACLPlan with the
pointer removed after planning, which is the only place the loss is visible; a
stage-one assertion on specs[0].IsFile passed for the whole time the bug was
live. A control with the pointer present keeps a green result from meaning an
apply that did nothing.
2026-09-11 10:17:31 +05:30
Vasanthdev2004 a8b295def3 test(sandbox): stop probing for privilege by mutating System32
The test applied the real ACL plan to C:\Windows\System32 and used the result
as its privilege probe: on success it skipped, having already mutated. Both
return values were discarded at the call site, so the snapshot holding the
original descriptor was gone and nothing could put it back. A process that does
hold WRITE_DAC there would leave an inheritable allow ACE for a synthetic SID
on System32 and on everything later created beneath it, permanently.

Reachability is narrower than reported, and worth writing down. System32 grants
WRITE_DAC only to TrustedInstaller; Administrators and SYSTEM get 0x1301bf on
the object, which does not include it, and their GA aces are inherit-only. So
an ordinary elevated run takes the denial branch. The branch that mutates needs
a token whose backup or restore privilege is enabled, since the applier opens
with FILE_FLAG_BACKUP_SEMANTICS, which is the normal shape of a LocalSystem
service token and therefore of a self-hosted runner installed as a service.
That could not be driven here, so it rests on documented behaviour rather than
on output. The trigger is narrow; the residue is unbounded and silent.

The coupling this test exists to pin, openWindowsACLTarget's wording against
windowsACLPlanDeniedPath's marker, is now pinned against a disposable directory
rigged to refuse WRITE_DAC. A plain deny ace is not enough there, because the
owner keeps an implicit WRITE_DAC that defeats it and the apply succeeds;
OWNER_RIGHTS is what makes the DACL the whole story. That was measured, not
assumed, and a naive deny-only fix would have relocated the same bug.

No run can now leave residue outside t.TempDir(), and the skip that used to
follow a completed mutation is a SETUP INVALID failure instead.
2026-09-11 10:17:31 +05:30
Vasanthdev2004 30d3c4791e fix(cli): keep a specified-empty sandbox environment from inheriting
exec.Cmd reads a nil Env as "inherit this process's entire environment", which
is a different statement from "run with no variables". The plan owns its
environment: directCommandEnv and scrubSensitiveEnv return a slice they built,
and that slice is non-nil with length zero when every entry was sensitive.
Testing its length collapsed those two states and turned the strictest possible
answer into the loosest one.

Reported by jatmn as a credential leak. Being precise about reachability: it is
not reachable through `zero sandbox exec` today. The child environment is
os.Environ(), so an environment holding only sensitive keys also has no
%AppData%, and config resolution fails at sandbox_exec.go before the planner
runs. Two independent checks reached that conclusion and I confirmed it at the
call site.

Fixed regardless. The guard is one assignment, and the next caller that hands
the plan a deliberately narrow environment would inherit everything instead,
silently. Both directions are pinned by a child that prints its own
environment, on every platform rather than behind a Unix-only skip.
2026-09-11 10:17:31 +05:30
Vasanthdev2004 26958ac6dd fix(sandbox): do not synthesize a .git inside an ancestor repository
A missing .git meant "this directory may become a repository", so the Windows
plan materialized .git/config and .git/hooks to get the deny ACE in place
before git first ran. That is right for a standalone directory. It is wrong
when the workspace is a subdirectory of an existing repository: the created
directory is a control directory competing with the ancestor's for git's
discovery walk, synthesized inside a repository Zero does not own.

The carveouts are now skipped when an ancestor carries git metadata, which is
git's own discovery rule. That is the same argument the linked-worktree branch
already makes: the metadata governing this workspace lives outside the write
root, the sandboxed principal has no inherited access to it, so it needs no
carveout here. The non-materialized deny-delete on <root>/.git is emitted
separately and still guards the name if a repository is ever created.

Ancestor detection accepts .git of either shape, since a linked worktree or
submodule ancestor carries it as a pointer file and still owns the directory.

Reported by jatmn. Worth recording that the stated consequence did not
reproduce here: a .git holding only config and hooks is not a valid repository,
so this git version walks past it and status, log and rev-parse still resolve
to the ancestor. The fix stands on the narrower ground that creating
repository metadata Zero does not own is wrong regardless, and anything later
adding a HEAD there would break discovery for real.
2026-09-11 10:17:31 +05:30
Vasanthdev2004 7920d3be3d fix(sandbox): key the read-grant refusal on the grant, not on the volume root
The refusal looked for a volume-root entry, which is a symptom of the
production profile rather than the thing that is unsafe.
permissionProfileReadRoots happens to seed the bare filesystem root, so that
check covered production by coincidence. A denyRead profile with a narrowed
read list carried no volume root, sailed through, and elevated setup would have
put an inheritable read ACE on C:\Windows: the same defect one level down.

The grant itself is what cannot be applied to a directory Zero does not own,
and it exists only for a denyRead profile, so that is what is refused now. Read
grants that land on the plan's own write roots are excluded, because those are
Zero's directories and were never the objection; the diagnostic names the
broadest path outside them, preferring a volume root so it reports the worst
one.

Found by probing the neighbouring case rather than by rerunning the one the
first fix was written against.
2026-09-11 10:17:31 +05:30
Vasanthdev2004 4320d08bae fix(sandbox): refuse a denyRead profile instead of ACLing the volume root
A profile that configures denyRead selects a fully restricted token, and that
token applies its restricted-SID check to reads, so the plan granted the read
capability at every read root. Production profiles seed ReadRoots with the bare
filesystem root.

The applier marks allow entries on a directory inheritable and calls
SetSecurityInfo, and Windows propagates inheritable ACEs onto existing
children. So applying that one entry was never a change to a sandbox-owned
object: it walks and rewrites DACL inheritance across unrelated system,
application and user trees on the drive, and a locked or exclusively opened
descendant leaves the result dependent on ambient filesystem state.

Paying that price does not even buy a working sandbox. A bare root resolves on
one volume, while the executables and libraries a command needs can sit on
another without being read roots of their own, so the strict token can still
fail before its executable starts. Measured separately: with the read
capability granted nowhere, the strict token cannot open cmd.exe.

So the profile is refused rather than half-served. The refusal moves out of the
unelevated tier, where it started for the narrower reason that an ordinary user
lacks the rights, and becomes the plan's own answer that both tiers consume.
Elevated setup refuses before its first mutation, which matters because that
tier CAN write the DACL. Profiles without denyRead are untouched and keep the
workspace write jail.

This leaves denyRead unavailable on Windows until there is a bounded
authorization model covering the real platform, runtime and executable
dependencies on every relevant volume, which is what #869 tracks. The
alternative on offer was a silently voided write jail or a volume-wide ACL
rewrite, and refusing is better than either.
2026-09-11 10:17:30 +05:30
Vasanthdev2004 bd7e98c05c fix(sandbox): make the capability git guard reach a workspace that gets git later
The capability planner emitted the deny-delete on .git and the deny-writes on
.git\config and .git\hooks without Materialize. On a workspace that had no
.git when setup ran, the first apply pass skipped all three as missing and the
deferred pass skipped them again, because nothing else in the capability plan
created them. Setup recorded success anyway.

A later git init then created .git, config and hooks beneath the already
granted workspace. They inherit the workspace allow, DELETE included, with no
object-specific deny of their own, so a sandboxed command could rename .git
aside, recreate it, and get credential.helper and core.hooksPath back. This is
the default backend, so the weaker of the two planners' rules was the one
almost every Windows user got.

The principal planner has materialized its carveouts from the start, which is
also what lets the applier's deferred pass land the deny-delete: creating
config and hooks creates .git as their parent. Sharing that shape rather than
only the guard's pathname is the fix.

The plan-shape test pinned materialize=false on these three entries, which
encoded exactly the behaviour that was wrong, so it is updated rather than
worked around. The new regression applies the real plan to a workspace with no
.git, runs a real git init, and reads the deny mask back off the object.
2026-09-11 10:17:30 +05:30
Vasanthdev2004 5a43074c30 fix(sandbox): recheck the runtime object on the unelevated tier too
The unelevated marker fingerprints pathnames and actions, and cleanup may
reclaim the deterministic runtime directory that plan was realized on. An
ordinary later run recreates the same pathname with the caller-private DACL and
no capability ACE, so the serialized plan is unchanged and the cached marker
returned before anything looked at the directory. The restricted child still
carried the capability SID; the new object did not grant it, and every temp,
package-cache and build-cache write failed after launch with a bare access
denial and nothing pointing at setup.

The restricted-token tier got this check in the previous commit. This tier
reaches the same lifecycle without elevation, and its answer differs: it owns
its plan, so it reapplies rather than refusing. Refusing would print advice to
run elevated setup, which is unnecessary here and unfollowable for a user with
no Administrator account.

The regression drives ensureWindowsUnelevatedSetup through provision, reclaim,
recreate, and asserts the grant is restored, with a setup guard proving the
recreated directory really lost it first. A companion pins that an intact root
still takes the cached fast path.
2026-09-11 10:17:30 +05:30
Vasanthdev2004 0904d88b26 fix(sandbox): check the runtime root still carries its grant, not just its pathname
cleanupSandboxRuntimeRoots reclaims inactive sibling workspace roots on an age
and count policy, treating them as disposable cache state. Setup and its marker
treat their DACL as durable provisioned state. When the reclaimed workspace runs
again, command-side preparation recreates the same deterministic pathname as the
ordinary caller, and the new directory inherits from its parent without the
capability SID ACE elevated setup applied to the object that used to be there.

ValidateWindowsSandboxSetupMarker still passed, because it fingerprints pathnames
and actions rather than the identity of the ACL-bearing object. So the restricted
child launched and then failed its cache, temp and package-cache writes with a
bare access-denied and nothing pointing at setup.

The command now asks the object, not the pathname: before the token is minted it
confirms the runtime root carries an allow ACE for its capability SID, and
refuses with the setup remedy when it does not. That reconciles the two owners
without making cleanup preserve trees it is meant to reclaim.

The regression applies a real plan, reclaims the directory the way cleanup does,
recreates the pathname the way an ordinary run does, and asserts the refusal
names the root and the remedy; accepting a missing grant fails it on that. Not
covered, and said plainly: a write performed by a real capability token, which
needs a provisioned sandbox an unelevated box cannot create. The ACE presence is
the fact the command consumes, and that is what is pinned.
2026-09-11 10:17:30 +05:30
Vasanthdev2004 2925a6768b fix(sandbox): validate runtime candidates before the elevated create, not after
ensureWindowsSandboxRuntimeCandidates ran as Administrator and used os.MkdirAll,
which follows links. Both candidate ancestries are prepared by the invoking user,
so a junction planted at a not-yet-created component below the cache directory,
or at the fallback anchor, made elevated setup build the runtime tree beneath a
redirected, Administrator-writable target. The ACL applier's no-follow check runs
afterwards and does spot the redirection, but the privileged create has already
happened by then and sits outside its rollback boundary. A leaf check after
MkdirAll would leave the same gap.

Candidates are now created by peermsg.EnsurePrivateDir, which descends
handle-relative with no-follow, refuses any component that is a link, and refuses
a leaf this user does not own. It is handed a physically resolved base first,
because it walks from the volume root and a redirected cache or TEMP above the
owned tail is the operator's business: the same pairing the fallback anchor
already uses, and the same mistake that refused every fallback on macOS when the
parent was left unresolved. physicalTempDir is generalised to physicalDir for
that, keeping GetFinalPathNameByHandle on Windows because EvalSymlinks does not
traverse a junction.

The regression plants a junction at the first owned component and asserts the
redirected target stays empty; letting the creator follow links again fails it on
that assertion.
2026-09-11 10:17:30 +05:30
Vasanthdev2004 faa07e3937 fix(sandbox,cli): plan the grant and its guard together, and state the tier boundary
The .git rename guard belonged to one planner rather than to the grant. The
allow-write mask both backends share includes DELETE, and it inherits from each
write root onto .git; the carveouts that actually protect git are attached to
.git/config and .git/hooks as objects, so renaming .git aside and recreating it
discards them and hands back credential.helper and core.hooksPath. The principal
planner denied DELETE there and the capability planner did not, and the
capability backend is the default. Both now derive that object from one place, so
a change to the shared mask cannot update one consumer and miss the other. The
regression reads the ACE back off the applied object rather than asserting plan
shape, because the plan is what was wrong.

The unelevated tier now states its boundary before it mutates anything. A profile
carrying denyRead runs on a strict token, which applies the restricted-SID check
to reads, so the read capability must be granted at the volume root that
permissionProfileReadRoots seeds. Elevated setup can write that DACL; an ordinary
user cannot, and the common opener asks for WRITE_DAC on every entry, so this
tier failed on that one root on every command. Dropping the root ACE instead is
not available, because the strict token would then fail its own read check for
the executable. So it is refused up front, naming the root, the denyRead cause
and elevated setup as the remedy. That last part matters: the previous
after-the-fact diagnostic told the reader that running setup elevated would NOT
fix it, which is the opposite of the truth for this case.

Separately, `sandbox exec` no longer reports a signaled child as exit 255. On
Unix ExitCode() answers -1 for signal termination and os.Exit truncates that, so
a child killed by SIGTERM was indistinguishable from one that chose to exit 255.
It now returns the conventional 128+signal, read from the ProcessState, with
Windows keeping the exit code it already reports.
2026-09-11 10:17:30 +05:30
Vasanthdev2004 834c184d4a fix(sandbox): resolve the temp dir physically before proving the fallback anchor
peermsg.EnsurePrivateDir walks every component from the root and refuses
any link. That is the right rule for the directory Zero owns and the wrong
rule for the operator's temp location above it: on macOS os.TempDir sits
under /var, a symlink to /private/var, so 8af05997 refused every fallback
on every Mac with "refusing non-directory or symlink runtime path component
var".

Anchor the fallback under the physical temp dir instead, so only the anchor
itself is a new component. EvalSymlinks off Windows; GetFinalPathNameByHandle
on Windows, where EvalSymlinks does not traverse a junction and a redirected
TEMP would trip the same way. The fixture compares against the resolved
temp dir rather than its spelling, since t.TempDir can come back as an 8.3
short name.
2026-09-11 10:17:30 +05:30
Vasanthdev2004 8da16b455f fix(sandbox): root the fallback runtime tree beneath a validated private anchor
The fallback runtime root moved from a fresh os.MkdirTemp parent to the
predictable <temp>/zero/runtime/v1/<hash> so that elevated setup and the later
command process agree on it. That agreement is required and stays. But a
predictable path directly under the shared system temp is not a private
allocation. On an ordinary shared /tmp another local user can create /tmp/zero
with mode 0700 first, and every affected user then fails before the sandbox
command starts; a pre-existing redirected component makes host-side
preparation lease, create, chmod and clean somewhere other than the derived
tree. Determinism was being used as if it were ownership.

The tree now lives beneath <temp>/zero-runtime-<user>, and that anchor is
created and validated by peermsg.EnsurePrivateDir before anything is built
under it: handle-relative descent, no-follow, refused if any component is a
link or the leaf is not owned by the current user, mode 0700. That primitive
already existed with exactly the semantics jatmn described, so it is exported
and reused rather than written a fourth time. On Unix the uid is in the name
because /tmp is shared; on Windows os.TempDir is already per-user and the
private descriptor plus owner check do the rest.

Validation runs on both paths that can hand back a fallback root:
sandboxRuntimeRootFor returns one itself when the cache lands inside the
workspace, and prepareSandboxRuntime asks for one when the cache root cannot be
leased. Both are covered, each with a junction planted at the anchor, and both
refuse with the junction target untouched; a control shows a clean fallback
still prepares beneath the anchor.

Two things went wrong on the way and are worth recording. The first draft
called pathWithinRoot with its arguments reversed, which asked whether the
anchor was beneath the root, answered false every time, and skipped the
validation entirely while every dependent test reported success through the
junction. And the first lease-failure trigger planted its file at the derived
leaf, so preparation failed on that mkdir before ever reaching the fallback
branch. Both fixed; with validation disabled the two refusal tests now die on
"reported success" while the control stays green.
2026-09-11 10:17:30 +05:30
Vasanthdev2004 c3e5e4bdfc test(sandbox): stop the launch preflight test asserting a machine's token
TestPrincipalLaunchPreflightExplainsAMissingPrivilege ran the real preflight and
then asserted SeAssignPrimaryTokenPrivilege appeared in the message. Which
privilege is missing is a property of the account running the test, not of the
code: an unelevated user often holds neither, but this box holds
SeAssignPrimaryTokenPrivilege and not SeIncreaseQuotaPrivilege, so only the
other name appeared and the test failed for a reason that was never a defect.

Its own comment said it asserted "the shape of the answer rather than a fixed
verdict, because the verdict legitimately differs by machine", and then it
hardcoded one of the two names. The comment was right and the assertion did not
match it.

principalLaunchPrivilegeError splits the rendering out from the token work, so
each combination is driven directly: neither held, only assign-primary-token,
only increase-quota, and nothing missing. Each asserts the message names what IS
missing and does NOT name the one that is held, since sending an operator after
a privilege they already have is its own failure. Making the message always name
both fails the two single-privilege cases.

The real preflight keeps a test, reduced to what does not vary: if it refuses,
the refusal names at least one of the two rather than something the operator
cannot act on. Stability across calls is unchanged.
2026-09-11 10:17:30 +05:30
Vasanthdev2004 89b2e6dfbc test(sandbox): keep the runtime-root candidates inside test-owned storage
runtimeRootTestConfig put the workspace and sandbox home under t.TempDir, but
windowsSandboxRuntimeCandidates still derived a candidate through the
production sandboxUserCacheDir seam, and the test creates every candidate and
registers os.RemoveAll cleanup for each.

So the test reached into the real user cache: it fails outright on a read-only
home, and on an ordinary developer or CI account it creates and then deletes a
path outside its own storage. The workspace hash makes a collision unlikely; it
does not make somebody else's directory test-owned.

Redirected before any candidate is derived, and restored with t.Cleanup.
Production derivation is unchanged, and the assertion that setup materializes
every granted write root still stands.

A before/after count of the real cache cannot observe this, since the test
creates and removes in the same run. The mechanism is the evidence:
prepareSandboxRuntime reads sandboxUserCacheDir, and the test RemoveAlls every
candidate that derivation produces.
2026-09-11 10:17:29 +05:30
Vasanthdev2004 cd7805062f fix(sandbox): keep principal provisioning closed until a launch path exists
The gate asked whether the CALLING process held SeAssignPrimaryTokenPrivilege
and SeIncreaseQuotaPrivilege. That is the wrong lifetime, and it got the answer
backwards where it mattered.

The process that needs those privileges is the later, ordinary command process.
Setup does not run it, and nothing carries launch authority across the UAC
boundary. So the caller-token check refused unelevated setup, which was never
the dangerous case, and PASSED elevated setup, which is precisely the case that
lands a local account, its password, its logon-right assignments, workspace
ACEs, the recovery ledger and network filter state for a backend no later
command can use. The check existed to prevent durable machine state serving
something that cannot run, and in the one configuration that creates that state
it allowed it.

Requiring every sandboxed command to run elevated would line the privileges up
and is deliberately not done: it is a worse boundary than the restricted token
it would replace, and it is not the lifecycle this is for. Until a reviewed
bootstrap or broker exists, provisioning is closed rather than half-working.

windowsPrincipalLaunchAvailable replaces the preflight var and takes no
argument, because the answer is about which mechanisms exist rather than about
the current process. It is the one place that learns to say yes when a broker
lands, and everything below it -- the plans, the ledger, the ACL and filter
work -- still builds and is still tested against it.

The runner keeps its own privilege check at launch time, which is the correct
lifetime for one; only the setup wiring is removed.

The regression test asserts the property the old shape could not express: the
refusal is stable regardless of what the calling process holds, and it does not
tell the operator to re-run from an elevated terminal, which is the advice that
produced the unusable state. Restoring the caller-passes behaviour fails both
new tests.

Refs #662, which this is foundation for and does not close.
2026-09-11 10:17:29 +05:30
Vasanthdev2004 6f0d45323b test(sandbox): assert nothing was created, not that a count held still
TestTeardownPathDerivationCreatesNothing compared the number of entries in the
SHARED temp directory before and after deriving the teardown paths. The
assertion it wants is that deriving a path creates nothing, and a count cannot
tell creation from removal: that root is also used by every other test binary
running at the same time and by the OS, so a concurrent cleanup made the count
fall and the failure read "temp directory gained -1 entries".

It compares the entry names now and reports anything that APPEARED, which is the
question actually being asked and is indifferent to whatever else disappears.
The failure also names the entry rather than a delta, so the next person sees
what was created instead of a number.
2026-09-11 10:17:29 +05:30
Vasanthdev2004 d6b4e73e0e fix(sandbox): refuse to provision a principal this caller could never launch
Measured on an ordinary unelevated session: the token holds neither
SeAssignPrimaryTokenPrivilege nor SeIncreaseQuotaPrivilege, so the principal
launch path can never engage for the process the runner is designed to be
called from. Elevated setup does not change that, because the command runs
later from the caller rather than from setup.

Until now setup succeeded completely in that situation. It created a local
account, its password, its logon-right assignments, the workspace ACEs, the
recovery ledger and the network filter state, and then every principal-mode
command refused before opening its executable. The operator was left with
durable machine state serving a backend that cannot run, and nothing said so at
the point they could still act on it.

The check runs in the caller's own process, which is the one whose privileges
decide the answer, and before anything crosses the UAC boundary. It is wired to
the same function the launch path uses, so a change to what a launch requires
cannot leave setup provisioning for a capability that no longer exists.

Three existing tests asserted argument plumbing with the opt-in on and passed
only because nothing checked; they stub the preflight now, so they no longer
depend on the privileges of whoever runs the suite.

This does not give the principal backend a working launch path. That needs a
different architecture and is not in this change.
2026-09-11 10:17:29 +05:30
Vasanthdev2004 3574f62c2f fix(sandbox): name the two role inventories, and fingerprint the whole plan
Three follow-ups from going back over the review findings. None was raised
directly; two are the same shape as things that were.

windowsPrincipalPlanFingerprint was the one of three buildWindowsPrincipalACLPlan
call sites that did not pass DenyWrite. Apply and teardown both did, so the hash
the marker carries described a different plan than the one that actually gets
applied, and a change to the policy's deny-write paths moved the applied plan
while leaving the marker where it was. It is not a live hole, because the
capability ACLPlanHash covers the same paths and moves the marker anyway. That
is also exactly what would have kept it invisible until somebody changed the
capability plan's shape.

The role list was spelled out in three places and two of them are meant to
differ, which is why writing them out by hand kept going wrong.
windowsSandboxPrincipalIsInstalled asked only the offline and online roles while
teardown retires the legacy account too, so a machine still holding the untagged
pre-split account was reported clean and the opted-out marker claimed a teardown
that had not happened. Provisioning has the opposite constraint: legacy must
never appear there or setup would recreate that account on every run of an
already-upgraded machine. Both are named now, windowsSandboxLiveRoles and
windowsSandboxRetirableRoles, with a test pinning the legacy role into exactly
one of them.

And the opt-out error said "retire the principal" when a workspace has two plus
the legacy one, all of which that re-run retires.
2026-09-11 10:17:29 +05:30
Vasanthdev2004 fffc780dc3 fix(sandbox): bind the ACL restore to the object it snapshotted
jatmn's P1 asked for creation AND cleanup to be handle-bound rather than
resolved from a pathname. Creation and the materialization unwind both are.
The DACL restore was not, and its comment read as though it were.

It re-opened the target with a no-follow open, which rules out a reparse point
swapped in since apply and nothing else. The other substitution passes it
untouched: rename the target aside and put an ordinary directory of the same
name in its place. Nothing there is a link, so the open succeeds, the pre-apply
DACL lands on the decoy, and the real object keeps the ACEs from the setup that
just aborted. The snapshot now records the volume serial and file index of the
object it read the DACL from, the restore proves it is writing back to that same
object, and a mismatch is refused rather than forced through. Leaving the real
object with the aborted setup's ACEs is the safe direction, since the caller is
failing anyway.

Three things nothing was pinning, all of which could be deleted with a green
suite. This repository has already had a fix silently reverted by a later
change, so these are worth more than their size.

rollbackWindowsACLSnapshots documented its reverse iteration as pinned by
TestRollbackUnwindsDescendantsBeforeAncestors. That test did not exist anywhere
in the repo; the only match for the name was the sentence claiming it. The
ordering is load-bearing twice over, because a materialized directory must be
empty before its own removal and SetSecurityInfo propagates inheritable ACEs
downward, so the ancestor has to go last. It exists now.

The principal ACL rollback restores the ledger alongside the DACLs, and the
neighbouring test asserted only the order of the two ACL reverts and never read
the ledger. Deleting the restore left the suite green while the paths it put
back were unnamed, so cleanup could not find them.

windowsSandboxUserIsManaged promises an account carrying the legacy bare comment
gets the workspace key stamped on. The probe for the legacy comment was seamed
and the upgrade itself was not, so nothing could observe the call. It is seamed
now, with the negative case covered too so the assertion cannot be satisfied by
an unconditional rewrite.
2026-09-11 10:17:29 +05:30
Vasanth T 272acb9324 feat(sandbox): give each workspace an offline and an online principal (#812)
* feat(sandbox): give each workspace an offline and an online principal

The principal backend stood down whenever the network was denied, which is the
default, so opting into it left the restricted-token path doing all the work in
normal use. The reason was that network denial is enforced by block filters
keyed to the offline-marker SID, and a principal token cannot carry it:
LogonUser builds a token from an account's real group memberships, and the
marker is a synthetic capability SID.

A real local group closes that gap. ZeroSandboxOffline is created by setup, the
block filters name its SID alongside the marker, and a principal is denied the
network by being a member. Each workspace therefore gets two accounts that
differ only in that membership, and the command's network mode selects between
them. A group rather than each principal's own SID because principals are per
workspace: one filter set covers every offline principal on the machine instead
of needing a filter per workspace.

Both principals are provisioned together even though a given setup run sees one
profile, because setup needs elevation and commands do not. Provisioning lazily
would mean an unelevated command discovering it needs an account it cannot
create. They also get identical filesystem access, so an approved network
command sees the same filesystem as an ordinary one.

Two orderings are load bearing. The network plan is now built AFTER
provisioning, because the group it keys to is created there; planning first
installed filters naming only the marker and left every offline principal with
an open network while looking correctly set up. And the role tag sits before
the workspace hash in the account name, so truncation at the 20 character limit
eats hash characters rather than the tag, which would otherwise collide the two
roles onto one account on exactly the workspaces most likely to truncate.

Anything that is not an explicit allow maps to the offline principal, so an
unrecognised mode loses the network rather than keeping it.

The filter identity set is resolved rather than assumed, and stays absent until
the group exists, so a machine that never provisions principals computes the
same plan as before. That matters because the plan is hashed into the setup
marker and re-derived on every command; an identity set that differed between
setup and the command path would fail every command as out of date.

Cost worth stating: this doubles the sandbox accounts on a machine, to two per
workspace.

* fix(sandbox): prove ownership before deleting a sandbox account

removeWindowsSandboxIdentity is called with a DERIVED name, so it could be
pointed at a name that happens to belong to somebody else's local account.
Deleting a user is not a recoverable mistake, and the only thing standing
between the two cases was the name matching a pattern we generate ourselves.
Raised by CodeRabbit against the test fixtures, but the production teardown path
had the same hazard, so the guard belongs there rather than in the tests.

The ownership check itself now lives on the base branch, which grew the same
helper to stop provisioning ADOPTING a squatted account. This applies it to the
other end: an account that is not ours is left alone rather than deleted. The
gated tests get the protection for free, since their pre-clean goes through the
same helper.

Also appends the trimmed offline-group SID rather than the raw one. Worth noting
the reported consequence does not hold: newWindowsWFPUserCondition canonicalises
before converting, so a padded value would have been trimmed before reaching
StringToSid. The resolver returns SID.String(), which never carries whitespace,
so this is defensive tidying rather than a fix.

* fix(sandbox): assert the filters cover principals, and report a retained account

Two follow-ups from review, both on the same theme: a control that quietly does
nothing looks identical to one that works.

The network plan must be built AFTER provisioning, because provisioning creates
the group the block filters name. Built first, the filters name only the
offline marker and every offline principal has an open network while setup
reports success. That ordering is invisible at the call site, so setup now
checks the plan actually names the offline group before installing anything and
refuses if it does not. A later refactor that moves the plan build back fails
loudly instead of producing a security control that enforces nothing.

The predicate is separate so it can be asserted directly: a plan carrying only
the marker must read as uncovered, one carrying the group as covered, case
differences must not read as missing, and a host with no group provisioned has
no principal to miss and must not be refused. Making coverage always report
true fails that test.

Removal also reported plain success when it declined to delete an account Zero
did not create. Leaving it alone is right, but telling an operator cleanup
completed when a name they may care about was deliberately retained is not.
That case is now a distinguishable sentinel, and teardown treats it as success,
since "no principal of ours under this name" is the goal state either way.

* fix(sandbox): spare adopted principals when dual-role setup rolls back

Provisioning already declined to delete an account it had adopted, and the
outer setup rollback then appended an unconditional removal for every role
that got that far. With two roles that is the common case rather than an
unlucky one: the offline role usually succeeds, so a failure in the online
role or in ACL application destroyed a principal that was working before
the run started. The removal closure is now only appended for a principal
this run created.

Threads the workspace key into the delete path as well. Ownership was
proven from the account comment alone, which on a name collision belongs
to a DIFFERENT workspace, so deleting it would have been the same
unrecoverable mistake the check exists to prevent.

Policy DenyWrite now reaches the principal ACL plan here too, matching the
single-principal path.

Fixes the mode-independence test, which required exactly one identity SID
and so failed on any Windows host that already had ZeroSandboxOffline,
where the plan legitimately carries two. CI never saw it because the Linux
and macOS jobs leave the hook nil and a fresh Windows runner has no group.
The hook is now pinned, and the test additionally asserts the property it
is named for in the group-present case, including that the infra hash
changes when the group appears, which is the cross-workspace coupling
raised for a maintainer decision.

* test(sandbox): stub the password reset and pin the resolved group SIDs

Two review points on the tests added in the previous commit.

The provisioning stub left resetWindowsSandboxUserPassword as a real
call. Nothing under test reaches it any more, because rotation moved to
the caller, but a test that resets a real managed account's password if
the code ever moves back is not a risk worth carrying. It is now stubbed
to fail the test instead, which also states the contract.

The group-present assertion checked only that two identity SIDs were
present. A duplicated offline marker or an unrelated SID would satisfy
that while meaning something quite different, so it now pins both
positions.

Also drops a duplicated stub assignment left by the rebase.

* fix(sandbox): refuse an offline group zero does not own

ensureWindowsLocalGroup accepted NERR_GroupExists and ERROR_ALIAS_EXISTS as
success without inspecting the group it was about to reuse. Setup then resolved
that group's SID and installed it on the persistent WFP deny filters, and made
the sandbox principal a member of it.

If anything else on the machine already owns a group named ZeroSandboxOffline —
another tool, a policy, a prior unrelated convention — that is not a no-op. Every
existing member abruptly loses outbound access, because the filters now name
their group. In the other direction the sandbox principal inherits whatever
permissions that group carries, which is the opposite of what an offline
principal is for.

The add now reports its raw status and the already-exists branch verifies the
group carries this setup's managed marker before adopting it, failing with an
actionable message otherwise. A lookup error fails closed rather than adopting.

NetLocalGroupAdd and the ownership lookup sit behind seams so the branch is
reachable in tests without an elevated machine; the marker compared is the
group's own, so the principals group and the offline group cannot be confused.

Reported by jatmn on #812.

* fix(sandbox): recheck offline group membership before minting a token

Network denial does not follow from picking the offline account. The WFP block
filters match the offline GROUP'S SID, and LogonUser builds a token from the
account's real memberships — so membership is the whole enforcement, and the
command path never revalidated it.

An account that drifts out of ZeroSandboxOffline through local policy, an
administrator, or a re-setup that could not re-add it still resolves, still has
its stored secret, and still logs on. Its token no longer satisfies the filter
condition, so a NetworkDeny command gets full egress under a profile that asked
for none. The stale setup marker keeps the whole path looking healthy.

The offline role now confirms the membership its mode depends on before the
secret is read, and falls back to the restricted token when it is absent. That
direction is deliberate: the restricted token carries the offline marker the
same filters match, so egress stays blocked, and only read confinement is lost.
A failed lookup surfaces rather than downgrading silently. The online role is
not checked, since it is not in that group by design.

Reported by jatmn on #812.

* fix(sandbox): derive setup's runtime root deterministically or not at all

windowsSandboxRuntimeRootPath resolved through sandboxRuntimeRootFor, which
falls back to os.MkdirTemp when the user cache lives inside the workspace and
memoizes that only in-process.

Elevated setup is its own process. It granted the principals an ACE on temp root
A; the next command, being a new process, derived temp root B, where the
principal has no ACE, and failed ordinary cache writes with a bare ACCESS_DENIED
and nothing pointing at the sandbox. Teardown, a third process, cleaned a third
directory. The three callers that have to agree exactly could not agree at all.

Setup now uses the same side-effect-free derivation teardown already used, and
reports no runtime root when that derivation is unusable rather than inventing
one. A root only the granting process can name is worse than no root: the
principal loses the runtime tree, which is a degraded sandbox, instead of the
sandbox appearing provisioned while every command fails.

TestTeardownPathDerivationCreatesNothing asserted the opposite — that setup
"should still fall back to a usable tree" — so it is inverted here, with the
reasoning recorded in the test. That assertion encoded the assumption this
finding overturns: a per-process temp tree is not usable. Restoring the fallback
fails it with the invented path in the message, and a new
TestSetupAndTeardownDeriveTheSameRuntimeRoot pins the ordinary case, so
"report none" cannot quietly become the answer everywhere.

Reported by jatmn on #812.

* style(sandbox): separate the two doc paragraphs the rebase ran together

Adapting the ACL-record test to dual roles left #808's fail-open rationale
and #812's per-role rationale as one unbroken block. Both are worth
keeping; they are two points, not one.

* fix(sandbox): fail closed when offline-group coverage cannot be verified

The post-provisioning assertion ran inside `if groupErr == nil`, so a
failed lookup skipped it and setup carried on to install filters and
write a success marker. The comment directly above it says what that
costs: a machine reporting a successful setup while every offline
principal has an open network.

An empty SID was the same hole by a different route. Resolving to
("", nil) means the group does not exist, which is the ordinary state
before provisioning and an impossible one after it, and
WindowsNetworkPlanCoversPrincipals answers true for an empty SID
(correctly, for the pre-provisioning callers that ask it). So the
assertion passed vacuously in exactly the case where the group setup
had just created was missing.

Move the check into assertWindowsNetworkPlanCoversOfflineGroup, which
takes the resolver as a parameter and fails closed on every answer that
is not a definite yes: lookup error (wrapped, so the Win32 reason still
reaches the operator), empty SID, plan omitting the group, and a nil
resolver. Setup rolls back and exits 1 on each.

Taking the resolver as a parameter is what makes the error paths
testable, which is the regression the review asked for.

Reported by @anandh8x on #812.

* fix(sandbox): scope the offline-group assert to provisioned runs

c404ebd2 made the coverage assert reject an empty group SID, closing the
vacuous pass where a missing group counted as covered. It ran the assert
unconditionally, and the offline group is only created inside
provisionWindowsSandboxIdentity, which runs only under the
ZERO_WINDOWS_SANDBOX_IDENTITY opt-in.

So on a default machine with principals opted out, the resolver reports
("", nil) exactly as it should, and setup died with "the sandbox offline
group does not exist after provisioning" on a path that worked before
c404ebd2. The empty-SID rejection is correct after provisioning and wrong
before it.

Pass provisioned to the assert and return early when it is false, gated
at the call site on the same windowsSandboxIdentityEnabled check that
decides whether principals are provisioned at all. The fail-closed
behaviour anandh8x asked for is unchanged whenever provisioning ran.

Reported by @jatmn on #812.

* fix(sandbox): keep opted-out setup markers valid, and refuse a foreign offline group

Two of jatmn's findings on this PR.

Existing markers stay compatible (maintainer decision). The offline group is
machine-global, and the plan included its SID whenever the group existed. So the
first workspace to opt in changed the computed NetworkInfraHash for every OTHER
sandbox home on the machine, and those homes rejected their own stored markers
until each was re-run from an elevated terminal, having opted into nothing.

The inclusion is now gated on THIS home's opt-in rather than on the group
existing, so an opted-out home computes exactly the plan it computed before any
of this existed. Setup and the command path read the flag from the same
environment, so they agree. Opting in after setup does invalidate that home's
marker, which is correct: it has no principals yet.

Do not install filters for an unowned offline group (P1). The ownership check
only ran through principal provisioning, so an opt-out setup reached the resolver
and adopted any local alias carrying the name. applyWindowsNetworkPlan turns
every SID in the plan into an allowed-to-match WFP descriptor, so a foreign group
meant global deny filters against every one of ITS members: anyone with a local
group by that name loses the network for those accounts because we ran setup.
The resolver now requires the managed comment, and refuses rather than skipping,
because a plan whose filters cover no principal while setup reports success is
the failure this backend exists to prevent.

Three existing tests exercised the group path without the opt-in and now set it.
The new test asserts the other direction, that an opted-out home's hash is
unchanged when another workspace creates the group, since that is the property
the decision turns on. Verified both ways: disabling the gate fails the existing
tests, making it unconditional fails the new one.

* fix(doctor): report the principal that dual-role setup actually uses

jatmn's P2. This branch made the offline principal work under NetworkDeny, but
the doctor helper still described the old restricted-token standdown, so
`zero doctor` reported active:false and told operators reads were unconfined for
a correctly provisioned offline principal, recommending they enable network or
drop the opt-in to fix something that was not broken.

WindowsSandboxPrincipalInactiveReason is removed rather than reworded. Its only
condition was the deny-mode standdown, so after this branch it could never return
anything, and a check that cannot fire is worse than no check.

What replaced it matters more than what it said. That helper existed to be the
SINGLE rule doctor and the runtime both read, precisely so they could not drift,
and drift is what happened anyway when dual-role changed the behaviour under one
of them. WindowsSandboxPrincipalRoleForNetwork is now that shared rule:
windowsSandboxRoleForNetwork delegates to it and doctor calls it, so the reported
account and the used account cannot disagree. Doctor now names which principal a
command runs as instead of asserting a standdown.

One thing the existing tests caught. Routing the shared rule through
NormalizeNetworkMode case-folds, so "ALLOW" selected the ONLINE principal where
the runtime required an exact match and failed closed to offline. Sharing a rule
is only an improvement if it shares the stricter one, so the comparison is exact
and a test pins the casing.

* fix(sandbox): converge the dual-role branch with the rebased identity work

Rebasing #812 onto the new #808 needed real resolution rather than taking a
side, and this records what each conflict actually decided.

The account key. #808 made the principal key caller-scoped so elevated setup
provisions the account the caller will later look for. #812 derived usernames
from the workspace key alone. Every username derivation now uses the caller
scoped key, including the two inline call sites a blanket substitution missed:
the identity lookup in the unrecorded-retire path and the ledger read in
windowsPrincipalRevocationPaths. That second one is why teardown could not find
a recorded root the current policy no longer named. The setup LOCK stays keyed
to the workspace on purpose, because two users setting up one shared workspace
still write DACLs on the same paths and must serialize against each other.

The network plan stays where #812 put it, after provisioning, because the block
filters are keyed to the offline group that provisioning creates. Building it
earlier, as #808 does, would install filters naming only the marker and leave
every offline principal with an open network while looking correctly set up.

Group ownership converged on #812's implementation, not mine. #808 grew a check
hardcoded to the users group; #812 already had the general
ensureWindowsLocalGroup plus windowsLocalGroupOwnedByZero, which covers both
managed groups. The narrower version was removed and its test rewritten against
the general seams, so the users group keeps the coverage anandh8x asked for
while the offline group keeps its own.

Two functions the resolution dropped and the compiler caught:
windowsSandboxPrincipalKey and windowsCurrentUserSID. Worth naming because the
previous attempt at this convergence lost the same first function silently.

Also closes jatmn's remaining findings on this branch. The opt-out installed
check now asks about BOTH role accounts rather than one, since retiring one
while the other survives is exactly the half-done teardown an opted-out marker
must not report as success. And the post-provisioning filter-coverage assert now
resolves the offline group through the existing hook rather than the concrete
function, so it is stubbable like everything else around it.

The SensitiveEnvKeys omission jatmn reported on sandbox_exec.go arrives with the
rebase; it was fixed on #808.

* fix(sandbox): keep offline coverage and grant the fallback runtime root

Two ways the dual-role split left a workspace worse off than it looked.

The block filters are machine-global and every setup installs them by
deleting and recreating one fixed set, but the plan a home builds names
the offline group only when THAT home opted in. So an ordinary opted-out
setup for a second workspace replaced the filters without the group SID,
and the first workspace's offline principal, still in the group, still
passing the runtime membership check and still holding a valid marker,
was no longer matched by any filter. A NetworkDeny command there gained
egress silently, because the second setup did exactly what it was asked.

The gate itself is left alone, because it is load bearing for a different
reason: the plan is hashed into each home's marker, and keying it on the
group's existence made the first workspace to opt in invalidate every
other home's marker on the machine. What a home RECORDS is about its own
configuration; what setup INSTALLS is about the machine. Answering both
from one plan is what forced a choice between stale markers and a silent
hole, so WindowsNetworkPlanForApply answers the second question only, at
the apply call site, leaving the fingerprinted plan untouched.

Setup also granted the principals an ACE on the cache-derived runtime
root alone, and none at all when the cache sat inside the workspace. That
was correct when the other branch minted a random per-process directory
through MkdirTemp, but fallbackSandboxRuntimeRoot now derives its path by
hashing the workspace and creates nothing, so every process agrees on it.
Commands in that layout therefore DO select it and redirect TMP, GOCACHE
and the package caches into it, against a tree neither principal could
write. Setup now grants the same candidate set the capability plan
already covers, and creates each one, since applyWindowsACLPlan fails on
a target that does not exist.

Reverting either fix fails its regression: the opted-out plan installs
filters naming only the marker SID, and setup grants nothing while
commands write to Temp\zero\runtime\v1\<hash>.

Two existing assertions had to be inverted rather than adapted, and both
were asserting the old bug. One required setup to report NO runtime root
in the cache-inside-workspace layout; the other compared setup's single
root for equality against the command's choice. Setup covers the whole
candidate set now precisely because that choice is made per process, so
the contract is membership.

* fix(sandbox): treat an unreadable offline group as a failure, and retire the pre-split principal

Three findings from review.

A resolution failure in WindowsNetworkPlanForApply returned a marker-only plan,
and the machine's WFP filters are replaced wholesale from that plan. So an
opted-out setup whose group lookup failed transiently removed the offline group
SID another workspace's principals depend on, and that workspace's NetworkDeny
commands silently regained egress while its marker and its direct membership
check both still passed. The old reasoning was that refusing to install would
trade a partial denial for no denial; that is wrong, because the alternative to
installing is leaving the existing filters alone. It is fatal now, which is only
reachable from an opted-out home since assertWindowsNetworkPlanCoversOfflineGroup
is gated on provisioned.

Splitting the single principal into offline and online roles changed both
account names without changing the marker schema, so an installation made by the
previous version kept a valid marker, setup was never re-run, and the runner
found neither zero-sbx-d<key> nor zero-sbx-n<key> and fell back to the
restricted-token backend with no read confinement. The schema version is bumped
so that installation reports as out of date, and a legacy role derives the old
untagged name so the ordered retirement can remove the account, its secret, its
logon rights, its ACEs and its ledger. It is retired, never provisioned, and
there is a test for that because the two lists are one line apart.

Doctor reported that commands run as the selected principal whenever the marker
validated, but marker validation compares serialized plans and hashes and names
no account: deleting the account or its secret, or dropping the offline account
out of its group, leaves the marker valid while the runtime falls back or fails.
Verifying liveness needs Windows-only queries internal/doctor cannot make, so
the claim is narrowed to what the marker actually proves. The role is still
reported, since that part is derived rather than assumed.
2026-09-11 10:17:28 +05:30
Vasanthdev2004 d736aae19a test(sandbox): compare normalized paths, not the raw input
TestACLComparablePathDoesNotResolveAReparsePoint failed on Windows CI
while passing locally. The test was wrong, not the code.

It asserted that windowsACLComparablePath returns a string equal to the
path passed in. GetLongPathName legitimately rewrites that string: a CI
runner's temp directory is an 8.3 short name, so expanding RUNNER~1 to
runneradmin produces a different string naming exactly the same object,
and the assertion failed on the one property the function is supposed to
have.

Both sides are now normalized before comparison, which states the real
property: a path THROUGH the reparse point must not normalize to the
target's normalization, or the guard would compare a redirected handle
against a redirected expectation and match itself. A second assertion
keeps the link component present so a resolution to something else
entirely still fails.

The test's documented limit is unchanged and still honest: a junction
cannot separate the old basis from the new one, because EvalSymlinks does
not resolve junctions either. It remains an invariant test.
2026-09-11 10:17:28 +05:30
Vasanthdev2004 129800b995 fix(sandbox): stop the redirect check resolving what it checks for
verifyWindowsACLTargetNotRedirected asks GetFinalPathNameByHandle where
the handle landed, then compared that against
canonicalSandboxWorkspaceRoot(path), which runs filepath.EvalSymlinks.
That is the same resolution the kernel had just performed, so for a
directory symlink the two sides agreed precisely BECAUSE the redirect
happened: elevated setup went on to rewrite the DACL of an object outside
the workspace while the check reported success.

Junctions were rejected, but by accident rather than by design. Go reports
a junction as ModeIrregular rather than ModeSymlink, so EvalSymlinks
refuses it, the canonicalization falls back to the lexical path, and the
mismatch surfaces. That is a property of the standard library's mode bits,
not of this guard, and a Go release that resolved mount points would
silently disarm the one case it was known to catch.

The expected side is now normalized without resolving anything.
GetLongPathName expands an 8.3 short name by reading directory entries and
does not follow a link to its target, and EqualFold still covers casing,
so the two spellings that legitimately name the same object still compare
equal. Every failure degrades to the lexically cleaned path, which can
only produce a spurious refusal, never a spurious match.

A target deliberately spelled through a symlink is now refused. That is
the intended direction: the question here is whether the object the handle
landed on is the object that was named.

On the tests, plainly: the directory-symlink regression is the one that
separates the old basis from the new, and it needs Developer Mode or
SeCreateSymbolicLinkPrivilege, so it skips on a machine without either and
skipped on mine. The junction test beside it passes against both bases and
says so in its own comment; it is an invariant test guarding the Go
behaviour the old code accidentally depended on, not a regression for this
change.
2026-09-11 10:17:28 +05:30
Vasanthdev2004 474f6e9b08 fix(sandbox): drop the unfollowable sandbox override from ACL failures
Both unelevated ACL failures told the reader to re-run with `--sandbox
forbid`. There is no such option: SandboxPreferenceForbid is an internal
engine state with no flag behind it, so acting on it produced an unknown
option and left them stuck on the failure they had just been told how to
clear. Advice that does not work costs more than none, because finding
that out takes the reader's time.

Name the real way out instead, the user config key, which is honored
from global config only so a cloned repo cannot set it. The
elevated-setup remedy beside it was already correct and stays.

Reported by jatmn against the same string on #640. It predates this
branch, having arrived with the unelevated fallback tier in #427, and
the copy on #886 is fixed separately in 1b304e13.

Also covers the secret write with the junction regression it was owed:
the caller owns the sandbox home, so they can put a reparse point where
the secret directory is expected, and the pathname version followed it
in an elevated process. The test asserts the refusal names the reparse
point and that nothing survives on the far side, since refusing while
still creating the file would leave the caller holding it.
2026-09-11 10:17:28 +05:30
Vasanthdev2004 2a765446cb fix(sandbox): stop the principal's environment naming the caller
The child environment starts as the invoking user's, and the deliberate
sandbox redirects only replace HOME, the temp variables and the per-tool
cache dirs. Everything identifying the account survived, so a command
running as the principal read USERPROFILE, APPDATA, LOCALAPPDATA,
HOMEDRIVE, HOMEPATH, USERNAME and USERDOMAIN describing the CALLER,
whose profile the principal deliberately cannot open. Native tools
resolve per-user state through exactly those, so they fail during
startup or quietly look somewhere they have no business reading.

Point them into the sandbox runtime tree, which is already granted to
the principal and already holds its caches, so the paths are writable by
construction. Naming the real Windows profile would need LoadUserProfile
to have run, and a variable pointing at a directory that does not exist
yet is a worse answer than one pointing somewhere usable.

Layered under the deliberate redirects rather than over them:
sandboxRuntimeEnvironment stays the single owner of HOME, TMPDIR, TMP
and TEMP, and a regression pins that so the two cannot drift into
setting the same variables from two places.

This is the environment half of the finding. Loading the principal's
profile and known folders is left until the launch mechanism is settled,
since LOGON_WITH_PROFILE would do it as a side effect.
2026-09-11 10:17:28 +05:30
Vasanthdev2004 81c8326072 fix(sandbox): report the privileges a principal launch actually needs
CreateProcessAsUser exempts only a restricted version of the caller's
own primary token from SE_ASSIGNPRIMARYTOKEN_NAME, which is precisely
why the ordinary restricted-token path works while holding nothing
special. A principal token comes from LogonUser against a separate local
account, so the exemption does not apply and both that privilege and
SE_INCREASE_QUOTA_NAME are required. Nothing enabled or checked either,
and a token measured on an ordinary unelevated process holds neither, so
the failure arrived as a bare "Access is denied" from inside process
creation, before the command's executable was ever opened, and read as
the command being rejected.

Enable them where they are held, since present-but-disabled still fails
the access check and that is where an elevated administrator lands, and
refuse with the specific names and a way out where they are not.

Detected by ENUMERATING the token. AdjustTokenPrivileges reports an
unheld privilege by returning success with ERROR_NOT_ALL_ASSIGNED, which
this binding does not surface: it returns nil for SeTcbPrivilege on an
ordinary process. A check built on its error passed everywhere, which is
worse than no check, since it would call the sandbox ready in exactly
the case it cannot run.

This does not make the principal launchable. It makes the reason legible
while the launch mechanism itself is settled.
2026-09-11 10:17:28 +05:30
Vasanthdev2004 b9ba54a948 fix(sandbox): write the principal secret through one pinned handle
The elevated secret write resolved its path four separate times:
MkdirAll, an O_TRUNC open, SetNamedSecurityInfo by name, then WriteFile
by name. The sandbox home belongs to the invoking user, who is the party
this sandbox contains, so each resolution was a place to swap a
component. A symlink leaf lets an Administrator truncate a file of the
caller's choosing and then rewrite its DACL; a junction alone is enough
to plant the deterministic secret somewhere the caller controls.

Create the leaf relative to a pinned no-follow parent handle, refuse it
if it is a reparse point, and apply both the DACL and the bytes to that
handle. The name is never resolved again after the create.

The payload is now sealed before the file exists, so a failure there
leaves nothing on disk rather than an empty file for someone to race.
Cleanup on failure stays by name, which is safe in the direction that
matters: at worst it misses and leaves a locked-down file, never deletes
something it did not create.
2026-09-11 10:17:28 +05:30
Vasanthdev2004 b97e744989 fix(sandbox): protect the gitdir pointer in a linked worktree
A linked worktree or submodule has .git as a FILE holding a `gitdir:`
pointer, not a directory. The principal plan names .git/config and
.git/hooks and materializes both, and the Windows materializer gets
there by descending through .git as a directory. A regular file cannot
have children, so opted-in elevated setup aborted and the sandbox could
not be used in a worktree at all. Zero's own development worktrees are
this shape, which is how it went unnoticed.

Deny the pointer file itself there instead. That is the stronger
protection rather than a fallback: a principal able to rewrite `gitdir:`
repoints the repository at a control directory of its choosing, which
subsumes editing config or planting a hook. The real control directory
sits outside the write root, so nothing is inherited there and no
carveout is needed.

Decided by an Lstat rather than a lexical guess, since the layout is a
property of the checkout. An absent .git keeps the directory-shaped
carveouts so they are still created before git first runs.
2026-09-11 10:17:28 +05:30
Vasanthdev2004 55023a9805 test(sandbox): fix the workspace-root literal in the setup-args tests
A bulk edit dropped the separator, leaving the drive-relative
`C:workspace` where `C:\workspace` was meant. Windows resolves the
first well enough that the two halves still agreed; on Linux a backslash
is an ordinary character, so the command half derived no runtime
candidates at all and the marker carried two the command never saw.

The setup half no longer pre-augments either: BuildWindowsSandboxSetupArgs
folds the runtime roots in itself, and passing them in hid that from the
one test that covers it.
2026-09-11 10:17:28 +05:30
Vasanthdev2004 9800065f65 fix(sandbox): give the principal's read roots a restricting SID
A profile with DenyRead drops WRITE_RESTRICTED, so Windows runs the
restricted-SID check over reads as well as writes. Read roots were
granted only to the principal's account SID, and the write jail removes
that SID from the restricting set on purpose, so reads passed the normal
check and matched nothing on the restricted one. The result was not a
narrower sandbox but an unusable one: no read root readable, including
the executable the command was trying to start.

Mint a read capability SID, grant it on every read root in the
capability plan, and carry it in the strict token's restricting set, so
the read allow-list and the restriction come from one value instead of
two that can drift.

Deny it on every DenyRead path too. The read roots begin at the
filesystem root, so without that the carveouts stay readable through the
new grant and the deny list stops meaning anything, which is the whole
reason the strict token is chosen. The no-write-roots case keeps its
ReadOnly deny as well: both SIDs the token can carry must be denied, not
only the newest.

Gated on DenyRead, which is what selects the strict token. Elsewhere
reads never reach the restricted check and the grant would be ACEs on
the filesystem root that buy nothing. Both halves decide from the
profile alone, so they cannot disagree about whether the entries exist.
2026-09-11 10:17:28 +05:30
Vasanthdev2004 18ffd02b93 fix(sandbox): derive the runtime roots where TEMP is the operator's
Every sandboxed command failed marker validation with two plans of the
same size and different hashes:

  marker ...\windows-setup.json has 12 entries, hash 76fda2032e66;
  this command expects 12 entries, hash 4be1dbf8b642

The temp-derived runtime candidate reads os.TempDir(), and the sandbox
points TMPDIR, TMP and TEMP at its own runtime temp for everything it
launches. The command runner inherits that env, so when it derived the
candidate set it produced a root under the runtime tree while setup,
whose TEMP is untouched, produced one under the real temp. Same count,
different path, and no command could run.

A fingerprint both halves compare cannot be a function of the caller's
environment. Derive it only where TEMP is still the operator's: the
setup args builder, the Windows command plan, and doctor. The runner now
takes the profile it is handed, and commandConfig no longer re-derives
on behalf of whoever happens to call it.

The regression settles the profile first and redirects TEMP afterwards,
in that order, so it reproduces the mismatch against the old behaviour.
2026-09-11 10:17:27 +05:30
Vasanthdev2004 bfa40a79ca fix(sandbox): say what changed when the setup marker is rejected
"permission roots or deny lists changed" told an operator that every
sandboxed command would now refuse to run, and nothing else. Not which
side is stale, not by how much, not even whether the marker belongs to
this workspace. Debugging it meant reading the source and guessing,
which is what happened.

Report the marker path, both entry counts and both hashes. The counts
separate the two shapes this takes: equal counts mean the same roots
spelled differently, unequal counts mean one side has roots the other
has never heard of.
2026-09-11 10:17:27 +05:30
Vasanthdev2004 6e342cee45 fix(sandbox): create the runtime roots setup grants
Elevated setup stopped working entirely:

  zero-windows-sandbox-setup.exe: windows ACL target does not exist:
  ...\AppData\Local\Temp\zero\runtime\v1\67b1b01412f588b9

Putting both runtime candidates into the capability plan added a write
root that nothing creates. The capability plan deliberately refuses to
materialize a write root, since an absent path is a typo or a stale
config and inventing the tree would grant write on a directory nobody
asked for, so the whole run fails on a path that is merely missing. Only
the selected root was ever created, and only on the principal path.

Create every candidate on the setup side, before the plan that grants
them is built. The regression walks the plan and fails on any granted
write root that does not exist, so the two halves cannot drift apart
again: today one function chooses the candidates and another creates
them, and nothing else couples them.

Found by the elevated end-to-end run, which is the only thing that
executes this path. No unit test reached it and CI does not run it.
2026-09-11 10:17:27 +05:30
Vasanthdev2004 03c7783905 test(sandbox): make the jail aliasing assertion able to fail
The aliasing test appended a sentinel to the returned jail and then
ranged over the caller's slice looking for it. That can never fail:
append returns a new header, so the caller's length never grows and the
range never reaches the slot the write landed in. It passed against an
implementation that returns the caller's slice verbatim, which is the
exact thing it claims to rule out. Lint noticed the symptom as an
ineffectual assignment.

Assert through the backing array instead: element storage must not be
shared, and an append must not write into the caller's spare capacity.
Both fail against an aliasing implementation.

Also drop windowsSandboxDeterministicRuntimeRootPath, which lost its
last caller to the shared runtime-candidate helper and duplicated its
derivation.
2026-09-11 10:17:27 +05:30
Vasanthdev2004 9fa86240be fix(sandbox): cover both runtime roots in the setup contract
A fresh setup marker rejected the very command it had just been written
for. Engine.run augments the profile with the selected runtime root
before the Windows runner sees it, but setup fingerprinted the bare
profile, so the extra write root changed the ACL plan hash and every
command on a restricted filesystem failed with "permission roots or
deny lists changed".

The runtime root also reached the principal ACL plan only. A principal
command runs on a WRITE_RESTRICTED token, where a write needs the
normal check and the restricting-SID check to both pass, so a root
carrying just the account ACE was still unwritable once the marker
agreed.

Derive the runtime candidates once and present them on both sides of
the setup protocol. Setup covers the cache-derived root and the
temp-derived fallback rather than whichever one it happened to select,
since selection is per process and a command that fell back would
otherwise land on an unprovisioned tree. Both are pure functions of the
workspace root, so setup can cover the set and a later process can
select from it.

Regressions fail without this: the marker one reproduces the exact
rejection, the capability-plan one shows the missing restricting-SID
grant.
2026-09-11 10:17:27 +05:30
Vasanthdev2004 282a29f610 chore: drop a stray probe artifact from the branch
probe-inside.txt is a leftover from the elevated end-to-end probe and was never
meant to be committed. A `git add -A` in the write-jail commit swept it in.

It is what the automated review's diff-hygiene check was failing on: the file
carries trailing whitespace, so `git diff --check` reported a blocker while
tests, build and smoke all passed.
2026-09-11 10:17:27 +05:30
Vasanthdev2004 602b21fab4 fix(sandbox): derive the fallback runtime root instead of minting one per process
Reported by jatmn. sandboxRuntimeRootFor falls back to a private tree when the
cache-derived runtime root would land inside the workspace, and that fallback
called os.MkdirTemp and cached the answer in a process-global map.

Separate processes therefore got separate answers. Elevated setup granted the
sandbox principal write access to the directory it created, and every later
__windows-command-runner process created a different one and pointed TMP,
GOCACHE, npm and the rest at it. Those directories are made by the calling user
and carry no ACE for the principal, so ordinary cache and temp writes failed
with a bare ACCESS_DENIED and nothing naming the sandbox. sandboxRuntimeRootFor
already documented that both callers must agree exactly; the fallback was the
branch where that could not hold.

It now hashes the workspace under os.TempDir, the same shape as the
cache-derived root, so every process reaches the same path with no shared state.
When even that lands inside the workspace it returns an error rather than
picking somewhere arbitrary: a runtime tree governed by the workspace's own
policy makes the sandbox's cache writes indistinguishable from the work it is
confining.

Two consequences worth naming.

It creates nothing now, so the split between deterministicSandboxRuntimeRoot and
the resolver is no longer about avoiding a side effect. The comments that
justified that split on those grounds were rewritten rather than left describing
behaviour the code no longer has.

Teardown can name the fallback tree for the first time. windowsPrincipalTeardown
Paths used the deterministic resolver precisely because the fallback was random
and unnameable, which meant an opted-out machine kept principal ACEs on whatever
tree the fallback had produced. It now goes through the shared resolver and
revokes what commands actually used.

Tests pin the property the defect turned on: a repeated call, which is what a
second process looks like with no shared state, must return the same root. The
old implementation could not have passed that, since only the in-process map
made repeat calls agree. Also pinned: per-workspace separation, that naming the
tree creates nothing so teardown leaves no directory behind, and that the root
stays outside the workspace.
2026-09-11 10:17:27 +05:30
Vasanthdev2004 8c242fc33e fix(sandbox): stop the principal's own SID from defeating its write jail
Reported by jatmn. The principal path appended the account's own SID to the
restricting-SID list before building a WRITE_RESTRICTED token.

That token allows a write only when BOTH the normal token and the restricting
list allow it. The account SID is already enabled in the normal token, so
listing it as a restricting SID makes the second check a formality for anything
granted to that account: every path carrying a direct principal ACE passes both
halves and is writable wherever it sits. The principal's own profile directory,
which Windows creates on first logon with exactly such an ACE, is outside every
configured write root and was writable for that reason.

It is the same defect as the World SID in the restricted list (#865), with the
account SID in place of Everyone. A SID already carried by the normal token
cannot also restrict it.

The previous reasoning, recorded in the comment this replaces, was that the ACL
plan grants the workspace to the principal SID so removing it would jail the
principal out of its own tree. That is not so, because setup applies
BuildWindowsACLPlan on every path, not only the restricted-token one, so each
configured write root already carries a capability ACE as well as the principal
ACE. Confining to the capability SIDs therefore restores the intersection the
jail is supposed to be: a write root satisfies the normal token through its
principal ACE and the restriction through its capability ACE, while a path
holding only a principal ACE now fails the restricted check.

The account SID is passed to windowsPrincipalJailSIDs and excluded there rather
than simply not passed. Naming it makes the exclusion the function's contract
instead of an omission a later edit could undo silently, and it also strips the
SID should it ever arrive through the capability list, which is the route the
World SID took.

On the test jatmn asked for: the existing jail test grants WinBuiltinGuestsSid,
a GROUP, so it exercised a configuration the product never ships and could not
have caught this. The new test plants the account SID INSIDE the capability list
and asserts it is gone, which is deliberately falsifiable: a list that never
contained it would pass against any implementation, including one that appends
the SID straight back. Verified by mutation, disabling the filter fails it with
the reported symptom. A second test pins that the capability SIDs survive, so
the fix cannot degenerate into jailing the principal out of its workspace.

Still outstanding from the same review and not addressed here: the runtime-root
fallback that hands setup and each command runner a different directory, and the
elevated end-to-end evidence.
2026-09-11 10:17:27 +05:30
Vasanthdev2004 9cb9139b77 fix(sandbox): refuse to adopt a ZeroSandboxUsers group Zero did not create
Reported by anandh8x as P2 #3. ensureWindowsSandboxGroup treated NERR_GroupExists
and ERROR_ALIAS_EXISTS as plain success, so any local group that happened to
carry our name was adopted. Its members, and every grant already keyed to it,
silently became part of the sandbox's identity.

A name is not proof of provenance, which is the same reasoning
windowsSandboxUserIsManaged already applies to an ACCOUNT of our name. The group
half was missing. An unprivileged user cannot create a local group, but an
administrator, an installer or an earlier build can, and the principal would
then inherit whatever it grants.

An existing group is now adopted only when it carries the managed comment, read
back with NetLocalGroupGetInfo. Anything else is refused by name rather than
adopted, renamed around or deleted: removing somebody else's group would be
destructive, and provisioning into it is the hole being closed.

The decision is split from the syscall into resolveWindowsSandboxGroupAdd so it
can be tested without Administrator and without leaving a real local group on
the machine running the suite. Tests cover both "already exists" statuses,
refusal for a foreign group, adoption of our own so re-running setup still
converges, no ownership probe when we just created it ourselves, an unreadable
probe surfacing rather than being guessed either way, and a real API failure
still failing.

Also rebased onto main, 17 commits behind, under the fresh-base rule. All 51
commits replayed with no conflicts.
2026-09-11 10:17:27 +05:30
Vasanthdev2004 8dd74e23d1 fix(sandbox): fail opt-out only when the principal actually survived
Three corrections, the first to my own previous commit.

Making the opt-out retirement failure fatal was too broad.
removeWindowsSandboxPrincipalForSetup deliberately continues past a secret file
owned by another administrator's setup, reporting it at the end through
errors.Join, so that one unlinkable file cannot strand the account, its logon
rights and its ACEs. The account is already gone when that error is returned.
Treating it as fatal made `zero sandbox setup` fail permanently on such a
machine and rolled back its ACL work, taking the DEFAULT restricted-token
sandbox down over inert residue.

The rule is now the narrower one that was always meant: fatal when the ACCOUNT
survived, because that is exactly what makes an opted-out marker a lie. Asked of
the account rather than inferred from the error, since the error is a join whose
parts are not separable at the call site, and the lookup fails closed so an
undeterminable state counts as still installed. A retirement that left something
inert behind still completes, and still names what it left.

Second, assertWindowsSetupRunsAsCaller cannot fire on any path Zero takes, and
said otherwise. Zero never elevates the helper: runSandboxSetupHelper is a plain
exec.Command and runWindowsSandboxSetup refuses unless already elevated, so the
operator supplies elevation by opening an elevated terminal and BOTH halves run
there. The caller SID is resolved from the process that becomes the helper, so
the two are equal by construction. The guard is kept, because it is a
correctness assertion that becomes load-bearing the moment a ShellExecute
"runas" path is added and already covers a helper invoked directly, but its doc
now says plainly what it does not do. The residual hazard has a different shape
and is loud: elevating as another administrator provisions into that account's
sandbox home, and the operator's own session finds no marker and is told to run
setup.

Third, parseSandboxExecArgs claimed to scan for the separator up front. Every
branch of its loop body returned, so it only ever examined index 0 and the scan
did not exist. Rewritten as the straight-line decision it actually was, which is
also the rule we want: only the first token is the wrapper's.

sandbox exec also built its engine without SensitiveEnvKeys, so a key named by
apiKeyEnv in the user's config was scrubbed for every sandboxed tool call and
handed to the one command whose purpose is to reproduce that environment.

Tests: the opt-out branch now covers both sides of the rule, and
parseSandboxExecArgs gets the coverage it never had, including the reported
`-- cmd --help` case and an invariant that the returned command is always a
trailing slice of the input.
2026-09-11 10:17:27 +05:30
Vasanthdev2004 d0a0506fb4 fix(sandbox): keep elevated Windows setup tied to the caller's identity
Two failures on the elevated setup path, both reported by anandh8x.

The first is caller identity. windowsSandboxPrincipalKey sampled the CURRENT
process token, and elevated setup is not the caller's process: under
over-the-shoulder UAC or `runas` it belongs to whichever administrator typed the
credentials. Setup therefore provisioned an account, a secret, an ACL ledger and
a set of grants named after that administrator, while every later command
derived the ordinary user's key, found nothing, and fell back to the restricted
token. The admin-keyed leftovers were unreachable and nothing would ever reclaim
them.

The caller's SID now crosses the UAC boundary in the setup args, exactly as the
principal opt-in already does and for exactly the same reason, and the key is
derived from it. That fixes everything merely NAMED after the invoking user.

It cannot fix the secret. CryptProtectData derives its key from the user that
stores the blob, so a password sealed by another administrator could not be
unsealed by the caller no matter how the account were named. Provisioning is
refused up front in that case, before an account or a grant exists, with a
message that says how to clear it. The refusal is scoped to the principal
opt-in: the default restricted-token sandbox stores no secret and works fine
across that boundary.

The second is the opt-out path. Retiring an existing principal could fail, and
setup printed the error and carried on to write an opted-out marker and exit 0.
Teardown being idempotent was the argument for continuing, but it is the reason
this must fail instead: a machine with nothing to retire passes straight
through, so an error here means a real account, secret, logon right, ACE set and
ledger are still installed, and the marker now claims none of them exist. Setup
returns non-zero and rolls back its ACL work.

runWindowsSandboxSetup had no coverage at all, since every step wants an
elevated token, a machine-global mutex, real DACLs, the WFP engine or a local
account. The external effects are now seams in the idiom the package already
used for two of them, and the tests drive the step order and each failure path,
including the marker never being written.
2026-09-11 10:17:26 +05:30
Vasanthdev2004 47f26f65a1 fix(sandbox): address jatmn's review on the principal backend and sandbox exec
Four of the five findings were real. Taking them in order of what they cost.

Cross-user principal collision (P1). The account name was keyed on the workspace
alone while its DPAPI secret and ACL ledger both live under the invoking user's
sandbox home, so two Windows users sharing one workspace derived the same account
with private bookkeeping. The second user found no ledger of their own and either
retired the first user's working principal or adopted it and rotated its password
while storing only their own secret; either way the first user's marker still
validated and their next command could not log on.

windowsSandboxPrincipalKey now folds the invoking user's SID into the key. The
setup LOCK deliberately keeps the workspace-only key: two users setting up one
shared workspace still write DACLs on the same paths, so they must keep
serializing even though they now provision separate accounts. Splitting the two
keys is the point, and there is a test asserting they differ.

Ledger not restored on rollback (P1). The narrowed ledger is written only after
everything succeeds, but the rollback closure restored the old ACEs and left it
narrowed. A later setup or teardown reads the ledger to decide what to revoke, so
those restored paths would never be revisited: access outside the current policy
held by an account nothing knows to clean up. The closure now writes back the
union recorded before any DACL changed. Over-recording is the safe direction.

sandbox exec skipped the production planning path (P2). It built a SandboxManager
directly, so it never reached prepareSandboxRuntime and ran without the runtime
write root that a real sandboxed command gets. It now goes through
Engine.BuildCommandPlan. This matters beyond tidiness: the command exists to
prove enforcement, and it was proving a path no tool call takes.

Plan resources leaked (P2). No plan.Cleanup(), so every invocation left a
/tmp/zero-sandbox-report-* behind on Linux. Deferred immediately after the build.

The `--` separator (P2). The reported case, `exec -- cmd --help`, already worked:
the loop hits the separator first and returns. The real break was the tolerated
separator-less form, where `exec mycmd --help` printed Zero's help and never ran
mycmd. The separator is now located before any help flag is interpreted, and help
is only read from the wrapper's own arguments.

Two existing ledger tests seeded state under a username derived from the
workspace key and had to move to the principal key. Worth noting for anyone
running this branch: an account provisioned before this commit will not be found
by the new key, and setup will retire it as unrecorded. That is correct behaviour
for an unmerged branch with no released accounts, but it is not a no-op locally.
2026-09-11 10:17:26 +05:30
Vasanthdev2004 229a6acdf6 fix(sandbox): serialize elevated setup with a per-workspace lock
anandh8x's finding #3, the last of the twelve.

Setup is a transaction, not a write. It rotates the principal's password,
stores the secret, read-modify-writes the ACL ledger, installs WFP filters and
writes the marker. Two setups for the same workspace at once interleave those
steps: the account ends up with one process's password while the stored secret
is the other's, so every later command fails to log on, and the ledger's
read-modify-write silently loses a path set so ACEs that should have been
revoked stay on disk with nothing recording them.

Atomic individual writes do not address this. Each step being all-or-nothing is
orthogonal to two processes interleaving BETWEEN steps, which is the actual
failure, so the lock spans from the elevation check through the marker write.

Nothing to port here: the reference implementation has the identical bug. Its
password rotation and secret write hold no lock, its named mutex guards only an
unrelated read-ACL-only mode and is machine-singleton, and the singleflight
that looks like a fix is process-local.

Decisions worth the reviewer's attention.

Global rather than Local namespace, because the protected state is not
session-scoped: the local account, its LSA logon rights and the WFP filters are
machine state, so setups in different logon sessions must still exclude each
other. Per-workspace rather than machine-wide, because every artifact the lock
protects is per-workspace and a global lock would serialize unrelated setups.

The DACL is Administrators and SYSTEM only, protected. A sandbox principal able
to open this object could hold it and stall every future setup, or create it
first and squat the name so real setup believes it holds a lock it does not.

The OS thread is pinned. Win32 mutex ownership is thread-affine, so a goroutine
that migrated between the wait and the release would call ReleaseMutex from a
thread that does not own the object, leaving the mutex held until process exit,
which is a deadlock for every later setup on the machine.

WAIT_ABANDONED is treated as acquired and reported. The previous holder died
inside the transaction, so the machine may be half set up; setup is idempotent
and re-running it is the repair, whereas refusing would leave no way forward.
A bounded wait rather than skip-and-succeed, because skipping here means not
setting the sandbox up at all.

On the tests: the production DACL means an unelevated process cannot open an
existing lock, so the contention test could not reach the mutex wait anywhere
that matters, including CI. The SDDL is therefore a var the wait tests relax
for themselves, and a separate test pins the production value so loosening it
takes an explicit change. Writing the test first is what surfaced this at all.
2026-09-11 10:17:26 +05:30
Vasanthdev2004 05d7c2f62c fix(sandbox): retire the principal on opt-out, and finish teardown past a foreign secret
anandh8x's findings #6 and #8. They are one commit because #6 calls straight
into the path #8 breaks, so fixing #6 alone would have shipped an opt-out that
aborts on exactly the machines #8 describes.

#8 first. readWindowsSandboxSecret already treats permission-denied as
unavailability rather than breakage, and documents why: an operator who
elevated with a separate administrative account ends up with a secret their
ordinary account cannot open. Removal did not agree. os.Remove returning a
permission error aborted teardown at its very first step, so the account, its
logon rights, its ACEs and its ledger all stayed installed because one file
could not be unlinked. The operator asked for removal, got an error, and kept a
working principal.

Removal now classifies that case distinctly and teardown carries on, reporting
the leftover secret at the end rather than swallowing it. An ordinary removal
failure is still fatal, and there is a test for the difference: misclassifying
one as the other would turn a real failure into a shrug.

#6. Opting out has to actually retire the principal, because that is what we
tell people it does. ValidateWindowsSandboxSetupMarker sends an operator here
in as many words. There was no opt-out branch at all, so the marker flipped to
opted-out while everything stayed exactly where it was: the instruction was a
lie, and the leftovers were invisible, because nothing afterwards looks for a
principal it believes was never provisioned.

Setup now runs teardown on the opt-out path. Not fatal if it does not complete:
teardown is idempotent and a machine that never had a principal passes straight
through, so a failure means genuine residue rather than a missing account. Say
so and finish a setup whose sandbox is otherwise fine.
2026-09-11 10:17:26 +05:30
Vasanthdev2004 f96b8b2f38 fix(sandbox): report an inactive principal in doctor, and finish the comment upgrade
anandh8x's findings #7 and #10.

#7. windowsSandboxPrincipalEligible stands the principal down under
network-deny, which is the DEFAULT policy, so an operator who set the opt-in to
confine reads silently gets the same-user restricted token and no read
confinement at all. Nothing told them. The runner cannot: it is re-exec'd per
command, so the notice would land on the stderr of essentially every tool call,
and it is not per-command actionable anyway. The setup marker validates happily
because setup really did provision the account. The runtime comment already
said this belonged on `zero doctor`, and doctor never carried it.

Doctor now warns, and the rule has one definition rather than two. The
eligibility check asks the same exported predicate doctor does, so the two
cannot drift into disagreeing about whether a principal is in play. Drift here
would mean doctor telling someone reads are confined while commands run on the
restricted token, which is worse than saying nothing.

A warning rather than a failure: commands work and the network is still
enforced. What is wrong is the operator's picture of what they have.

#10. windowsSandboxUserIsManaged has always claimed a legacy account is
"adopted and its comment rewritten on the way through", and it never was:
provisioning only ever set the password (USER_INFO_1003 is documented in this
file as the password-only form). So a pre-key account stayed permanently
unattributable, and every later run had to keep accepting the bare comment to
avoid orphaning it.

Adoption now stamps the workspace key via USER_INFO_1007, which ends that and
lets the bare form eventually be retired rather than accepted forever. Best
effort: the account is adopted and working either way, and failing provisioning
over a cosmetic stamp would strand a usable sandbox for bookkeeping. Reported
rather than swallowed, so a run that keeps re-adopting the same legacy account
is visible.

The legacy-comment probe is a separate function rather than folded into
windowsSandboxUserIsManaged, so that keeps its (bool, error) shape and the test
seam around it does not have to change.
2026-09-11 10:17:26 +05:30
Vasanthdev2004 d43362aca7 fix(sandbox): fingerprint principal grants in the setup marker
anandh8x's finding #4. The marker hashed BuildWindowsACLPlan, the
capability-SID plan, while principal grants are built separately by
buildWindowsPrincipalACLPlan from the same profile. So the marker was blind to
them: narrowing or removing a principal read root left setup looking current
and the old AllowRead ACE sitting on disk. Narrowing a policy has to be able
to take access away, and this was the one path where it could not.

The fingerprint hashes the plan with a fixed placeholder trustee rather than
the real principal SID. The account is recreated with a fresh SID whenever it
is reprovisioned, so hashing the real one would move the fingerprint on every
rebuild even when the granted paths were identical, and every command would
then rerun setup. What must invalidate the marker is the set of paths and
actions, which is what this captures.

Empty when the principal backend is not opted into, so the default install's
marker does not churn. Schema version goes 5 to 6 so existing markers are
treated as stale rather than read as having no principal grants.

Validation refuses a mismatch with the action to take, since the remedy is
re-running elevated setup so the stale grants are actually revoked rather than
merely re-planned.
2026-09-11 10:17:26 +05:30
Vasanthdev2004 2ca6ac69d5 feat(sandbox): add zero sandbox exec to run one command through the sandbox
Until now the sandbox could only be exercised through a full agent turn with a
model in the loop. `zero sandbox policy` reports the posture it would take and
`zero sandbox check` evaluates a hypothetical decision, but nothing ran a
command and let anyone look at what happened on disk afterwards.

That is the root of the verification gap on this branch. Enforcement is covered
almost entirely by tests asserting the shape of an ACL plan, and almost not at
all by tests asserting that a write was refused. The two are not the same
thing, and this branch has already produced the proof: the .git rename guard
was emitted correctly by the planner and silently dropped by the applier, and
four tests covering the plan passed while the ACE was absent from the
directory.

It goes through SandboxManager.BuildCommandPlan, the same path a shell tool
takes, so what it demonstrates is what users get rather than what a test double
does. Backend, enforcement level and workspace are written to stderr before the
command runs, and a downgrade is printed explicitly, so a harness can assert
the sandbox was actually engaged instead of passing because it quietly stood
down. Exit status is the command's own, which a harness asserting a refusal
needs.

Everything after `--` is the command, so its flags are never parsed as ours.

Verified by hand on Windows: a write inside the workspace succeeds and the file
exists; the same write to C:\Windows\Temp fails with UnauthorizedAccessException
and the file is not created. Both halves matter, since a command can fail for
an unrelated reason while the write still lands.

This is the prerequisite for a real smoke harness, which is the actual goal.
2026-09-11 10:17:26 +05:30
Vasanthdev2004 a18523ad65 fix(sandbox): name the root that blocks unelevated ACL setup
Found while testing the default sandbox path, not the principal path this PR
is about. One write root that the current user cannot re-DACL fails the entire
unelevated ACL plan, and the success marker is only recorded on success, so
the identical failure repeats on every later command until that root leaves
the plan. The workspace is effectively unusable in the meantime.

Refusing to run is correct and is left alone: without those ACEs there is no
write jail, so continuing would run a command that believes it is sandboxed
and is not. The defect was the diagnosis. Every failure got the same guess,
"the workspace may be on a filesystem the current user does not own", and
recommended elevated setup, which does nothing when the real problem is a
system directory sitting in the root set.

An access denial now names the exact path, says the sandbox cannot enforce a
boundary there, points at TEMP and TMP as the usual way such a path gets in,
and states plainly that elevated setup will NOT help. Other failures keep the
old message.

The extractor reads the path back out of an error string produced two
functions away, which the compiler cannot check, so a test drives the real
producer rather than hand-writing the message: if openWindowsACLTarget rewords
its error the test fails instead of the diagnostic quietly going blank. That
test earned itself immediately by catching the first version splitting on the
first colon and returning "C", since on Windows the path opens with a drive
colon. It splits on colon-space now, which a drive colon can never be.

The helper sits behind the Windows build tag beside its only caller, for the
same reason windowsACLPlanPaths was moved earlier in this branch.
2026-09-11 10:17:26 +05:30
Vasanthdev2004 b5553577fc docs(sandbox): attribute the Users-group premise the volume-root fix relies on
Cross-checking against another Windows sandbox implementation showed it joins
its account to the built-in Users group explicitly, and then verifies at apply
time whether Users already hold read before granting. Ours gets that membership
implicitly from NetUserAdd with USER_PRIV_USER and asserts the consequence in a
comment. Same conclusion, weaker footing, so the comment now says where the
membership comes from and that a hardened image which strips Users read would
need an explicit bounded read set instead.
2026-09-11 10:17:26 +05:30
Vasanthdev2004 c3d041b0af fix(sandbox): stop granting a principal read at the volume root, and report failed ACE revocation
Two of anandh8x's findings on this PR.

The read grant. permissionProfileReadRoots seeds its list with the bare
separator, because the workspace-write posture is read-all with a write jail.
That costs nothing for the capability backend, whose child runs as the caller
and could read those paths anyway. For a principal it became a real,
persistent, inheritable allow-read ACE for a separate local account at the root
of the current drive, reaching every directory that does not block inheritance.
Verified against the shipped profile rather than argued: with the filter
removed the plan emits AllowRead on the drive root.

Dropping it does not remove the reads a principal needs. It is a member of
Users, and the machine's own ACLs already grant Users read on the system and
program directories. What the grant added was read access to the places Users
are deliberately kept out of, which is the opposite of what a sandbox is for.
The volume root is detected structurally, since filepath.Dir of a root is that
same root, so drive-qualified paths, a bare separator and UNC roots are all
covered on either build host.

The teardown. removeWindowsSandboxPrincipalForSetup discarded the result of
revokeWindowsPrincipalACEs, deleted the account, deleted the ledger and
returned success. A failed revocation therefore left ACEs naming that SID on
the user's tree while the only record of which paths they sat on was removed
moments later: residue nothing could find again.

The existing reasoning for not failing hard was right and is kept, since
refusing to remove the account would strand the principal and its logon rights
permanently. So teardown still completes, but the error is now remembered, the
ledger is kept when revocation failed, and the returned error says the ledger
was kept. A record that outlives its principal is a smaller problem than
unfindable residue.

The new read-root test is built from the production profile, and skips loudly
rather than passing silently if that profile ever stops carrying a volume root.
It also asserts the workspace itself stays reachable, so the fix cannot trade a
real grant for a broken sandbox.
2026-09-11 10:17:26 +05:30
Vasanthdev2004 d2968aef28 fix(sandbox): apply the .git rename guard on a workspace that had no .git
Found by gnanam1990 and anandh8x independently, and confirmed on disk before
fixing: the deny-delete ACE that stops a principal replacing .git was silently
absent on exactly the workspace shape that matters most.

.git deliberately carries no Materialize, because creating an empty one breaks
`git init`. Groups are applied in ascending path order, so the .git group ran
while .git did not yet exist, was skipped as a non-materializing missing
target, and nothing revisited it when the .git\config carveout created .git as
its parent chain moments later. windowsACLGroupRequiresExistingTarget did not
catch it either, since it only treats AllowWrite as requiring an existing
target. Net effect: the principal could rename .git aside and recreate it
without the config and hooks carveouts, which is the escape the guard exists
to stop.

Groups skipped for a missing target are now retried once after the pass, since
a later group can create what an earlier one needed. Groups that are genuinely
absent simply skip again. Ordering is otherwise untouched, so the reverse-order
unwind that rollback depends on still holds.

Fixing the gate to demand an existing target for deny-delete would have been
wrong: it turns a fresh clone into a setup failure. Materializing .git is
likewise ruled out by git init.

The four existing guard tests assert the mask and what the planner emits, and
all four pass with the guard absent from disk, which is why a green suite said
nothing. The new tests apply the plan and read the actual DACL back through
SDDL. Verified the fresh-workspace case fails without this change and passes
with it, while the already-has-.git case passes either way, so the new coverage
is pinned to the defect rather than to the code.

Also moves windowsACLPlanPaths behind the Windows build tag. Every caller is
Windows-tagged, so defining it in the portable file made it dead code on Linux
and macOS and failed make lint-static, as anandh8x reported.
2026-09-11 10:17:25 +05:30
Vasanthdev2004 6a1b4562d0 fix(sandbox): reject protected metadata names that escape the write root
ProtectedMetadataNames is documented as names, but it is joined onto the write
root to place a deny ACE and to materialize the directory that ACE protects. A
value containing ".." or a separator puts both outside the workspace: the deny
lands on a directory the sandbox does not own, and elevated setup creates it
there. Raised by CodeRabbit on this PR.

Not reachable today, since the only caller passes a package constant. It is
guarded so that stays true if a future caller sources these from config, which
is the kind of change that would not obviously be a security decision.

The component check moves to the portable file so both users share it. The
handle-relative primitives need it because NtCreateFile resolves a relative
name containing separators the ordinary way, following any junction inside it;
the plan builder needs it for the escape above. Separators are matched
explicitly rather than through filepath.Base, because these are Windows paths
whatever the build host is, and on Linux filepath.Base leaves a
backslash-joined name untouched and would wave it through.

Rejection tests are in the portable test file, so they run on all three
platforms alongside the rest of the plan-builder coverage.
2026-09-11 10:17:25 +05:30
Vasanthdev2004 011c4dad15 fix(sandbox): bind windows ACL materialization and rollback to handles
Closes the two path-swap findings on this PR. Both had the same cause: an
object was addressed by a pathname that the kernel re-resolves at the moment
the call runs, so a workspace owner could change what that name meant in the
gap between checking it and using it. Junctions need no privilege, so this was
reachable by exactly the unprivileged user the sandbox exists to contain.

Materialization verified a component, closed the handle, then handed the same
string to os.Mkdir. Swapping the verified ancestor for a junction inside that
gap got the component created outside the approved tree, as Administrator, and
verifying again afterwards cannot un-create it. It now opens the deepest
existing ancestor once and creates each missing component relative to the
handle of the level above, so the tree it descends is pinned to objects rather
than named by strings.

Rollback called os.RemoveAll on the target pathname, so an ancestor swapped to
a junction after creation sent a recursive elevated delete into an unrelated
tree. It now records what it created as single components under an anchor and
unwinds them handle-relative, deepest first. It also removes the whole chain
rather than only the final component, which the old comment claimed was fixed
and was not, and it removes only what the kernel confirmed this run created,
so a racing creator no longer gets its directory deleted on teardown.

Three things this turned up that were not in the original findings:

The delete primitive used FILE_DELETE_ON_CLOSE, which defers the removal to
cleanup and reports a non-empty directory to nobody: open succeeded, close
succeeded, directory still there. Wired into rollback that would have been
worse than the os.RemoveAll it replaced, since rollback would report success
while leaving state on disk. It now sets the disposition explicitly, so
STATUS_DIRECTORY_NOT_EMPTY comes back to the caller. Residue is preferable to
recursing through a path someone else controls; lying about it is not.

The child create never inspected the handle it returned, so an existing
junction was handed back as the next parent in the walk and every deeper
create landed on the far side of it. Component names are now validated as
single components too: NtCreateFile resolves a relative name containing
separators the ordinary way, which would have walked straight through an
intermediate junction.

Rollback re-opens the anchor by pathname and checks its volume and file index
against what materialization saw, because replacing a directory with another
real directory of the same name needs no reparse point at all and passes every
no-follow check there is. Holding the handle instead would be stronger, but
three call sites deliberately discard the rollback closure and would leak.

Testing. makeWindowsACLDirChainNoFollow carries a seam that fires between
verifying the anchor and creating anything, because a race nobody can trigger
on demand is not a regression test. The existing junction test plants its
junction before the walk starts and so never reached this. The new test has a
control arm that performs the identical swap and creates by pathname, and
asserts the object does escape, so the fixed arm proves the hole was open
rather than proving some code ran. Also covers the file target, rollback
through the closure callers actually hold, and the non-empty case that the
old empty-directory-only delete test hid.

Validation now runs before the filesystem is touched, so a malformed entry no
longer creates a chain and then fails.
2026-09-11 10:17:25 +05:30
Vasanthdev2004 c2cf7b8f3a fix(sandbox): keep the git rename guard tests portable
The two rename-guard tests built their expectations from a hardcoded
C:\work\repo, but buildWindowsPrincipalACLPlan normalizes every write
root before it names an ACE. On Windows that root is already absolute,
so normalizing is a no-op and both tests passed locally. On Linux and
macOS it is not absolute, so the plan named a different path and both
tests failed. The plan builder is portable code with no build tag, so
these tests run on every platform.

Use an OS-neutral root and normalize the expected path the same way the
plan does, which is what the other untagged test in this package
already does. The Windows-only assertions about the ACE mask and its
inheritance stay where they are, in the file that is tagged for it.
2026-09-11 10:17:25 +05:30
Vasanthdev2004 2d5e1f7885 feat(sandbox): handle-relative directory create and delete on Windows
Groundwork for the two remaining materialization P1s. No call sites yet;
the walk and the rollback move onto these next.

Every pathname-based call re-resolves the whole path inside the kernel
when it runs, so verifying a component and then creating through it are
two separate resolutions of the same string. A workspace owner can swap
an ancestor for a junction in that gap. Demonstrated, not theorised: with
the same swap performed between verify and create, os.Mkdir put the new
directory OUTSIDE the approved tree ("landed inside approved tree: false,
ESCAPED outside approved tree: true"), and the post-create check cannot
un-create it.

A handle pins the object rather than the name, so a create resolved
against it cannot be redirected however the path is later rearranged.
os.Mkdir, os.OpenFile and os.RemoveAll are pathname-based by construction
with no relative form on Windows, hence NtCreateFile with
OBJECT_ATTRIBUTES.RootDirectory. x/sys/windows already exposes every
piece, so this adds no hand-rolled syscall bindings.

createWindowsACLChildDirectory reports whether it created or opened,
because rollback must delete only what it made; removing a directory that
already existed would destroy a user's data over an unrelated failure.
deleteWindowsACLChildDirectory is the counterpart that rollback needs:
os.RemoveAll on a pathname whose ancestor has since become a junction
recurses outside the workspace.

The fix also makes the race testable. Against the old code the swap had
to be threaded into the middle of a function; here it is three ordinary
lines between an open and a create, because the handle is held across
them. Both tests perform the real swap and assert the operation stayed
inside the verified directory, and the delete test leaves a bystander
under the decoy whose survival proves the delete never resolved by path.

Refs #808.
2026-09-11 10:17:25 +05:30
Vasanthdev2004 bcae716a07 fix(sandbox): stop a principal replacing .git to shed its carveouts
The write-denied carveouts guarding .git are attached to .git/config and
.git/hooks as OBJECTS. The workspace allow grant is inheritable and
carries DELETE, and nothing denied DELETE on .git itself, so a principal
could rename .git aside, recreate it, and create fresh config and hooks
that inherit the allow with no deny of their own. That restores
credential.helper and core.hooksPath, and with them arbitrary code
execution on the next git command.

.git could not simply join sandboxFullyProtectedMetadataNames next to
.zero and .agents: that list emits DenyWrite, whose mask includes
FILE_GENERIC_WRITE, and git has to write index, objects and refs. Its
absence from that list was correct and was also the hole.

Add WindowsACLDenyDelete: DELETE, WRITE_DAC and WRITE_OWNER only.
Renaming a directory needs DELETE on that directory, so denying it is
what closes the replacement. WRITE_DAC and WRITE_OWNER come along because
a guard the principal can rewrite is not a guard. FILE_GENERIC_WRITE and
FILE_DELETE_CHILD stay out so git keeps working.

The ACE is applied uninherited, which is why the narrow mask is safe:
inherited onto .git's children it would deny DELETE on every file inside
and git could not remove a lock file or a ref. windowsExplicitAccessEntries
hardcoded SUB_CONTAINERS_AND_OBJECTS_INHERIT for every directory entry,
so inheritance is now decided per action.

The entry is not materialized. git creates .git, and an empty one made by
setup breaks git init.

Reported by @jatmn on #808.
2026-09-11 10:17:25 +05:30
Vasanthdev2004 7f45a7cd54 test(sandbox): compare ACL record paths the way the plans do
The two new record tests failed on the Windows runner and passed
everywhere else. The plan builder runs every root through
normalizeProfilePath, whose EvalSymlinks expands the 8.3 short name
GitHub's runners hand out for TEMP, so the record held
C:\Users\runneradmin\... while t.TempDir() had returned
C:\Users\RUNNER~1\... and an EqualFold on the raw spellings called two
spellings of one directory different paths.

Production was never affected: the recorded paths and the newly planned
paths both go through that same normalization, so setup and teardown agree
with each other. This was only the test being naive about what "same path"
means on Windows, and a developer whose volume has 8.3 name generation
disabled cannot reproduce it — which is how it shipped.

The comparison now normalizes both sides through normalizeProfilePath and
keys them with windowsCapabilityPathKey, which is what the ACL plans
themselves use. Re-checked against the mutation that matters: reverting the
revocation to the new plan's paths alone still fails
TestReSetupRevokesARootTheNarrowedPolicyDropped, so the looser-looking
comparison has not defanged the assertion.
2026-09-11 10:17:25 +05:30
Vasanthdev2004 cae96b2830 fix(sandbox): revoke principal ACEs on roots that left the policy
applyWindowsPrincipalACLs revoked the trustee only from the paths of the
plan it was about to apply. A root that LEFT the policy is by definition
absent from that plan, so its ACE survived the re-setup marker validation
forces and the principal kept write access the current policy no longer
grants -- the sandbox widened as a result of being tightened. Teardown
repeated the same current-plan-only calculation, so retiring the principal
cleaned every path except that one, and then deleted the account, leaving
the ACE naming a SID nothing could resolve.

Nothing on Windows can answer "which paths hold an ACE for this SID"
without walking every volume, so the grants are now written down as they
are made: a per-principal record beside the secret, keyed the same way
because one sandbox home serves every workspace on the machine. Setup
revokes over the union of the recorded paths and the new plan's; teardown
revokes over the same union.

The record is written as that union BEFORE any DACL changes and narrowed
to the granted set after, so a crash in between leaves a superset rather
than a record missing paths the run granted. A superset is the safe
direction: revoking a path that holds no ACE for the trustee is a no-op.

The interesting case is a principal from an earlier setup with no record.
Proceeding with an empty prior set would be the fail-open, on the one path
where the prior set is not empty but unenumerable. Setup retires that
account before provisioning instead: Windows never reuses a deleted local
account's RID, so whatever ACEs cannot be found end up naming a principal
that no longer exists, and the SID minted next is one no DACL on the
machine can already carry. It needs no new operator action, which matters
-- there is no `zero sandbox teardown` to send anyone to.

Every guard is mutation-checked. Reverting the union to the new plan's
paths fails the end-to-end test against real DACLs with "the principal
kept its grant on a root the narrowed policy removed"; moving the record
after the grant, dropping the retirement, reverting teardown, and trusting
an unknown schema each turn a different test red.

Two existing tests move to the new applyWindowsPrincipalACLs signature.
2026-09-11 10:17:25 +05:30
Vasanthdev2004 f18e645c8b fix(sandbox): carry the principal opt-in through the setup protocol
Elevated setup and the commands that later use a principal each read
ZERO_WINDOWS_SANDBOX_IDENTITY from their own process environment, and setup runs
in a separate, UAC-elevated process whose environment is not the caller's.
commandConfig() returned a nil Env, so the gate in windows_setup_windows.go fell
through to os.Getenv in the elevated helper. The two halves could disagree and
nothing detected it.

Direction B is the dangerous one: command opted in, setup did not. Marker
validation passed (the marker recorded nothing about the opt-in), the principal
lookup then declined with a nil error, and the command ran on the same-user
restricted token — which by its own comment does not confine reads — while the
operator believed an account boundary was isolating it. No warning fired.
Direction A left an orphaned account holding batch-logon rights and workspace
ACEs that teardown never retires, because teardown sits inside the same opt-in
branch.

The opt-in is now resolved in the shell the user typed `zero sandbox setup` into
and serialized across the UAC boundary as --sandbox-principal 0|1. The marker
records it (schema 4 -> 5) and validation refuses on mismatch, before the ACL and
network checks. Both directions refuse rather than fall back silently: an
unreadable value is rejected outright, since guessing "off" would provision a
weaker sandbox than asked for and report success.

PrincipalOptIn is a *bool, not a bool. Unset means "consult the environment"
rather than "opted out", so the existing smoke-test callers that do not set it
keep working instead of serializing --sandbox-principal 0 while the command half
still consults os.Getenv.

Dropped the deny-mode fallback warning added alongside this. Announcing it looked
right, since deny is the default mode and an opted-in operator therefore never
gets a principal for ordinary commands. But this runner is re-exec'd per command,
so its sync.Once is once per COMMAND: the notice would print on nearly every tool
call, and noise that repeats gets filtered rather than acted on. It is also not
actionable per command. `zero doctor` carries the opt-in now and is the right
surface for a standing configuration fact. The deny-mode behaviour stays pinned
by TestPrincipalBackendDefersToRestrictedTokenWhenNetworkDenied.

Reported by jatmn on #808.
2026-09-11 10:17:25 +05:30
Vasanthdev2004 949ee3d761 fix(sandbox): keep the principal inside the Windows write jail
The principal branch handed the raw LogonUser token to CreateProcessAsUser. That
token is a full token for the account, so the sandboxed child kept every write
its ambient memberships grant. The ACL plan can add grants and denies at named
paths, but it cannot revoke what BUILTIN\Users, Authenticated Users or
NT AUTHORITY\BATCH already allow elsewhere — so an opted-in command whose
profile permitted writes only to the workspace and runtime roots could still
write C:\Users\Public\Documents, which grants BATCH modify and which a batch
logon therefore satisfies.

The principal now gets its own identity AND the restricted token, not one or the
other: reads stay confined by its ACEs, writes by the restricted-SID check.

The principal's own SID joins the capability SIDs deliberately.
applyWindowsPrincipalACLs grants the workspace to identity.SID rather than to a
capability SID, so omitting it would leave the workspace grant matching nothing
in the restricted list — a jail that locks out the inmate and no one else. The
SID is read back from the token itself rather than threaded through the call, so
it cannot drift from the identity actually running.

Not fixed here, and separate from this finding: worldSID is unconditionally in
the restricted-SID list, so any path whose DACL grants Everyone still satisfies
the restricted check on both this path and the pre-existing fallback. That
predates the principal work and is raised with the maintainers separately.

Reported by jatmn on #808.
2026-09-11 10:17:24 +05:30
Vasanthdev2004 97c8c98068 fix(sandbox): reject reparse ancestors before creating an ACL target
FILE_FLAG_OPEN_REPARSE_POINT only stops the FINAL path component being followed.
materializeWindowsACLTarget built its target with os.MkdirAll and os.OpenFile on
the pathname, and both resolve ancestors — so the ancestor reparse check on the
subsequent no-follow re-open ran only after the objects already existed.

An ordinary workspace owner needs no privilege to create a junction. Turning
.git into one before elevated setup runs, with config absent, had setup create
the target at a location of the attacker's choosing as Administrator. Rejecting
it afterwards does not undo that, and the failure path removes only the final
component, so every intermediate directory MkdirAll created outside the
workspace survived permanently.

Creation now goes through makeWindowsACLDirChainNoFollow, which walks up to the
deepest existing ancestor and verifies it no-follow first. One check suffices for
the whole chain above it because GetFinalPathNameByHandle answers for the entire
resolved path. Missing components are then created one at a time, each
re-verified immediately after creation, so a component swapped for a junction
mid-walk is caught before anything lands underneath it.

Taken over the relative-handle NtCreateFile route because x/sys/windows offers no
ergonomic relative-create primitive, and this leaves a window of one component
with an immediate post-create check rather than create-everything-then-verify.

Reported by jatmn on #808.
2026-09-11 10:17:24 +05:30
Vasanthdev2004 7070993ef9 fix(sandbox): surface a failed stale-secret cleanup after rotation
The provisioning rollback removes the stored secret when this run created the
account or rotated an adopted one's password, because in both cases what is on
disk cannot authenticate and absent beats stale: the command path treats a
missing secret as "not provisioned" and falls back, while a stale one fails the
logon and reports a broken sandbox.

That removal ignored its own error. When it failed, the invariant it exists to
keep was not restored — a credential for a password that no longer works stayed
on disk — and setup said nothing. The operator met a provisioned-but-unusable
principal on the next command instead of hearing it from the run that broke it.

undo now returns that one error and the five failure paths join it onto the
error they were already returning, so the original cause and the cleanup failure
both surface. The message names the file and what to do about it. The other undo
steps still swallow: they leave residue, while this one leaves a credential.

Reported by jatmn on #808.
2026-09-11 10:17:24 +05:30
Vasanthdev2004andClaude Opus 5 d685d83df6 fix(sandbox): stop teardown creating a directory while naming one
windowsPrincipalTeardownPaths said the runtime root was "resolved without
creating it, since teardown has no business making directories on its way
out". That was my comment and it was false: it went through
sandboxRuntimeRootFor, whose fallback calls os.MkdirTemp when the
cache-derived root would land inside the workspace. So cleanup created a
fresh temp directory, and a useless one — the fallback root is random per
process and could never match the tree the commands actually used.

sandboxRuntimeRootFor is split: deterministicSandboxRuntimeRoot computes the
cache-derived path and says whether it is usable, creating nothing, and the
existing resolver keeps the fallback on top of it. Teardown takes the pure
one and simply has no runtime tree to revoke when it reports unusable, which
is correct — there is no way to name the random root from here anyway.

The first version of the test called the pure resolver directly. It passed,
and reverting the call site to the creating one left it passing. It now
drives windowsPrincipalTeardownPaths and counts temp-directory entries
across the call, and that mutation fails it.

Co-Authored-By: Claude Opus 5 <[email protected]>
2026-09-11 10:17:24 +05:30
Vasanthdev2004andClaude Opus 5 7e996fa4fd fix(sandbox): close the delete-through-parent, junction-ancestor and rollback gaps
Three findings from jatmn's review, all reachable only under the opt-in
principal backend but all real.

FILE_DELETE_CHILD is no longer granted. On a parent it authorises deleting a
child whatever the child's own DACL says, so granting it on a write root
handed back the carve-outs underneath: delete .git/config, recreate it, and
the replacement inherits the grant with no deny of its own — restoring the
credential.helper and core.hooksPath control the carve-out exists to
prevent. It was granted to keep the mask symmetric with the deny mask, which
is the wrong instinct: denying a capability is not a reason to grant it. The
comment two lines up already made that argument for WRITE_DAC and
WRITE_OWNER. DELETE alone still covers removing and renaming files inside
the roots, which is what the grant is actually for — verified before
removing it.

Note this does NOT close the second route jatmn described: .git itself
carries no ACE, so renaming the whole directory aside needs only DELETE.
That needs a guard on .git and is not in this commit.

ACL targets are now rejected when a PARENT is a reparse point. CreateFile
resolves ancestors even with FILE_FLAG_OPEN_REPARSE_POINT, so the
final-component check passed while elevated setup rewrote the DACL of an
object outside the workspace. Junctions need no privilege to create, unlike
symlinks, so this was reachable by exactly the unprivileged user the sandbox
contains. GetFinalPathNameByHandle answers where the handle really landed,
covering every component in one call instead of walking the path and racing
between checks. The comparison is against the path's own resolved form, so a
differently-cased or 8.3 spelling is still accepted.

The revocation's rollback is returned instead of discarded. Discarding it
was justified on the grounds that the only failure path removes the
principal outright — true for a principal this run CREATED, false for one it
ADOPTED, which #812 keeps alive on failure rather than destroying someone
else's working account. The account survived with its previous ACEs stripped
and the new ones rolled back: logged on, and unable to reach its own
workspace. Teardown still discards it deliberately, since putting ACEs back
on an account about to be deleted is the opposite of the point.

Co-Authored-By: Claude Opus 5 <[email protected]>
2026-09-11 10:17:24 +05:30
Vasanthdev2004andClaude Opus 5 6b54ac0814 test(sandbox): assert the ancestor walk, not the old all-or-nothing contract
TestCanonicalWorkspaceRootFallsBackWhenResolutionFails asserted that a path
with missing segments came back as the plain cleaned path. That was the
behaviour before the ancestor walk, and Windows CI failed it correctly:

    canonical("C:\Users\RUNNER~1\...\001\never-created\deeper")
      = "C:\Users\runneradmin\...\001\never-created\deeper", want the cleaned path

The existing ancestor resolved and the missing remainder was re-appended,
which is precisely what the walk exists to do. The assertion now says that:
the result equals the canonical parent joined with the segments that do not
exist, and those segments survive rather than collapsing to the ancestor.

Co-Authored-By: Claude Opus 5 <[email protected]>
2026-09-11 10:17:24 +05:30
Vasanthdev2004andClaude Opus 5 8d42270e30 fix(sandbox): resolve through path segments that do not exist yet
The previous fix normalized both the workspace root and the cache root, and
macOS CI still failed the same way. EvalSymlinks fails outright when the
LEAF does not exist, and a cache root has not been created at the point it
is first normalized — so the workspace resolved (/var to /private/var)
while the cache root did not, and the containment check that decides
whether the runtime tree must move out of the workspace compared the two
anyway.

canonicalSandboxWorkspaceRoot now resolves the longest existing ancestor
and re-appends the remainder, so a path normalizes the same way whether or
not its final segments exist:

    /var/.../001/.cache        leaf missing, walk up
    /var/.../001               resolves
    /private/var/.../001/.cache

Terminates at the filesystem root, where it falls back to the cleaned
absolute path, and a path with no symlink anywhere along it is unchanged.

The regression test needs a symlink to produce a spelling only resolution
reconciles, so it skips on Windows — where creating one needs privilege —
and runs on the platforms that caught this. I could not reproduce either CI
spelling locally: this box's temp paths are already canonical and 8.3 alias
creation is disabled on the volume.

Co-Authored-By: Claude Opus 5 <[email protected]>
2026-09-11 10:17:24 +05:30
Vasanthdev2004andClaude Opus 5 0b5950e882 fix(sandbox): normalize the cache root too, not just the workspace root
sandboxRuntimeRootFor compares the workspace root against the runtime root
it derives from the cache root, and falls back to a private temp tree when
the derived root would land inside the workspace. The previous commit
canonicalized only the workspace root, so that comparison ran on two
different spellings of the same path and the containment check missed:

    macOS:   /var/folders/... vs /private/var/folders/...
    Windows: C:\Users\RUNNER~1\... vs C:\Users\runneradmin\...

The fallback never fired and the runtime tree was placed inside the
workspace it exists to stay out of. Both CI runners caught it; my box did
not, because its temp paths are already canonical and 8.3 alias creation is
disabled on the volume, so I could not reproduce either spelling locally.

Both inputs now go through canonicalSandboxWorkspaceRoot, on the
cross-platform path and the Windows setup path.

The regression test uses a symlink, which is the portable way to produce a
spelling only resolution reconciles — Clean cannot see through one. It
skips on Windows, where creating one needs privilege, and runs on the
platforms that caught the bug.

Two things about that test are deliberate. My first version used a
redundant-segment path, which Clean already normalizes, so reverting the
fix left it passing. My second resolved nothing before asserting, and
through the link the runtime root shares no textual prefix with the
workspace — it would have called a root sitting physically inside the
workspace "outside" and passed against the exact bug it exists for. It now
resolves before comparing.

Co-Authored-By: Claude Opus 5 <[email protected]>
2026-09-11 10:17:24 +05:30
Vasanthdev2004andClaude Opus 5 c6921d4145 fix(sandbox): canonicalize the workspace root on both sides, not just setup
Windows CI caught two faults in the previous commit. Both came from
canonicalizing one side of a pair.

setupWindowsSandboxRuntimeRoot resolved the workspace root while
prepareSandboxRuntime still only cleaned it, so the two disagreed exactly
where they had to agree. It passed locally because my temp paths were
already canonical; a Windows runner's TEMP is an 8.3 short path that
resolution expands:

    setup granted ...\runtime\v1\5e2d212300ccdfba
    commands use  ...\runtime\v1\92c31f8cf536dfde

The canonicalization moves to canonicalSandboxWorkspaceRoot in
runtime_state.go and both sides call it, which is what the original fix
should have done.

The carveout shape was rebuilt from the RESOLVED write root and compared
against subpaths that cannot resolve, since .git/config does not exist at
setup and normalizeProfilePath falls back to Clean when EvalSymlinks fails.
Two spellings of the same path therefore missed the lookup and .git/config
went back to being created as a directory — the original bug, reintroduced
quietly by its own fix. gitMetadataCarveoutIsFile now matches on the
trailing segments, derived from the spec list so it cannot drift from it,
and no reconstructed absolute path is compared at all.

Both failures now have regression tests that reproduce the non-canonical
root by lowercasing, which needs no short name and no privilege. Reverting
either fix fails them.

Co-Authored-By: Claude Opus 5 <[email protected]>
2026-09-11 10:17:24 +05:30
Vasanthdev2004andClaude Opus 5 227f4ed6ef fix(sandbox): revoke ACEs on teardown and key setup off the resolved root
Two ways setup and the command path disagreed.

Teardown removed the secret, the LSA rights and the account, but never the
ACEs. Once the account is gone its SID stops resolving and every ACE naming
it becomes an orphaned raw-SID entry on the user's own tree — precisely the
residue the capability-SID model left behind and this one exists to avoid.
Revocation now runs while the SID still resolves, by trustee so it also
clears grants written by older versions. A revoke failure is deliberately
not fatal: a path the user has since deleted cannot be cleaned, and
refusing to remove the account over it would strand the principal and its
logon rights permanently, which is worse than a leftover ACE.

The runtime root was derived from filepath.Clean(WorkspaceRoots[0]) at
setup while Engine.resolveCommandDir cleans, absolutizes and then
EvalSymlinks it. That needs no symlink to diverge — Windows opens a path in
any casing and EvalSymlinks canonicalizes it:

    setup sees   c:\users\me\myworkspace
    command sees C:\Users\me\MyWorkspace

so setup granted the principal one runtime tree and every command used
another. The grant that exists to make npm/go/pip caches writable landed
where nothing reads, surfacing as a bare ACCESS_DENIED on a cache write.
Both now go through canonicalWindowsSandboxWorkspaceRoot. An unresolvable
root falls back to the cleaned absolute path, matching the command path
rather than failing.

setupWindowsSandboxRuntimeRoot is split into derivation and creation so
teardown can name the tree without making directories on its way out.

The first version of the divergence test called the canonicalization helper
directly. It passed, and reverting setup to filepath.Clean — the actual bug
— left it passing. It now drives windowsSandboxRuntimeRootPath, and that
mutation fails it.

Co-Authored-By: Claude Opus 5 <[email protected]>
2026-09-11 10:17:24 +05:30
Vasanthdev2004andClaude Opus 5 8a84471dc9 fix(sandbox): revoke stale principal ACEs before re-applying the plan
windowsPrincipalRevokePlan was implemented and tested but had no production
caller, so nothing ever used it. applyWindowsACLPlan merges into the
existing DACL, which means a re-run after narrowing a write root or
shortening a deny list left the previous, wider ACEs sitting beside the new
ones: the principal kept access the current policy no longer granted, and
the sandbox silently widened as a result of being tightened.

Setup does get the chance to notice — marker validation already refuses
commands with "permission roots or deny lists changed" until setup runs
again — so the re-apply is exactly where this belongs.

The ACL step is extracted into applyWindowsPrincipalACLs: build the plan,
revoke every ACE naming this trustee on the paths it touches, then apply.
Revocation is by trustee rather than by remembered path, so it also clears
grants written by an older version of Zero. Its rollback is discarded on
purpose — the only failure path from here removes the principal outright,
and restoring stale ACEs for an account about to be deleted is the residue
this exists to prevent.

Extracting it also makes the ordering testable without new provisioning
seams, which #812 already adds with a different signature; adding them here
would have collided on its rebase.

Three tests: revocation actually drops a grant on a root that left the
policy while keeping the one that stayed (asserted against the real DACL,
counting deny ACEs as well as allow, since trustee revocation drops both);
revoking a path that was never created is a no-op rather than an error; and
the production path revokes BEFORE it applies. That last one is the one
that matters — the first two pass just as happily with the call site
deleted, and deleting it kills only the third.

Co-Authored-By: Claude Opus 5 <[email protected]>
2026-09-11 10:17:24 +05:30
Vasanthdev2004andClaude Opus 5 6ff26014d5 fix(sandbox): re-check principal privilege when minting a command token
Provisioning refuses an account that is already in Administrators, Power
Users or Backup Operators, but group membership is not frozen at setup. An
account provisioned clean can be added afterwards — by an operator, or by
an attacker who already has that access and would like the sandbox to hand
it back. Every command after that minted a token for a privileged account.

The re-check goes on the path that mints the token, not inside
lookupWindowsSandboxIdentity. Teardown resolves the same identity to revoke
its logon rights before deleting the account, so refusing there would leave
the very account this guards against permanently undeletable by Zero. The
command path already propagates anything that is not the not-provisioned
sentinel, so this surfaces to the operator instead of silently dropping
back to the restricted token.

Also make the gating test hermetic. Its "absent" case passed an empty map,
which falls through to os.Getenv, so a developer with the opt-in exported
saw a different result from CI:

    ZERO_WINDOWS_SANDBOX_IDENTITY=1 go test ./internal/sandbox/
    --- FAIL: TestWindowsSandboxIdentityGating/absent
        enabled = true, want false for ""

Every case there supplies an explicit map entry, so the process variable is
now pinned to prove none of them consult it. The os.Getenv fallback is what
elevated setup actually runs on — it passes no Env — so it gets its own
table rather than riding on a case that also has a map entry.

Co-Authored-By: Claude Opus 5 <[email protected]>
2026-09-11 10:17:23 +05:30
Vasanthdev2004andClaude Opus 5 700e749e30 fix(sandbox): materialize .git/config as a file, not a directory
Materializing the git control-plane carveouts creates a missing target so
the deny-write ACE is in place before git first runs. It did that with
os.MkdirAll on the full path, which is right for .git/hooks and wrong for
.git/config: git wants a file there.

The consequence is worse than a mis-ACL'd path. On a fresh workspace
neither carveout exists — which is exactly the case materialization was
added for, so this is the common path rather than a corner — and elevated
setup would leave a directory where git's config file belongs:

    warning: unable to access '<ws>/.git/config': Permission denied
    fatal: unknown error occurred while reading the configuration files

git init then fails outright and the workspace is unusable.

Materialization now takes the shape from the carveout definition:
gitMetadataWriteCarveoutSpecs is the single source of truth and
gitMetadataWriteCarveouts derives its list from it, so a carveout cannot be
added in one place and have its shape forgotten in the other. A file target
gets its parent chain created and then an empty file; a directory target is
unchanged. A racing creator winning the O_EXCL is treated as success, since
the target existing is all materialization needed.

The regression test runs a real `git init` over the applied plan. It names
Guests as the principal rather than Everyone — with Everyone the deny ACE
also denies the test process and git fails for an unrelated reason, which
would have made the test pass for the wrong reason once the shape was fixed.

Co-Authored-By: Claude Opus 5 <[email protected]>
2026-09-11 10:17:23 +05:30
Vasanthdev2004 73fc1c07ae fix(sandbox): refuse to adopt a principal in a privileged group
Adoption takes over an account whose name and ownership comment match,
resets its password and hands it to the sandbox. An account that is also
in Administrators, Power Users or Backup Operators would give the sandbox
the rights it exists to withhold: rewriting the ACLs confining it, reading
the secret locked to the invoking user, and stopping Zero. The name is
derived rather than discovered, so an account can match without anyone
intending it to.

Membership is resolved by well-known SID rather than by group name, so a
localised install where the group is Administratoren or Administrateurs is
still recognised.

Raised as a non-blocking follow-up in review; it is cheap enough to do now
rather than track.
2026-09-11 10:17:23 +05:30
Vasanthdev2004 f0bc1a3821 fix(sandbox): grant the principal the runtime tree commands write to
Four review findings on the elevated setup path.

The principal had no access to the sandbox runtime root.
permissionProfileWithRuntime appends that root to WriteRoots on every
command and redirects HOME, GOCACHE, npm_config_cache and similar into it,
but it lives under the user cache rather than the workspace, so the
profile setup builds its ACL plan from never contains it. On the
restricted-token path that costs nothing, since the child still runs as
the caller. A principal is a separate local account with none of those
rights, so every npm install, go build or pip install would have failed on
a cache write with a bare ACCESS_DENIED and nothing naming the sandbox as
the cause. Setup now resolves the same root and grants it.

The derivation is extracted so both callers share it. If setup and
prepareSandboxRuntime ever disagreed, the ACE would land on one directory
while commands used another, which is the same failure with a harder
diagnosis, so a test asserts the two agree.

The git control-plane carveouts are materialized. .git/config and
.git/hooks arrive as ReadOnlySubpaths, and applyWindowsACLPlan skips an
absent target, so on a workspace where git had not run yet the deny ACEs
were never written and the principal kept inherited write access once git
created them.

Command-time lookup verifies workspace ownership. The account name carries
only 11 characters of the workspace digest; the comment carries all of it.
Provisioning already refused a foreign account, but the command path
resolved the name straight to a SID, so the workspace that lost a
collision would have run as the other one's principal. SID resolution
still runs first, so an absent account stays the unavailable sentinel
rather than becoming a collision error.

The gated round-trip test asserted a logon with the password from a second
provisioning call. Rotation moved to the setup path, so that value is a
fresh string the account never held. It now exercises the guarantee the
setup path actually makes: the stored secret logs the principal on.
2026-09-11 10:17:23 +05:30
Vasanthdev2004 2175366d4e fix(sandbox): keep an adopted principal's logon rights on rollback
Second round of review findings, both on the elevated setup path.

The rollback revoked logon rights whenever they had been attempted,
without regard to whether this run created the account.
revokeWindowsSandboxLogonRights passes AllRights, which drops every right
the account holds and deletes its LSA object outright. On an adopted
principal that is not a rollback but destruction: a transient grant,
secret-path or secret-write failure during a re-run stripped the
SeBatchLogonRight and deny-logon rights an earlier setup had established,
leaving exactly the broken-but-present principal this path exists to
avoid. Revocation is now scoped to accounts this run created. The rights
granted to an adopted account are the ones it is supposed to hold, so
leaving them is the safe direction.

A secret the current user cannot read now falls back instead of failing
the command. The secret's DACL names whoever ran setup, so an operator who
elevated with a separate administrative account, through runas or an
over-the-shoulder UAC prompt, leaves a secret their ordinary account
cannot open. That is the documented fail-soft case, and treating it as a
hard error made every sandboxed command fail on a machine that was merely
set up by a different admin. Permission errors from the removal path are
deliberately still reported, since incomplete teardown is worth knowing
about.

Both are covered by injected-failure tests and fail if the guard is
removed. The secret read is seamed to inject the permission error, because
producing a real ERROR_ACCESS_DENIED needs DACL surgery and would test the
platform rather than the mapping.
2026-09-11 10:17:23 +05:30
Vasanthdev2004 fd27716dfc fix(sandbox): stop setup destroying a principal it did not create
Six findings from review, all on the elevated setup path.

Teardown was not scoped to what the run created. provisionWindowsSandbox
PrincipalForSetup was careful never to delete an account it had adopted,
and then setupWindowsSandboxPrincipal called removePrincipal on any ACL
failure with no such guard. Re-running elevated setup on a working machine
and hitting one transient ACL error therefore deleted the local account,
its secret and its logon rights. It now returns whether it created the
principal and the outer teardown honours it; ACEs are still reverted,
since this run applied them.

Password rotation moved to immediately before the secret is committed.
Resetting an adopted account's password at the top of provisioning meant
every later step ran against an account whose password had been replaced
with no copy stored. Any failure there left a live account authenticated
by a password nothing on disk knew, and since the account pre-existed the
rollback correctly declined to delete it, so the command path read the
absent secret as "not provisioned" and fell back to the weaker backend for
good. The two operations are now adjacent. The rollback also stops
removing the secret when this run neither created the account nor rotated
it, because that secret still works.

Policy DenyWrite now reaches the principal ACL plan. The capability plan
has always emitted these; the principal plan denied write only on
protected metadata and read-only subpaths, so once the runner used a
principal token a policy deny elsewhere was not enforced at all.

Principal deny-read entries are materialized, matching the capability
plan, so a path created after setup still gets a deny ACE.

Logon-right revocation is keyed to the attempt rather than to success.
Rights are added one at a time and the grant returns on first failure, so
a partial grant left LSA entries behind pointing at a SID that deleting
the account then made unresolvable.

The ownership comment now carries the full workspace key. The account name
holds only 11 characters of the digest, so two workspaces could derive one
name and silently share an account, a secret and an ACL identity; a
mismatch is now refused. Accounts provisioned before the key was recorded
are still adopted.

Also warns once on stderr when the opt-in is set and a provisioned
principal cannot be used, rather than downgrading in silence.
2026-09-11 10:17:23 +05:30
Vasanthdev2004 206046bc04 fix(sandbox): grant delete to the principal and keep rollback able to find it
Two findings from review, both consequences of the principal being a
separate account rather than the calling user.

WindowsACLAllowWrite granted FILE_GENERIC_WRITE, which covers creating and
modifying but not removing or renaming, and a rename needs delete on the
source. Under the old same-user token this was invisible because the caller
already held inherited rights on its own tree. A principal inherits nothing,
so it could write files it could never delete, which fails ordinary editing
and most git operations rather than an edge case. DELETE and
FILE_DELETE_CHILD are now part of the grant, matching WindowsACLDenyWrite,
which already treats delete as part of write. WRITE_DAC and WRITE_OWNER stay
out: they are denied so the principal cannot rewrite its own restrictions.

provisionWindowsSandboxIdentity returned a zero identity alongside
created=true when group attachment or SID resolution failed after NetUserAdd
had already created the account. The caller's rollback deletes by
identity.Username, so it was asked to delete the empty string and left the
account behind. Group attachment is the case that matters, being both the
enforcement boundary and something local policy can refuse. The name now
comes back with the error.

The four provisioning calls are indirected so the failure paths are
reachable in a test. Seaming only the post-creation pair would not have been
enough: every step needs an elevated caller, so the test would have stopped
at the group check and passed without reaching what it names.

Also seeds the empty-secret test with a genuinely empty file. The previous
whitespace seed was several bytes, so it never reached the length check and
failed later in DPAPI instead, which another test already covers.
2026-09-11 10:17:23 +05:30
Vasanthdev2004 e8a0642c58 test(sandbox): check the ACE type before decoding its trustee
GetAce returns a generic ACE_HEADER and the helper reinterprets it as an
ACCESS_ALLOWED_ACE. That holds for the fixed-layout types, but an object
ACE carries Flags and two GUIDs ahead of the trustee, so SidStart would
land mid-structure and Copy would read whatever bytes follow. The caller
asserts that no unexpected trustee appears in the DACL, and on such an ACE
it would print a nonsense SID rather than name the entry that does not
belong.

Nothing under test builds anything but allowed ACEs today, so this changes
no current outcome. It keeps the failure legible if that ever changes.
2026-09-11 10:17:23 +05:30
Vasanthdev2004 17d5674d61 fix(sandbox): drop the stored secret whenever provisioning fails
The cleanup added for partial provisioning left the window it existed for
uncovered. It only removed the on-disk secret when this run had written one,
and it derived the secret path after the logon-rights grant, so a failure
before that point had nothing to remove.

That is exactly the case that matters. Provisioning ALWAYS sets the account's
password, including resetting a pre-existing account's, so from the moment it
returns the stored secret is already stale. A failure in the rights grant then
left that stale secret on disk against a password that had just changed, and
the next command failed the logon and reported a broken sandbox instead of
falling back.

The path is now resolved from the account name before anything can fail, and
removal is unconditional rather than gated on having written one. Absent beats
stale: the command path treats a missing secret as "not provisioned" and falls
back to the restricted token, which is the outcome a failed setup should leave
behind.

Raised by CodeRabbit, twice from different angles, on the commit that added the
cleanup.
2026-09-11 10:17:23 +05:30
Vasanthdev2004 17879dc480 fix(sandbox): refuse a squatted account name and clean up partial provisioning
Two problems in the provisioning path, both raised in review.

The account name is derived from a workspace hash rather than discovered, so it
can be occupied by a local account that has nothing to do with Zero, whether by
coincidence or because somebody put it there. Provisioning treated "NetUserAdd
says it exists" as "this is ours", reset the account's password, added it to the
managed group and adopted it. That is a stranger's account taken over during an
elevated setup, on the strength of a name matching a pattern we generate
ourselves.

Ownership is now proven from the comment provisioning stamps before anything is
touched, and a name held by an account Zero did not create fails with a typed
collision error instead of being adopted.

Second, a failure anywhere after the account existed left it behind. The
rollback the setup path installs is only built once provisioning has returned
successfully, so nothing could undo a failure between creating the account and
storing its secret; the account, and possibly its granted logon rights, simply
stayed. Provisioning now unwinds what the run actually did, in reverse, on every
failure path.

Scoped to what THIS run created, deliberately. An account that already existed
and belongs to Zero is a working principal from an earlier setup, so deleting it
because a later run failed would turn a partial failure into a total one. For
that case the repair is dropping the stored secret instead: this run reset the
password, so the secret no longer matches, and absent beats stale because the
command path treats a missing secret as "not provisioned" and falls back rather
than failing.

The ownership gate is asserted against real accounts every Windows install
carries, which needs no privilege because it only has to establish that they are
not ours. Classifying everything as managed makes it fail.
2026-09-11 10:17:23 +05:30
Vasanthdev2004 a527ffc040 fix(sandbox): revoke logon rights before deleting a principal
Retiring a principal deleted the account but left its LSA account rights
behind, keyed to a SID that no longer resolves. That is the orphaned residue
this model is supposed to avoid, and the reason ACE revocation is keyed to the
trustee rather than to a record of what was granted; the logon-rights half was
simply missing. CodeRabbit spotted it as a test-cleanup gap, but the production
teardown path had the same hole.

revokeWindowsSandboxLogonRights drops every right held by the principal and
removes its LSA entry, and setup teardown now calls it BEFORE deleting the
account, while the SID still resolves. Removing all rights rather than naming
them is deliberate: the principal is being retired, so rights granted by an
older setup that this one no longer knows about should go too.

An account that holds no rights is not an error, since that is the state
teardown wants. That tolerance depends on STATUS_OBJECT_NAME_NOT_FOUND
surviving LsaNtStatusToWinError as something errors.Is can still match, which
is the sort of Windows errno assumption that is often wrong, so there is now an
unprivileged test asserting it, including that the tolerance does not also
swallow access-denied.

Both gated tests now clean up rights and account, in that order. The
provisioning round trip had no cleanup at all and, since it started granting a
batch logon right, was leaving both behind on whatever machine ran it.
2026-09-11 10:17:22 +05:30
Vasanthdev2004 07f6492528 fix(sandbox): reset the password when the account already exists
NetUserAdd leaves a pre-existing account completely untouched, password
included, and ensureWindowsSandboxUser treated that status as success. So a
second setup run generated a fresh random password, stored it as the secret,
and left the account still authenticating with the old one. Every later command
then failed to log on with a principal that looked correctly provisioned. Two
comments claimed the caller reset the password in that case; nothing did.
Caught by CodeRabbit.

ensureWindowsSandboxUser now reports whether the account already existed, and
provisioning resets the password through NetUserSetInfo when it did, so the
value it returns is always the account's real password. The comments now
describe what the code does.

The gated provisioning test provisions twice and then logs on with the password
from the SECOND run, which is the only honest assertion here: a stale password
is indistinguishable from a correct one until something tries to authenticate
with it.

Also makes the syscall keep-alives explicit. The LSA and LogonUser call sites
borrow Go memory that was either not kept alive at all (the policy attributes,
the rights descriptor, the three logon strings) or kept alive only after the
error check, so the failure path returned with it already collectable. The two
netapi32 sites that used a deferred no-op closure now use runtime.KeepAlive as
well, so one idiom is used throughout.
2026-09-11 10:17:22 +05:30
Vasanthdev2004 949e104844 fix(sandbox): surface a squatted principal name instead of falling back
lookupWindowsSandboxIdentity collapsed every SID-resolution failure into the
"no principal is provisioned" sentinel, which threw away the check
resolveWindowsSandboxSID deliberately makes: a name that resolves to a group or
alias rather than a user account. The command path treats that sentinel as
permission to fall back quietly, so an account name squatted by something that
is not a user reached the operator as silence and a downgrade to the restricted
token. Caught by gnanam in review.

Only ERROR_NONE_MAPPED now means setup has not run. Anything else is a
principal that exists but cannot be used, and the runtime path propagates it
rather than swallowing it, which is where the description already said the line
should sit.

The decision lives in its own function because the lookup derives its account
name from a workspace key, so a test cannot hand it a name that resolves to a
group. The test drives the classifier with a real error from a well-known local
group, needs no privilege, and fails if the old collapse-everything behaviour
is restored.

Also corrects a comment pointing at sandboxRuntimeKey, which does not exist.
The function is windowsSandboxWorkspaceKey.
2026-09-11 10:17:22 +05:30
Vasanthdev2004 0b8fcf4b1e feat(sandbox): encrypt the stored principal password to the invoking user
The file ACL stays the primary control and is what keeps the sandbox
principal from reading its own credential. It only binds while the filesystem
is the one being asked, though, so a backup or a mounted image hands over the
password in the clear. CryptProtectData ties the ciphertext to the invoking
user's logon secret, which covers exactly that gap.

The principal name is passed as entropy, so a blob copied onto another
principal's path fails to decrypt rather than authenticating the wrong
account. A secret written by an older build reads as unavailable and falls
back to the restricted token; the next elevated setup rewrites it.

The round-trip test needs no privilege, so it runs everywhere rather than
joining the gated set, and it asserts the password does not appear verbatim
in the stored bytes.
2026-09-11 10:17:22 +05:30
Vasanthdev2004 3e238cc5ea fix(sandbox): keep the restricted token when the network is denied
Network denial is enforced by WFP filters keyed to the offline-marker SID.
The restricted token carries that SID; a token from LogonUser cannot, because
it names the account rather than a synthetic capability SID. Routing a
denied-network command through a sandbox principal therefore left the block
filters matching nothing and dropped egress enforcement altogether, and deny
is the default mode.

The principal now stands down whenever the network is denied and the
restricted-token backend runs instead, so read confinement is never traded
for a silent loss of network denial. Keying the filters to the principal's
own SID is the follow-up that lifts the restriction.

The decision sits in its own predicate rather than inline: on a machine with
nothing provisioned the lookup declines for its own reasons, so a test that
called through it would have passed with the guard removed.

Also names the opt-out variable when a provisioned principal cannot be used,
since the backend is opt-in and the operator needs a way back.
2026-09-11 10:17:22 +05:30
Vasanthdev2004 645976d215 feat(sandbox): provision a sandbox principal during elevated setup
Completes the chain. Until now the principal entry points had no non-test
callers, so `zero sandbox setup` created no account and the runner seam always
fell back: the feature was inert end to end.

Setup now provisions this workspace's principal, grants it the batch logon
right, stores its password locked to the invoking user, and applies the ACL plan
that gives it read+write on the workspace and read on the declared read roots. A
principal is a separate account with no inherent access to the caller's tree, so
those grants are what make the sandbox able to run at all, and their absence
elsewhere is what puts credential stores out of reach.

Provisioning is folded into the existing rollback rather than each later failure
path having to remember it, and the rollback revokes ACEs before deleting the
account: removing the account first would leave ACEs naming a SID that no longer
resolves, which is the orphaned residue this model exists to avoid.

Gated on the same opt-in as the runner. Account creation is visible in
`net user` and is exactly what endpoint protection and enterprise policy object
to, so it happens only when asked for; without the opt-in the capability-SID
backend remains the whole of setup, unchanged.
2026-09-11 10:17:22 +05:30
Vasanthdev2004 273bdede2a test(sandbox): cover the logon-rights and token-minting half
Provisioning is now validated on real Windows, but LsaAddAccountRights and
LogonUser had still never executed, so the principal was proven to exist without
being proven usable.

The batch logon doubles as the assertion that the rights grant worked: a
LOGON32_LOGON_BATCH logon fails with ERROR_LOGON_TYPE_NOT_GRANTED unless
SeBatchLogonRight is actually held, so a token coming back is evidence the grant
landed rather than merely that the call returned success. Granting twice is
exercised too, since setup re-runs must not fail on rights already held.

The token's user SID is compared against the principal's. If a token came back
belonging to the caller the identity boundary would be an illusion and reads
would still run as the user, which is the whole thing this model exists to stop.

Removes any leftover account first and cleans up after itself, because an
interrupted earlier run would leave an account whose password no longer matches
a freshly generated one.
2026-09-11 10:17:22 +05:30
Vasanthdev2004 8dbe818934 test(sandbox): name the per-shell env syntax in the provisioning skip
The skip fired on an unset environment variable but read as though elevation
was missing. `set VAR=1` is cmd syntax and sets a shell variable rather than an
environment variable in PowerShell, so the test skipped silently after the
operator believed they had enabled it. Spell out all three shells.
2026-09-11 10:17:22 +05:30
Vasanthdev2004 ea7c04cdbb feat(sandbox): use a sandbox principal for Windows command execution
Wires the principal model into the runner and settles where the account's
password lives.

The secret is stored under the sandbox home with an explicit,
inheritance-protected DACL naming only the invoking user and SYSTEM. The sandbox
principal is deliberately absent from it: a principal that could read the file
could mint its own token and the identity boundary would be decorative. The ACL
is applied to an empty file before the password is written, so the bytes never
exist under the config directory's inherited permissions, and PROTECTED drops any
inherited ACE outright.

At command time the runner asks for a principal token first and uses it in place
of the restricted token, because a separate account has reads denied by the
filesystem rather than left open the way a same-user restricted token must leave
them. The lookup is fail-soft: opt-out, no provisioned account, or no stored
secret all report "not available" and the existing restricted-token path runs
unchanged. Only a provisioned-but-unusable identity surfaces an error, since
that means setup ran and the sandbox is broken rather than absent.

The backend stays behind ZERO_WINDOWS_SANDBOX_IDENTITY=1 while the privileged
paths are unvalidated, so no existing install changes behaviour.
2026-09-11 10:17:22 +05:30
Vasanthdev2004 17aa51b530 feat(sandbox): add Windows sandbox principals
Groundwork for closing the Windows half of #662 and #675, where
credentialDenyReadPaths is a no-op today.

Every Windows backend currently derives its token from the calling user via
CreateRestrictedToken, so the sandbox can constrain writes but not reads: a deny
ACE that would stop the sandboxed child reading a credential store names the
same account Zero runs as, and would lock Zero out too. That is why deny-read is
skipped on Windows rather than merely unimplemented.

This adds a separate local account per workspace, held in one managed group, so
the sandbox has an identity of its own:

- provisioning: managed group, stable per-workspace account name inside the
  20-character limit, crypto/rand password meeting complexity policy, SID
  resolution, idempotent so setup re-runs converge
- logon rights: grants only SeBatchLogonRight and explicitly denies interactive,
  network, remote-interactive and service logon, then mints a token with
  LogonUser pinned to the local machine
- ACLs keyed to the principal: denies emitted before allows so carve-outs
  survive, workspace granted read+write, read roots granted read, protected
  metadata denied write and materialized
- removal: revocation by trustee, so retiring a principal drops every ACE naming
  it without needing a record of what was granted

The inversion is the point. A separate account has no access to the caller's
profile at all, so credential stores are unreachable by construction rather than
by enumerating deny rules, and the same SID is what a write grant or a firewall
rule can be keyed to.

Nothing is wired into command execution yet: these paths are additive and no
existing behavior changes. See the pull request for the open question about
where the principal's password lives.
2026-09-11 10:17:22 +05:30
137 changed files with 21527 additions and 176 deletions

No files matched your search

+11 -1
View File
@@ -22,7 +22,7 @@ const permissionProfileScopeNote = "permissionProfile is derived from this proce
func runSandbox(args []string, stdout io.Writer, stderr io.Writer, deps appDeps) int {
if len(args) == 0 {
return writeExecUsageError(stderr, "sandbox subcommand required. Use `zero sandbox policy` or `zero sandbox grants list`.")
return writeExecUsageError(stderr, "sandbox subcommand required. Use `zero sandbox policy`, `zero sandbox exec`, or `zero sandbox grants list`.")
}
switch args[0] {
case "-h", "--help", "help":
@@ -36,6 +36,8 @@ func runSandbox(args []string, stdout io.Writer, stderr io.Writer, deps appDeps)
return runSandboxSetup(args[1:], stdout, stderr, deps)
case "check":
return runSandboxCheck(args[1:], stdout, stderr, deps)
case "exec":
return runSandboxExec(args[1:], stdout, stderr, deps)
case "grants":
return runSandboxGrants(args[1:], stdout, stderr, deps)
default:
@@ -174,10 +176,17 @@ func runSandboxSetup(args []string, stdout io.Writer, stderr io.Writer, deps app
if !setupHelper.Available() {
return writeAppError(stderr, "Windows sandbox setup helper is not available", exitProvider)
}
// Resolved here, in the shell the user typed `zero sandbox setup` into, and
// carried in the args. The helper may be launched elevated, and an elevated
// process does not inherit this shell's environment. Stated explicitly rather
// than left nil (which resolves the same way) because this is the call site
// the opt-in is about.
principalOptIn := zeroSandbox.WindowsSandboxPrincipalOptIn(nil)
setupArgs, err := zeroSandbox.BuildWindowsSandboxSetupArgs(zeroSandbox.WindowsSandboxSetupArgsOptions{
CommandCWD: workspaceRoot,
WorkspaceRoots: []string{workspaceRoot},
PermissionProfile: profile,
PrincipalOptIn: &principalOptIn,
})
if err != nil {
return writeAppError(stderr, err.Error(), exitCrash)
@@ -646,6 +655,7 @@ Commands:
policy Inspect active sandbox policy and platform backend
setup Run native platform sandbox setup
check Evaluate the sandbox decision for a hypothetical tool action
exec Run one command through the real sandbox
grants Manage persistent sandbox grants
`)
+358
View File
@@ -0,0 +1,358 @@
package cli
import (
"context"
"errors"
"fmt"
"io"
"os"
"os/exec"
"strings"
"time"
"github.com/Twigpine/zero/internal/config"
"github.com/Twigpine/zero/internal/execution"
zeroSandbox "github.com/Twigpine/zero/internal/sandbox"
)
// runSandboxExec runs ONE command through the real sandbox and exits with its
// status.
//
// This exists because until now the sandbox could only be exercised through a
// full agent turn with a model in the loop. `zero sandbox policy` reports what
// the posture would be and `zero sandbox check` evaluates a hypothetical
// decision, but nothing actually ran a command and let you look at what
// happened on disk afterwards. The practical result is that enforcement is
// covered almost entirely by tests asserting the shape of an ACL plan, and
// almost not at all by tests asserting a write was refused.
//
// A plan can be perfectly correct and never reach the filesystem. That is not
// hypothetical here: the .git rename guard was emitted correctly by the planner
// and silently skipped by the applier, and four tests covering the plan all
// passed while the ACE was absent from disk. Something that runs the real
// binary and then stats the file is the only thing that catches that class.
//
// Deliberately NOT a debug curiosity: it takes the same path a shell tool
// takes, the engine's decision first and then the engine's command plan, so
// what it proves is what users get. It prints the decision, then the resolved
// backend and enforcement level, to stderr before running, so a harness can
// assert the sandbox was actually engaged rather than quietly downgraded.
func runSandboxExec(args []string, stdout io.Writer, stderr io.Writer, deps appDeps) int {
command, err := parseSandboxExecArgs(args)
if err != nil {
if errors.Is(err, errSandboxExecHelp) {
if writeErr := writeSandboxExecHelp(stdout); writeErr != nil {
return exitCrash
}
return exitSuccess
}
return writeExecUsageError(stderr, err.Error())
}
workspaceRoot, err := resolveWorkspaceRoot("", deps)
if err != nil {
return writeExecUsageError(stderr, err.Error())
}
resolved, err := deps.resolveConfig(workspaceRoot, config.Overrides{})
if err != nil {
return writeAppError(stderr, err.Error(), exitProvider)
}
policy := applyConfiguredSandboxPolicy(zeroSandbox.DefaultPolicy(), resolved.Sandbox)
scope, err := zeroSandbox.NewScope(workspaceRoot, resolved.Sandbox.AdditionalWriteRoots)
if err != nil {
return writeAppError(stderr, fmt.Sprintf("resolve sandbox write roots: %v", err), exitCrash)
}
// Through the ENGINE, not a SandboxManager built here.
//
// The engine is what a real tool call goes through, and it does more than
// hand the manager a request: it resolves the permission profile, calls
// prepareSandboxRuntime, and folds the runtime state into that profile
// before planning. Building a manager directly skipped all of it, so the
// command ran without the runtime write root, and cache or temp writes could
// pass or fail differently from the sandboxed command this exists to imitate.
// A harness that exercises the wrong path is worse than no harness, because
// its result still reads as evidence.
engine := zeroSandbox.NewEngine(zeroSandbox.EngineOptions{
WorkspaceRoot: workspaceRoot,
Policy: policy,
Scope: scope,
Backend: deps.selectSandboxBackend(zeroSandbox.BackendOptions{}),
// The same scrub list a real tool call gets. Without it the engine keeps an
// empty set, and only the hardcoded names plus the provider catalog's own
// AuthEnvVars are removed from the child's environment: a key named by
// `apiKeyEnv` in the user's config would be scrubbed for every sandboxed
// tool call and handed to this one. Reproducing the production environment
// is the entire point of the command, and a credential is the last part of
// it that may differ.
SensitiveEnvKeys: providerSensitiveEnvKeys(resolved),
})
// The CLI's shared shutdown context, so Ctrl+C and a directed SIGTERM both
// arrive here rather than only at whatever the terminal happens to signal.
runCtx, stopSignals := signalContext()
defer stopSignals()
// THE DECISION COMES BEFORE THE PLAN, as it does for every real tool call.
//
// A shell tool is evaluated by the engine and only then planned
// (tools.Registry.RunWithOptions). This went straight to BuildCommandPlan, so
// it took "the same path a shell tool takes" only from the second step on, and
// every refusal that lives in Evaluate did not exist here. The one that
// matters most is the nested-repository guard: a workspace governed by an
// ancestor repository carries NO git carveouts, on the strength of that guard
// refusing to create a repository there, and `zero sandbox exec -- git init`
// created one under the plain workspace grant with a writable config and
// hooks. A harness that runs what production would have refused does not
// prove what users get. Reported by @jatmn.
//
// PermissionGranted is true because the person at the terminal typed the
// command, which is the approval a prompt asks a session user for. It lifts
// exactly what an approval lifts in a session and nothing else: a denial is
// still a denial, and an approved network command still runs inside a sandbox
// that has the network off.
decision := sandboxExecDecision(runCtx, engine, workspaceRoot, command)
fmt.Fprintf(stderr, "sandbox: decision=%s reason=%s\n", decision.Action, decision.Reason)
if decision.Action == zeroSandbox.ActionDeny {
return writeAppError(stderr, decision.ErrorString(), exitCrash)
}
plan, err := engine.BuildCommandPlan(zeroSandbox.CommandSpec{
Name: command[0],
Args: command[1:],
Dir: workspaceRoot,
Env: os.Environ(),
})
if err != nil {
return writeAppError(stderr, fmt.Sprintf("build sandbox command plan: %v", err), exitCrash)
}
// The plan owns resources beyond its construction: on Linux it allocates a
// policy-report file and registers the removal here, so without this every
// invocation leaves a /tmp/zero-sandbox-report-* behind.
defer plan.Cleanup()
// Printed before the command runs and on stderr, so it survives a command
// that writes to stdout and stays greppable by a test harness. A downgrade
// is reported loudly for the same reason: a smoke test that passes because
// the sandbox quietly stood down is worse than no smoke test.
fmt.Fprintf(stderr, "sandbox: backend=%s enforcement=%s wrapped=%t workspace=%s\n",
plan.Backend.Name, plan.EnforcementLevel, plan.Wrapped, plan.WorkspaceRoot)
if strings.TrimSpace(plan.DowngradeReason) != "" {
fmt.Fprintf(stderr, "sandbox: DOWNGRADED: %s\n", plan.DowngradeReason)
}
return runSandboxPlannedCommand(runCtx, plan, stdout, stderr)
}
// sandboxExecToolName is the tool a session would have run this command with.
// Grants and the engine's shell rules are keyed by it.
const sandboxExecToolName = "bash"
// sandboxExecDecision asks the engine the question a session asks before it
// plans a shell command, for the argv this invocation was given.
func sandboxExecDecision(ctx context.Context, engine *zeroSandbox.Engine, workspaceRoot string, argv []string) zeroSandbox.Decision {
return engine.Evaluate(ctx, zeroSandbox.Request{
WorkspaceRoot: workspaceRoot,
ToolName: sandboxExecToolName,
SideEffect: zeroSandbox.SideEffectShell,
PermissionGranted: true,
PermissionMode: zeroSandbox.PermissionModeAsk,
Args: map[string]any{"command": sandboxExecCommandText(argv)},
Reason: "zero sandbox exec",
})
}
// sandboxExecCommandText renders argv as the command text the engine analyses.
//
// The engine classifies a shell tool by parsing its command string, so argv has
// to become one without changing what it says. A word made only of characters
// the shell does not interpret is left bare, which keeps `git init` reading as a
// session would have written it. Anything else is single-quoted, so an argument
// such as "git init" stays ONE word and is not mistaken for a command, and a
// payload handed to `sh -c` reaches the analyser as the payload it is.
func sandboxExecCommandText(argv []string) string {
words := make([]string, 0, len(argv))
for _, word := range argv {
words = append(words, sandboxExecQuoteWord(word))
}
return strings.Join(words, " ")
}
func sandboxExecQuoteWord(word string) string {
if word == "" {
return "''"
}
bare := true
for _, r := range word {
switch {
case r >= 'a' && r <= 'z', r >= 'A' && r <= 'Z', r >= '0' && r <= '9':
case strings.ContainsRune("_@%+=:,./-", r):
default:
bare = false
}
}
if bare {
return word
}
// A single quote cannot appear inside single quotes, so it closes them, is
// written escaped, and opens them again.
return "'" + strings.ReplaceAll(word, "'", `'\''`) + "'"
}
const (
// sandboxExecShutdownGrace is how long a cancelled child has to exit on its
// own after the graceful request, before it is killed outright.
sandboxExecShutdownGrace = 5 * time.Second
// sandboxExecShutdownPoll is how often that wait re-checks, matching the
// background package's termination policy.
sandboxExecShutdownPoll = 50 * time.Millisecond
)
func runSandboxPlannedCommand(ctx context.Context, plan zeroSandbox.CommandPlan, stdout io.Writer, stderr io.Writer) int {
// CANCELLING THE WRAPPER HAS TO REACH THE COMMAND.
//
// This started the backend wrapper with a bare exec.Command().Run(): no
// context, no forwarding, no shutdown path. A terminal masks it, because
// terminals signal the whole foreground process group, but a supervisor or
// task runner that sends SIGTERM to the zero sandbox exec PID killed only
// Zero. The wrapper and everything under it kept running, doing filesystem
// and network work after the caller considered the task cancelled, and the
// deferred plan cleanup never ran because the process was gone.
//
// DELIBERATELY NOT execution.ConfigureProcessGroup. Putting the child in its
// own process group closes this hole and opens a worse one: it severs every
// kernel-delivered group signal, so a supervisor escalating to a group kill,
// and a terminal delivering Ctrl+C to its foreground group, would stop
// reaching the child. That trades a path that works today for one that does
// not. Keeping the child in Zero's group leaves group delivery unchanged,
// while the directed-signal case, which reached nothing at all before, now
// reaches the child.
process := exec.CommandContext(ctx, plan.Name, plan.Args...)
// TWO PHASES, AND THE FIRST ONE HAS TO EXIST.
//
// The comments here used to describe a graceful signal followed by escalation
// while the code did neither: Cancel called KillProcessTree, which is SIGKILL
// on Unix and taskkill /T /F on Windows, and WaitDelay only starts counting
// AFTER Cancel returns, so it could never postpone a kill that had already
// happened. A directed SIGTERM reached the child as 137 rather than 143, with
// no chance to flush output, drop a lock file, or run a shutdown handler.
//
// TerminateProcessTree is the two-phase policy the background package already
// uses: SIGTERM, poll for the grace, then SIGKILL what is still alive. On
// Windows it is the single-phase kill, which is correct rather than lazy,
// because there is no signal to send a child that owns no console.
process.Cancel = func() error {
return execution.TerminateProcessTree(process.Process.Pid, sandboxExecShutdownGrace, sandboxExecShutdownPoll)
}
// A backstop only. Cancel above already waits out the grace and escalates, so
// this bounds the case where the tree is gone but Wait is still blocked on an
// inherited pipe a grandchild holds open.
process.WaitDelay = sandboxExecShutdownGrace + sandboxExecShutdownPoll
process.Dir = plan.Dir
if process.Dir == "" {
process.Dir = plan.WorkspaceRoot
}
// SPECIFIED-EMPTY IS NOT UNSPECIFIED.
//
// exec.Cmd treats a nil Env as "inherit this process's entire environment",
// which is a different statement from "run with no variables". The plan owns
// its environment: directCommandEnv and scrubSensitiveEnv return a slice they
// built, and that slice is non-nil with length zero when every entry was
// sensitive. Testing length collapsed those two states and turned the strictest
// possible answer into the loosest one.
//
// Not reachable through `zero sandbox exec` today, because the child
// environment is os.Environ() and an environment holding only sensitive keys
// has no %AppData%, so config resolution fails before the planner runs. Fixed
// anyway: the guard is one assignment, and the next caller that hands the plan
// a deliberately narrow environment would inherit everything instead, silently.
if plan.Env != nil {
process.Env = plan.Env
}
process.Stdin = os.Stdin
process.Stdout = stdout
process.Stderr = stderr
if err := process.Run(); err != nil {
var exitErr *exec.ExitError
if errors.As(err, &exitErr) {
// The command's own status, not ours. A harness asserting "the write
// was refused" needs the refusal's exit code, not a wrapper's.
// A SIGNALED CHILD HAS NO EXIT CODE TO REPORT. ExitCode() answers -1
// there, and os.Exit truncates that to 255, so a child that took SIGTERM
// became indistinguishable from one that chose to exit 255. Fold the
// signal into the conventional 128+n a shell would report, which needs
// the ProcessState rather than the integer.
if status, signaled := signaledExitStatus(exitErr.ProcessState); signaled {
return status
}
return exitErr.ExitCode()
}
fmt.Fprintf(stderr, "sandbox exec: %v\n", err)
return exitCrash
}
return exitSuccess
}
var errSandboxExecHelp = errors.New("help requested")
// parseSandboxExecArgs takes everything after `--` as the command, so the
// command's own flags are never mistaken for ours.
func parseSandboxExecArgs(args []string) ([]string, error) {
if len(args) == 0 {
return nil, errors.New("usage: zero sandbox exec -- <command> [args...]")
}
// Only the FIRST token is ours to interpret. Everything from the second
// onwards belongs to the child, help flags included.
//
// Written as a straight-line decision on args[0] rather than a loop, because
// a loop here is a lie. An earlier version scanned for `--` "up front" and
// said so in its comment, but every branch of its body returned, so it only
// ever examined index 0 and the promised scan did not exist. The rule below
// is what that code actually implemented, and it is the rule we want: it is
// the wrapper's own prefix that can ask for the wrapper's help, and the
// prefix is at most one token long.
switch args[0] {
case "--":
// Everything after the separator is the command, verbatim, including
// `--help`. That is the documented contract: `zero sandbox exec -- cmd
// --help` must run cmd's help, not ours.
command := args[1:]
if len(command) == 0 {
return nil, errors.New("usage: zero sandbox exec -- <command> [args...]")
}
return command, nil
case "-h", "--help", "help":
return nil, errSandboxExecHelp
}
// The separator-less form, tolerated for interactive use: the first token is
// the command, so nothing after it is ours to read. Without this,
// `zero sandbox exec mycmd --help` printed OUR help and never ran mycmd,
// which is the same contract break as reading past `--`. The help text still
// shows the separator, because anything with a leading dash needs it.
return args, nil
}
func writeSandboxExecHelp(w io.Writer) error {
_, err := fmt.Fprint(w, `Usage:
zero sandbox exec -- <command> [args...]
Runs one command through the real sandbox and exits with its status.
Everything after the -- separator is the command, so its own flags are not
parsed as Zero's. The command is evaluated the way a session evaluates a shell
tool call before anything is planned: the decision is written to stderr, and a
command a session refuses is refused here too, with the same reason. Running it
from a terminal counts as the approval a session would prompt for, and lifts
only what that approval lifts. The resolved backend and enforcement level are
then written to stderr before the command runs, and a downgrade is reported
there explicitly.
Examples:
zero sandbox exec -- cmd /c echo hello
zero sandbox exec -- powershell -Command "Set-Content out.txt x"
`)
return err
}
+78
View File
@@ -0,0 +1,78 @@
package cli
import (
"context"
"io"
"os"
"runtime"
"testing"
"time"
zeroSandbox "github.com/Twigpine/zero/internal/sandbox"
)
// longLivedPlan returns a plan whose child outlives the test unless something
// terminates it.
func longLivedPlan(t *testing.T) zeroSandbox.CommandPlan {
t.Helper()
plan := zeroSandbox.CommandPlan{Dir: t.TempDir()}
if runtime.GOOS == "windows" {
plan.Name = "cmd.exe"
plan.Args = []string{"/c", "ping -n 120 127.0.0.1 >NUL"}
return plan
}
plan.Name = "/bin/sh"
plan.Args = []string{"-c", "sleep 120"}
return plan
}
// CANCELLING THE WRAPPER HAS TO REACH THE COMMAND.
//
// The sandboxed command was started with a bare exec.Command().Run(): no
// context, no forwarding, no shutdown path. A terminal masks that, because it
// signals the whole foreground process group, but a supervisor or task runner
// that sends SIGTERM to the wrapper's PID killed only Zero. The command kept
// running, doing filesystem and network work after the caller considered the
// task cancelled, and the deferred plan cleanup never ran.
//
// Driven with a real long-lived child and a real cancellation, asserting that
// the call actually returns rather than that a field is set.
func TestCancellingTheWrapperTerminatesTheSandboxedCommand(t *testing.T) {
ctx, cancel := context.WithCancel(context.Background())
done := make(chan int, 1)
go func() {
done <- runSandboxPlannedCommand(ctx, longLivedPlan(t), io.Discard, io.Discard)
}()
// Let the child actually start, or cancelling proves nothing.
time.Sleep(300 * time.Millisecond)
select {
case <-done:
t.Fatal("SETUP INVALID: the child exited on its own, so cancellation was not exercised")
default:
}
cancel()
select {
case <-done:
case <-time.After(sandboxExecShutdownGrace + 10*time.Second):
t.Fatal("cancelling the wrapper did not terminate the sandboxed command; it would keep running after the caller gave up")
}
}
// And an uncancelled command still runs to completion and reports its own
// status, or the fix above would be "kill everything immediately".
func TestAnUncancelledSandboxedCommandStillReportsItsStatus(t *testing.T) {
plan := zeroSandbox.CommandPlan{Dir: t.TempDir()}
if runtime.GOOS == "windows" {
plan.Name = "cmd.exe"
plan.Args = []string{"/c", "exit 3"}
} else {
plan.Name = "/bin/sh"
plan.Args = []string{"-c", "exit 3"}
}
if code := runSandboxPlannedCommand(context.Background(), plan, io.Discard, os.Stderr); code != 3 {
t.Fatalf("exit code = %d, want the child's own 3", code)
}
}
+162
View File
@@ -0,0 +1,162 @@
package cli
import (
"bytes"
"context"
"os"
"path/filepath"
"strings"
"testing"
"github.com/Twigpine/zero/internal/config"
"github.com/Twigpine/zero/internal/sandbox"
)
// governedNestedWorkspace is a workspace inside somebody else's repository: an
// ancestor carries .git and the workspace itself does not. Setup plans no git
// carveouts for it, which is why a repository must not be created there.
func governedNestedWorkspace(t *testing.T) (ancestor, workspace string) {
t.Helper()
ancestor = t.TempDir()
if err := os.MkdirAll(filepath.Join(ancestor, ".git"), 0o700); err != nil {
t.Fatal(err)
}
workspace = filepath.Join(ancestor, "packages", "app")
if err := os.MkdirAll(filepath.Join(workspace, "sub dir"), 0o700); err != nil {
t.Fatal(err)
}
return ancestor, workspace
}
func sandboxExecTestDeps(workspace string) appDeps {
return appDeps{
getwd: func() (string, error) { return workspace, nil },
resolveConfig: func(string, config.Overrides) (config.ResolvedConfig, error) {
return config.ResolvedConfig{}, nil
},
// No native runner. A command that got past the decision would run
// unwrapped, which is exactly what makes a missing refusal visible on
// disk instead of only in a return value.
selectSandboxBackend: func(sandbox.BackendOptions) sandbox.Backend {
return sandbox.Backend{Name: sandbox.BackendUnavailable, Fallback: true, Message: "no native sandbox in this test"}
},
}
}
// `zero sandbox exec` REFUSES WHAT A SESSION WOULD REFUSE.
//
// The command is documented as taking the path a shell tool takes. A shell tool
// is evaluated by the engine and then planned; this went straight to the plan,
// so nothing that lives in Evaluate applied. In a workspace governed by an
// ancestor repository that is the nested-repository guard, and that guard is the
// only thing standing in for the git carveouts setup deliberately does not plan
// there. `zero sandbox exec -- git init` created the repository, writable config
// and hooks included.
//
// Driven through the real CLI entry point, with a backend that would run the
// command unwrapped if it were let through, and checked on disk: the refusal has
// to come with the reason an operator can act on, and no repository may exist
// afterwards. Reported by @jatmn.
func TestSandboxExecRefusesToCreateARepositoryInAGovernedWorkspace(t *testing.T) {
for _, testCase := range []struct {
name string
argv []string
made []string
}{
{name: "git init", argv: []string{"git", "init"}, made: []string{".git"}},
{name: "git init behind -C and a quoted directory", argv: []string{"git", "-C", "sub dir", "init"}, made: []string{"sub dir/.git"}},
{name: "git init behind a shell launcher", argv: []string{"sh", "-c", "git init"}, made: []string{".git"}},
{name: "git init behind env", argv: []string{"env", "GIT_TRACE=0", "git", "init"}, made: []string{".git"}},
{name: "git clone", argv: []string{"git", "clone", "https://example.invalid/repo.git", "vendored"}, made: []string{"vendored"}},
} {
t.Run(testCase.name, func(t *testing.T) {
_, workspace := governedNestedWorkspace(t)
var stdout, stderr bytes.Buffer
args := append([]string{"sandbox", "exec", "--"}, testCase.argv...)
exitCode := runWithDeps(args, &stdout, &stderr, sandboxExecTestDeps(workspace))
for _, made := range testCase.made {
if _, err := os.Lstat(filepath.Join(workspace, filepath.FromSlash(made))); err == nil {
t.Errorf("%s exists after the command: the repository was created under the plain workspace grant", made)
}
}
if exitCode == exitSuccess {
t.Errorf("exit = %d for a command a session refuses; stderr:\n%s", exitCode, stderr.String())
}
if !strings.Contains(stderr.String(), "decision=deny") {
t.Errorf("stderr does not report the decision:\n%s", stderr.String())
}
if !strings.Contains(stderr.String(), "sits inside an existing git repository") {
t.Errorf("the refusal does not carry the nested-repository reason and its remedy:\n%s", stderr.String())
}
if strings.Contains(stderr.String(), "backend=") {
t.Errorf("a command plan was built for a refused command:\n%s", stderr.String())
}
})
}
}
// The decision is the engine's, asked the way a session asks it. These are the
// controls: what must NOT be refused, so the gate above is not simply refusing
// git, or refusing this workspace.
func TestSandboxExecDecisionLeavesOrdinaryCommandsAlone(t *testing.T) {
_, governed := governedNestedWorkspace(t)
standalone := t.TempDir()
for _, testCase := range []struct {
name string
workspace string
argv []string
}{
{name: "an ordinary git command in the governed workspace", workspace: governed, argv: []string{"git", "status"}},
{name: "the words git init as one argument", workspace: governed, argv: []string{"echo", "git init"}},
{name: "git init in a workspace nobody governs", workspace: standalone, argv: []string{"git", "init"}},
} {
t.Run(testCase.name, func(t *testing.T) {
engine := sandbox.NewEngine(sandbox.EngineOptions{
WorkspaceRoot: testCase.workspace,
Policy: sandbox.DefaultPolicy(),
Backend: sandbox.Backend{Name: sandbox.BackendUnavailable, Fallback: true},
})
decision := sandboxExecDecision(context.Background(), engine, testCase.workspace, testCase.argv)
if decision.Action == sandbox.ActionDeny {
t.Fatalf("%q was refused: %s", strings.Join(testCase.argv, " "), decision.ErrorString())
}
})
}
}
// ARGV BECOMES COMMAND TEXT WITHOUT CHANGING WHAT IT SAYS. The engine classifies
// a shell command by parsing its text, so the rendering decides what the
// classifier sees. One argument has to stay one word, and a payload handed to a
// shell launcher has to arrive as that payload.
func TestSandboxExecCommandTextKeepsArgvIntact(t *testing.T) {
for _, testCase := range []struct {
name string
argv []string
want string
gitInit bool
}{
{name: "bare words stay bare", argv: []string{"git", "init"}, want: "git init", gitInit: true},
{name: "a spaced argument is one word", argv: []string{"echo", "git init"}, want: "echo 'git init'"},
{name: "a launcher payload is analysed as a payload", argv: []string{"sh", "-c", "git init"}, want: "sh -c 'git init'", gitInit: true},
{name: "a quote inside an argument", argv: []string{"printf", "it's"}, want: `printf 'it'\''s'`},
{name: "substitution syntax is inert", argv: []string{"echo", "$(git init)"}, want: "echo '$(git init)'"},
{name: "an empty argument survives", argv: []string{"printf", ""}, want: "printf ''"},
{name: "a directory with a space", argv: []string{"git", "-C", "sub dir", "init"}, want: "git -C 'sub dir' init", gitInit: true},
} {
t.Run(testCase.name, func(t *testing.T) {
text := sandboxExecCommandText(testCase.argv)
if text != testCase.want {
t.Fatalf("command text = %q, want %q", text, testCase.want)
}
analysis := sandbox.AnalyzeCommand(text)
if analysis.TooComplex {
t.Fatalf("%q does not parse, so the classifier would treat a plain argv as obfuscated", text)
}
if analysis.GitInit != testCase.gitInit {
t.Errorf("%q: GitInit = %v, want %v", text, analysis.GitInit, testCase.gitInit)
}
})
}
}
+72
View File
@@ -0,0 +1,72 @@
package cli
import (
"context"
"os"
"runtime"
"strings"
"testing"
zeroSandbox "github.com/Twigpine/zero/internal/sandbox"
)
// envPrinterPlan returns a plan whose child prints its own environment, so the
// assertion is about what the child received rather than about a field value.
func envPrinterPlan(t *testing.T, env []string) zeroSandbox.CommandPlan {
t.Helper()
plan := zeroSandbox.CommandPlan{Dir: t.TempDir(), Env: env}
if runtime.GOOS == "windows" {
plan.Name = "cmd.exe"
plan.Args = []string{"/c", "set"}
return plan
}
plan.Name = "/bin/sh"
plan.Args = []string{"-c", "env"}
return plan
}
// A PLAN THAT SPECIFIES NO VARIABLES MUST NOT INHERIT EVERY VARIABLE.
//
// exec.Cmd reads a nil Env as "inherit this process's entire environment", which
// is a different statement from "run with no variables". The plan owns its
// environment: directCommandEnv and scrubSensitiveEnv return a slice they built,
// and that slice is non-nil with length zero when every entry was sensitive.
// Testing its length collapsed the two states and turned the strictest possible
// answer into the loosest one.
//
// Not reachable through `zero sandbox exec` today, because the child environment
// is os.Environ() and an environment holding only sensitive keys has no
// %AppData%, so config resolution fails before the planner runs. Pinned anyway,
// because the next caller that hands the plan a deliberately narrow environment
// would silently inherit everything instead.
func TestAnEmptyPlannedEnvironmentDoesNotInherit(t *testing.T) {
const marker = "ZZ_SANDBOX_ENV_MARKER"
t.Setenv(marker, "leaked-value")
var out strings.Builder
// Specified, and deliberately empty.
code := runSandboxPlannedCommand(context.Background(), envPrinterPlan(t, []string{}), &out, os.Stderr)
if code != 0 {
t.Fatalf("child exited %d: %s", code, out.String())
}
if strings.Contains(out.String(), marker) {
t.Fatalf("a plan specifying no environment leaked the caller's %s to the child:\n%s", marker, out.String())
}
}
// And a nil environment still inherits, which is the meaning the planner relies
// on when it did not build one. Without this the fix above could be "never pass
// the environment", which would break every ordinary command.
func TestANilPlannedEnvironmentStillInherits(t *testing.T) {
const marker = "ZZ_SANDBOX_ENV_MARKER"
t.Setenv(marker, "inherited-value")
var out strings.Builder
code := runSandboxPlannedCommand(context.Background(), envPrinterPlan(t, nil), &out, os.Stderr)
if code != 0 {
t.Fatalf("child exited %d: %s", code, out.String())
}
if !strings.Contains(out.String(), marker) {
t.Fatalf("a nil planned environment stopped inheriting, which changes the meaning the planner relies on:\n%s", out.String())
}
}
@@ -0,0 +1,187 @@
//go:build !windows
package cli
import (
"context"
"io"
"os"
"path/filepath"
"strconv"
"strings"
"syscall"
"testing"
"time"
zeroSandbox "github.com/Twigpine/zero/internal/sandbox"
)
// THE GRACEFUL PHASE HAS TO ACTUALLY HAPPEN.
//
// The shutdown comments described a graceful signal followed by escalation while
// the code did neither: Cancel called KillProcessTree, which is SIGKILL here, and
// WaitDelay only starts counting after Cancel returns so it could never postpone
// a kill that had already happened. A directed SIGTERM therefore reached the
// child as 137 rather than 143, with no chance to flush output, drop a lock file,
// or run a shutdown handler.
//
// Driven with a child that traps the signal and records that its handler ran, so
// the assertion is about the observed lifecycle rather than about a configured
// duration.
func TestACancelledCommandGetsAChanceToCleanUp(t *testing.T) {
marker := filepath.Join(t.TempDir(), "cleanup-ran")
// Exits 42 on the graceful signal: a distinctive code the child could only
// have chosen itself, so the status proves the handler ran rather than that
// something plausible happened.
script := "trap 'echo yes > " + marker + "; exit 42' TERM; while :; do sleep 0.05; done"
ctx, cancel := context.WithCancel(context.Background())
done := make(chan int, 1)
go func() {
done <- runSandboxPlannedCommand(ctx, zeroSandbox.CommandPlan{
Name: "/bin/sh",
Args: []string{"-c", script},
Dir: t.TempDir(),
}, io.Discard, io.Discard)
}()
// The trap has to be installed before the signal, or this proves nothing.
time.Sleep(500 * time.Millisecond)
select {
case <-done:
t.Fatal("SETUP INVALID: the child exited on its own")
default:
}
cancel()
var status int
select {
case status = <-done:
case <-time.After(sandboxExecShutdownGrace + 10*time.Second):
t.Fatal("the cancelled command never terminated")
}
// The status the caller sees is the child's own, so a harness can tell an
// orderly shutdown from a kill.
if status != 42 {
t.Errorf("status = %d, want 42; the child chose that code in its TERM handler, so anything else means it never got to finish", status)
}
if _, err := os.Stat(marker); err != nil {
t.Fatalf("the child was killed outright instead of being asked to stop, so its cleanup handler never ran: %v", err)
}
}
// And a child that ignores the request is still force-killed, after the bound
// rather than before it. Without this the fix could be "only ever ask nicely".
func TestAStubbornCancelledCommandIsStillKilled(t *testing.T) {
// Traps TERM and keeps running: only escalation can end this.
script := "trap '' TERM; while :; do sleep 0.05; done"
ctx, cancel := context.WithCancel(context.Background())
done := make(chan int, 1)
go func() {
done <- runSandboxPlannedCommand(ctx, zeroSandbox.CommandPlan{
Name: "/bin/sh",
Args: []string{"-c", script},
Dir: t.TempDir(),
}, io.Discard, io.Discard)
}()
time.Sleep(500 * time.Millisecond)
started := time.Now()
cancel()
var status int
select {
case status = <-done:
case <-time.After(sandboxExecShutdownGrace + 15*time.Second):
t.Fatal("a child ignoring the graceful request was never force-killed")
}
// After the bound, not before: a kill that lands immediately is the defect
// this replaced.
if elapsed := time.Since(started); elapsed < sandboxExecShutdownGrace {
t.Fatalf("the child was killed after %s, before the %s grace it was owed", elapsed, sandboxExecShutdownGrace)
}
// And escalation really was a kill, so "ask nicely and give up" cannot pass.
if want := 128 + int(syscall.SIGKILL); status != want {
t.Errorf("status = %d, want %d after escalation", status, want)
}
}
// AND THE STATUS HAS TO SAY WHICH SIGNAL ARRIVED.
//
// 137 rather than 143 was the reported symptom, and it is the only part of this
// a caller can see. A child that does not trap anything must come back as
// 128+SIGTERM: if the first signal were still SIGKILL, this would be 137 and the
// two cases above would both still pass, since one traps and the other ignores.
func TestACancelledCommandReportsTheGracefulSignal(t *testing.T) {
ctx, cancel := context.WithCancel(context.Background())
done := make(chan int, 1)
go func() {
done <- runSandboxPlannedCommand(ctx, zeroSandbox.CommandPlan{
Name: "/bin/sh",
Args: []string{"-c", "while :; do sleep 0.05; done"},
Dir: t.TempDir(),
}, io.Discard, io.Discard)
}()
time.Sleep(500 * time.Millisecond)
cancel()
var status int
select {
case status = <-done:
case <-time.After(sandboxExecShutdownGrace + 10*time.Second):
t.Fatal("the cancelled command never terminated")
}
if want := 128 + int(syscall.SIGTERM); status != want {
t.Fatalf("status = %d, want %d; %d means the child was SIGKILLed with no graceful phase", status, want, 128+int(syscall.SIGKILL))
}
}
// TERMINATION IS COMPLETE BEFORE THE FUNCTION RETURNS.
//
// `zero sandbox exec` releases the plan with a defer around this call, so plan
// cleanup is ordered after termination only if nothing survives the return. A
// future refactor that lets Wait come back while the tree is still up would move
// cleanup on top of a live child, deleting the policy-report file it is using.
//
// The stubborn child is the one that can outlive the call, since it ignores the
// graceful request and only escalation ends it.
func TestACancelledCommandIsFullyReapedBeforeCleanupCouldRun(t *testing.T) {
pidFile := filepath.Join(t.TempDir(), "child.pid")
script := "echo $$ > " + pidFile + "; trap '' TERM; while :; do sleep 0.05; done"
ctx, cancel := context.WithCancel(context.Background())
done := make(chan int, 1)
go func() {
done <- runSandboxPlannedCommand(ctx, zeroSandbox.CommandPlan{
Name: "/bin/sh",
Args: []string{"-c", script},
Dir: t.TempDir(),
}, io.Discard, io.Discard)
}()
time.Sleep(500 * time.Millisecond)
raw, err := os.ReadFile(pidFile)
if err != nil {
t.Fatalf("SETUP INVALID: the child never recorded its pid, so there is nothing to check for survival: %v", err)
}
pid, err := strconv.Atoi(strings.TrimSpace(string(raw)))
if err != nil || pid <= 0 {
t.Fatalf("SETUP INVALID: unusable child pid %q: %v", raw, err)
}
cancel()
select {
case <-done:
case <-time.After(sandboxExecShutdownGrace + 15*time.Second):
t.Fatal("a child ignoring the graceful request was never force-killed")
}
// Signal 0 is the existence probe: no signal is sent, only the permission and
// liveness checks run, so ESRCH is the answer for a reaped process.
if err := syscall.Kill(pid, 0); err == nil {
t.Fatalf("the child (pid %d) was still alive when the run returned; plan cleanup is deferred around this call and would delete the policy-report file underneath it", pid)
} else if err != syscall.ESRCH {
t.Skipf("cannot probe pid %d here: %v", pid, err)
}
}
+28
View File
@@ -0,0 +1,28 @@
//go:build !windows
package cli
import (
"os"
"syscall"
)
// signaledExitStatus reports the conventional shell status for a child that was
// terminated by a signal, which exec.ExitError cannot represent.
//
// ExitCode() returns -1 for a signaled child, and the top level hands that to
// os.Exit, which truncates it to 255. A child that takes SIGTERM is then
// indistinguishable from one that exited 255 of its own accord, which breaks the
// documented status contract for a command whose whole job is to report the
// child's own status faithfully. 128+signal is what a shell reports and what a
// harness comparing statuses expects.
func signaledExitStatus(state *os.ProcessState) (int, bool) {
if state == nil {
return 0, false
}
status, ok := state.Sys().(syscall.WaitStatus)
if !ok || !status.Signaled() {
return 0, false
}
return 128 + int(status.Signal()), true
}
@@ -0,0 +1,65 @@
//go:build !windows
package cli
import (
"errors"
"os/exec"
"syscall"
"testing"
)
// A SIGNALED CHILD MUST NOT LOOK LIKE ONE THAT CHOSE TO EXIT 255.
//
// `sandbox exec` exists to report the child's own status faithfully, and
// exec.ExitError cannot represent signal termination: ExitCode() answers -1, and
// the top level hands that to os.Exit, which truncates it to 255. So a child
// killed by SIGTERM was indistinguishable from an ordinary exit of 255, and a
// harness comparing statuses could not tell a refusal from a kill.
//
// Driven with a real subprocess and a real signal rather than a synthetic
// WaitStatus, because the mapping is only correct if the OS agrees with it.
func TestSignaledChildReportsTheConventionalStatus(t *testing.T) {
for _, testCase := range []struct {
name string
script string
want int
}{
{name: "SIGTERM", script: "kill -TERM $$; sleep 5", want: 128 + int(syscall.SIGTERM)},
{name: "SIGINT", script: "kill -INT $$; sleep 5", want: 128 + int(syscall.SIGINT)},
} {
t.Run(testCase.name, func(t *testing.T) {
err := exec.Command("/bin/sh", "-c", testCase.script).Run()
var exitErr *exec.ExitError
if !errors.As(err, &exitErr) {
t.Fatalf("SETUP INVALID: the child did not end with an ExitError: %v", err)
}
// The behaviour being corrected: the integer alone cannot say this.
if code := exitErr.ExitCode(); code != -1 {
t.Fatalf("SETUP INVALID: a signaled child reported exit code %d, expected -1 on this platform", code)
}
status, signaled := signaledExitStatus(exitErr.ProcessState)
if !signaled {
t.Fatal("a signaled child was not recognised as signaled, so it would be reported as exit 255")
}
if status != testCase.want {
t.Fatalf("status = %d, want %d (128 + signal), which is what a shell reports", status, testCase.want)
}
})
}
}
// An ordinary non-zero exit is untouched: it has a real code and must keep it.
func TestOrdinaryExitIsNotTreatedAsSignaled(t *testing.T) {
err := exec.Command("/bin/sh", "-c", "exit 3").Run()
var exitErr *exec.ExitError
if !errors.As(err, &exitErr) {
t.Fatalf("SETUP INVALID: the child did not end with an ExitError: %v", err)
}
if _, signaled := signaledExitStatus(exitErr.ProcessState); signaled {
t.Fatal("an ordinary exit was reported as signaled, which would rewrite its status")
}
if code := exitErr.ExitCode(); code != 3 {
t.Fatalf("exit code = %d, want the child's own 3", code)
}
}
@@ -0,0 +1,12 @@
//go:build windows
package cli
import "os"
// signaledExitStatus has no Windows counterpart: a process there ends with an
// exit code, and there is no signal to fold into one. Windows keeps the exit
// code exec.ExitError already reports.
func signaledExitStatus(*os.ProcessState) (int, bool) {
return 0, false
}
+108
View File
@@ -0,0 +1,108 @@
package cli
import (
"errors"
"strings"
"testing"
)
// parseSandboxExecArgs sits on the boundary between Zero's flags and a child
// command's, and it had no tests at all: not for the reported defect, not even
// for the happy case. The contract it has to keep is that everything after the
// separator belongs to the child, help flags included, so the wrapper can never
// answer for a command it was supposed to be running.
func TestParseSandboxExecArgs(t *testing.T) {
for _, testCase := range []struct {
name string
args []string
command []string
help bool
usage bool
}{
{
// The reported defect: --help after the separator is the CHILD's.
name: "help after the separator belongs to the child",
args: []string{"--", "cmd", "--help"},
command: []string{"cmd", "--help"},
},
{
name: "a second separator is the child's too",
args: []string{"--", "cmd", "--", "inner"},
command: []string{"cmd", "--", "inner"},
},
{
name: "a flag-looking command survives the separator",
args: []string{"--", "--weird-binary"},
command: []string{"--weird-binary"},
},
{
// The separator-less form. The first token is the command, so its own
// flags are not ours to read either.
name: "help after a separatorless command belongs to the child",
args: []string{"cmd", "--help"},
command: []string{"cmd", "--help"},
},
{
// A separator arriving AFTER the command has already started is part of
// the child's argv, not a delimiter we get a second go at.
name: "a separator after the command is the child's argument",
args: []string{"ls", "--", "foo"},
command: []string{"ls", "--", "foo"},
},
{name: "bare help", args: []string{"--help"}, help: true},
{name: "short help", args: []string{"-h"}, help: true},
{name: "help subcommand", args: []string{"help"}, help: true},
{name: "help in the prefix wins", args: []string{"--help", "--", "cmd"}, help: true},
{name: "no arguments", args: nil, usage: true},
{name: "separator with nothing after it", args: []string{"--"}, usage: true},
} {
t.Run(testCase.name, func(t *testing.T) {
command, err := parseSandboxExecArgs(testCase.args)
switch {
case testCase.help:
if !errors.Is(err, errSandboxExecHelp) {
t.Fatalf("parseSandboxExecArgs(%q) = %q, %v; want the help sentinel", testCase.args, command, err)
}
case testCase.usage:
if err == nil || errors.Is(err, errSandboxExecHelp) {
t.Fatalf("parseSandboxExecArgs(%q) = %q, %v; want a usage error", testCase.args, command, err)
}
if !strings.Contains(err.Error(), "usage:") {
t.Errorf("a usage error must show the usage, got %q", err.Error())
}
default:
if err != nil {
t.Fatalf("parseSandboxExecArgs(%q) returned %v", testCase.args, err)
}
if strings.Join(command, "\x00") != strings.Join(testCase.command, "\x00") {
t.Errorf("parseSandboxExecArgs(%q) = %q, want %q", testCase.args, command, testCase.command)
}
}
})
}
}
// The wrapper must never consume a token it then fails to hand over. Whatever it
// returns as the command has to be a trailing slice of what it was given, with
// at most a leading separator removed, or an argument has gone missing on its
// way to the child.
func TestParseSandboxExecArgsNeverDropsAChildArgument(t *testing.T) {
for _, args := range [][]string{
{"--", "cmd", "--help", "-x", "--"},
{"cmd", "--help"},
{"ls", "--", "foo"},
{"--", "--weird-binary", "arg"},
} {
command, err := parseSandboxExecArgs(args)
if err != nil {
t.Fatalf("parseSandboxExecArgs(%q) returned %v", args, err)
}
if len(command) == 0 {
t.Fatalf("parseSandboxExecArgs(%q) returned an empty command", args)
}
suffix := strings.Join(args[len(args)-len(command):], "\x00")
if strings.Join(command, "\x00") != suffix {
t.Errorf("parseSandboxExecArgs(%q) = %q, which is not a trailing slice of the input; an argument was dropped or reordered", args, command)
}
}
}
+58 -4
View File
@@ -100,10 +100,17 @@ func windowsSandboxSetupCheck(goos string, backend sandbox.Backend, workspaceRoo
}
profile := sandbox.PermissionProfileFromPolicy(workspaceRoot, doctorSandboxPolicy(sandboxConfig), scope)
setupConfig := sandbox.WindowsSandboxSetupConfig{
SandboxHome: sandboxHome,
CommandCWD: workspaceRoot,
WorkspaceRoots: []string{workspaceRoot},
PermissionProfile: profile,
SandboxHome: sandboxHome,
CommandCWD: workspaceRoot,
WorkspaceRoots: []string{workspaceRoot},
// Same augmentation the setup args and the command plan apply, so doctor
// fingerprints what a real command fingerprints. Safe here: doctor runs in
// the operator's shell, not behind the sandbox's TEMP redirection.
PermissionProfile: sandbox.WindowsSandboxProfileWithRuntimeRoots(profile, []string{workspaceRoot}),
// Same opt-in a command would resolve, so doctor reports the principal
// mismatch as out-of-date setup instead of passing a check the next command
// will fail.
PrincipalOptIn: sandbox.WindowsSandboxPrincipalOptIn(nil),
}
if err := sandbox.ValidateWindowsSandboxSetupMarker(setupConfig); err != nil {
result := check("sandbox.backend", "Sandbox backend", StatusWarn, fmt.Sprintf("Native sandbox backend %s is installed, but Windows sandbox setup is missing or out of date: %v.", backend.Name, err), map[string]any{
@@ -115,6 +122,53 @@ func windowsSandboxSetupCheck(goos string, backend sandbox.Backend, workspaceRoo
})
return &result
}
// Setup is valid and the opt-in is set, so report which principal a command
// will actually run as.
//
// This used to warn that the principal stood down under the DEFAULT
// network-deny policy, which was true while network denial could only be
// expressed on the restricted token: a principal token cannot carry the
// synthetic offline-marker SID the WFP filters matched. Dual-role provisioning
// removed that limit by giving each workspace an offline account whose real
// group membership the same filters match, so deny mode now runs on a
// principal exactly as allow mode does. Leaving the warning would have doctor
// telling operators their reads are unconfined while they are confined.
//
// Naming the role rather than just saying "active" is the useful part. The two
// accounts differ only in that membership, so an operator debugging network
// behaviour needs to know which one this workspace picks.
if setupConfig.PrincipalOptIn {
// Asked of the shared rule rather than re-derived here, so doctor and the
// runtime cannot disagree about which account a command runs as. Two
// copies drifting is what produced the wrong report this replaces.
role := sandbox.WindowsSandboxPrincipalRoleForNetwork(profile.Network.Mode)
// SETUP IS CURRENT IS NOT THE SAME AS THE PRINCIPAL IS LIVE, and this used
// to claim the second from the first. Marker validation compares serialized
// plans and hashes; it names no account. Delete the selected account or its
// secret, or drop the offline account out of ZeroSandboxOffline, and the
// marker still validates while the runtime either falls back to the weaker
// restricted-token path or fails outright. Doctor asserting read
// confinement in that state is worse than saying nothing, because it is the
// surface an operator checks precisely when they are unsure.
//
// Verifying liveness needs the account, a usable secret and (for offline)
// the group membership, all Windows-only live queries this package cannot
// make. So the claim is narrowed to what the marker actually proves, and
// the role is still named because that part IS derived rather than assumed
// and is what an operator debugging network behaviour needs.
result := check("sandbox.principal", "Sandbox principal", StatusPass,
fmt.Sprintf("Sandbox principal setup is current; a command in this workspace selects the %s principal. Setup state does not confirm the account is usable.", role), map[string]any{
"backend": string(backend.Name),
"platform": goos,
"optIn": true,
// Deliberately not "active": nothing here checked the account, the
// secret or the group membership.
"setupCurrent": true,
"role": role,
"networkMode": string(profile.Network.Mode),
})
return &result
}
return nil
}
@@ -0,0 +1,72 @@
package doctor
import (
"strings"
"testing"
"github.com/Twigpine/zero/internal/config"
"github.com/Twigpine/zero/internal/sandbox"
)
// A VALID MARKER IS NOT A LIVE PRINCIPAL. Marker validation compares serialized
// plans and hashes and names no account, so it stays valid after the selected
// account is deleted, its secret is removed, or the offline account is dropped
// out of ZeroSandboxOffline. In each of those states the runtime falls back to
// the restricted-token path with no read confinement, or fails outright.
//
// Doctor is the surface an operator checks precisely when they are unsure, so
// claiming read confinement it has not verified is worse than reporting less.
// This pins the narrower claim: setup is current, the role is named because it
// is derived rather than assumed, and nothing asserts the account is usable.
func TestPrincipalCheckDoesNotClaimAnUnverifiedPrincipalIsActive(t *testing.T) {
sandboxHome := t.TempDir()
workspaceRoot := t.TempDir()
t.Setenv("ZERO_WINDOWS_SANDBOX_HOME", sandboxHome)
t.Setenv("ZERO_WINDOWS_SANDBOX_IDENTITY", "1")
sandboxConfig := config.SandboxConfig{}
scope, err := sandbox.NewScope(workspaceRoot, sandboxConfig.AdditionalWriteRoots)
if err != nil {
t.Fatalf("NewScope: %v", err)
}
profile := sandbox.PermissionProfileFromPolicy(workspaceRoot, doctorSandboxPolicy(sandboxConfig), scope)
// Mirrors what windowsSandboxSetupCheck derives, so the marker it writes is
// the one the check will validate against. Nothing here provisions an
// account, which is the whole point: the marker is valid and the principal
// does not exist.
if _, err := sandbox.WriteWindowsSandboxSetupMarker(sandbox.WindowsSandboxSetupConfig{
SandboxHome: sandboxHome,
CommandCWD: workspaceRoot,
WorkspaceRoots: []string{workspaceRoot},
PermissionProfile: sandbox.WindowsSandboxProfileWithRuntimeRoots(profile, []string{workspaceRoot}),
PrincipalOptIn: true,
}); err != nil {
t.Fatalf("WriteWindowsSandboxSetupMarker: %v", err)
}
result := windowsSandboxSetupCheck("windows", sandbox.Backend{Name: sandbox.BackendWindowsRestrictedToken}, workspaceRoot, sandboxConfig)
if result == nil {
t.Fatal("expected a principal check once the marker validates and the opt-in is set")
}
if result.ID != "sandbox.principal" {
t.Fatalf("check = %q (%s): the marker did not validate, so this test is not exercising the principal branch", result.ID, result.Message)
}
lowered := strings.ToLower(result.Message)
for _, claim := range []string{"is active", "commands run as"} {
if strings.Contains(lowered, claim) {
t.Errorf("doctor asserts %q about a principal it never checked: %q", claim, result.Message)
}
}
if active, ok := result.Details["active"]; ok {
t.Errorf("details carry active=%v, which nothing here verified", active)
}
// The role is still worth reporting: it is derived from the network mode by
// the shared rule rather than assumed, and it is what an operator debugging
// network behaviour needs.
if role, ok := result.Details["role"]; !ok || strings.TrimSpace(role.(string)) == "" {
t.Errorf("the selected role should still be reported: %#v", result.Details)
}
}
+1 -1
View File
@@ -10,7 +10,7 @@ import (
"strings"
)
func ensurePrivateDir(path string) error {
func EnsurePrivateDir(path string) error {
abs, err := filepath.Abs(path)
if err != nil {
return err
+8 -2
View File
@@ -12,7 +12,7 @@ import (
"golang.org/x/sys/unix"
)
func ensurePrivateDir(path string) error {
func EnsurePrivateDir(path string) error {
abs, err := filepath.Abs(path)
if err != nil {
return err
@@ -22,7 +22,13 @@ func ensurePrivateDir(path string) error {
if err != nil {
return err
}
defer unix.Close(parentFD)
// THE DESCRIPTOR THIS FUNCTION OWNS CHANGES ON EVERY ITERATION. The walk
// closes parentFD and replaces it with the child it just opened, so a defer
// that captured the first number would close a descriptor this function no
// longer owns (or one the kernel has since reused) and leave the last one it
// does own open. Close whatever is current when we leave, exactly once, on
// every path.
defer func() { unix.Close(parentFD) }()
for index, component := range components {
if component == "" {
continue
+65 -2
View File
@@ -3,9 +3,12 @@
package peermsg
import (
"fmt"
"os"
"path/filepath"
"testing"
"golang.org/x/sys/unix"
)
func TestEnsurePrivateDirRejectsSymlink(t *testing.T) {
@@ -18,7 +21,7 @@ func TestEnsurePrivateDirRejectsSymlink(t *testing.T) {
if err := os.Symlink(target, link); err != nil {
t.Fatal(err)
}
if err := ensurePrivateDir(link); err == nil {
if err := EnsurePrivateDir(link); err == nil {
t.Fatal("expected symlink runtime directory to be rejected")
}
}
@@ -33,7 +36,67 @@ func TestEnsurePrivateDirRejectsSymlinkedParent(t *testing.T) {
if err := os.Symlink(target, link); err != nil {
t.Fatal(err)
}
if err := ensurePrivateDir(filepath.Join(link, "peers")); err == nil {
if err := EnsurePrivateDir(filepath.Join(link, "peers")); err == nil {
t.Fatal("expected symlinked parent to be rejected")
}
}
// THE DESCRIPTOR THE WALK ENDS ON HAS TO BE CLOSED TOO.
//
// EnsurePrivateDir walks the path one component at a time, closing each parent
// as it opens the child. A deferred close that captured the first descriptor
// closed a number this function no longer owned and left the last one open, so
// every fallback-runtime preparation leaked a descriptor. The lowest free
// descriptor is the watermark: dup(0) hands it back, and a leak per cycle walks
// it upward. Several depths, because the kernel reuses numbers and a single
// shallow fixture can hide the leak by accident.
func TestEnsurePrivateDirClosesTheDescriptorItOwns(t *testing.T) {
lowestFree := func() int {
fd, err := unix.Dup(0)
if err != nil {
t.Fatalf("dup: %v", err)
}
unix.Close(fd)
return fd
}
// The physical path: on macOS t.TempDir() sits under /var, which is itself
// a symlink to /private/var, and this walk refuses a symlink component by
// design. Production resolves its temp root the same way before calling.
base, err := filepath.EvalSymlinks(t.TempDir())
if err != nil {
t.Fatalf("resolve temp dir: %v", err)
}
for _, depth := range []int{1, 3, 6} {
parts := []string{base}
for i := 0; i < depth; i++ {
parts = append(parts, fmt.Sprintf("level%d", i))
}
target := filepath.Join(parts...)
before := lowestFree()
for cycle := 0; cycle < 40; cycle++ {
if err := EnsurePrivateDir(target); err != nil {
t.Fatalf("depth %d cycle %d: %v", depth, cycle, err)
}
}
if after := lowestFree(); after != before {
t.Fatalf("depth %d: lowest free descriptor moved from %d to %d over 40 successful walks, so each one leaks", depth, before, after)
}
// And the failing walk: a symlink component is refused partway down.
linked := filepath.Join(base, fmt.Sprintf("linked%d", depth))
if err := os.Symlink(target, linked); err != nil {
t.Fatalf("symlink: %v", err)
}
failing := filepath.Join(linked, "below")
before = lowestFree()
for cycle := 0; cycle < 40; cycle++ {
if err := EnsurePrivateDir(failing); err == nil {
t.Fatalf("depth %d: a symlinked component was not refused", depth)
}
}
if after := lowestFree(); after != before {
t.Fatalf("depth %d: lowest free descriptor moved from %d to %d over 40 refused walks", depth, before, after)
}
}
}
+1 -1
View File
@@ -12,7 +12,7 @@ import (
"golang.org/x/sys/windows"
)
func ensurePrivateDir(path string) (resultErr error) {
func EnsurePrivateDir(path string) (resultErr error) {
abs, err := filepath.Abs(path)
if err != nil {
return err
+5 -5
View File
@@ -54,7 +54,7 @@ func TestEnsurePrivateDirAppliesOwnerOnlyProtectedDACL(t *testing.T) {
if !windowsDirectoryDACLContains(t, path, worldSID) {
t.Fatal("test setup did not grant the broad Everyone ACE")
}
if err := ensurePrivateDir(path); err != nil {
if err := EnsurePrivateDir(path); err != nil {
t.Fatal(err)
}
descriptor, err := windows.GetNamedSecurityInfo(
@@ -149,7 +149,7 @@ func windowsDirectoryDACLContains(t *testing.T, path string, wanted *windows.SID
func TestSecurePrivateDirectoryRejectsOwnerMismatch(t *testing.T) {
path := filepath.Join(t.TempDir(), "private")
if err := ensurePrivateDir(path); err != nil {
if err := EnsurePrivateDir(path); err != nil {
t.Fatal(err)
}
handle, err := openWindowsDirectory(path, windows.FILE_LIST_DIRECTORY|windows.FILE_TRAVERSE|windows.SYNCHRONIZE|windows.READ_CONTROL|windows.WRITE_DAC)
@@ -172,7 +172,7 @@ func TestSecurePrivateDirectoryRejectsOwnerMismatch(t *testing.T) {
func TestSecurePrivateDirectoryReportsDACLWriteFailure(t *testing.T) {
path := filepath.Join(t.TempDir(), "private")
if err := ensurePrivateDir(path); err != nil {
if err := EnsurePrivateDir(path); err != nil {
t.Fatal(err)
}
handle, err := openWindowsDirectory(path, windows.FILE_LIST_DIRECTORY|windows.FILE_TRAVERSE|windows.SYNCHRONIZE|windows.READ_CONTROL)
@@ -206,7 +206,7 @@ func TestEnsurePrivateDirRejectsWindowsReparseParent(t *testing.T) {
if err := os.Symlink(target, link); err != nil {
t.Skipf("cannot create Windows directory symlink: %v", err)
}
if err := ensurePrivateDir(filepath.Join(link, "peers")); err == nil {
if err := EnsurePrivateDir(filepath.Join(link, "peers")); err == nil {
t.Fatal("expected reparse-point parent to be rejected")
}
}
@@ -217,7 +217,7 @@ func TestEnsurePrivateDirRejectsWindowsFileComponent(t *testing.T) {
if err := os.WriteFile(file, []byte("not a directory"), 0o600); err != nil {
t.Fatal(err)
}
if err := ensurePrivateDir(filepath.Join(file, "peers")); err == nil {
if err := EnsurePrivateDir(filepath.Join(file, "peers")); err == nil {
t.Fatal("expected file path component to be rejected")
}
}
+3 -3
View File
@@ -158,7 +158,7 @@ func New(options Options) (*Service, error) {
}
// canonicalRuntimePath normalizes aliases in the existing prefix. It does not
// establish a security boundary; ensurePrivateDir validates that boundary when
// establish a security boundary; EnsurePrivateDir validates that boundary when
// the service starts.
func canonicalRuntimePath(path string) (string, error) {
missing := make([]string, 0, 4)
@@ -219,10 +219,10 @@ func (service *Service) Start(handler Handler) error {
if service.closed {
return errors.New("peer messaging: service is closed")
}
if err := ensurePrivateDir(service.root); err != nil {
if err := EnsurePrivateDir(service.root); err != nil {
return fmt.Errorf("peer messaging: create runtime directory: %w", err)
}
if err := ensurePrivateDir(service.registryDir()); err != nil {
if err := EnsurePrivateDir(service.registryDir()); err != nil {
return fmt.Errorf("peer messaging: create registry: %w", err)
}
endpoint, err := service.transport.Endpoint(service.root, service.nonce, service.pid)
+1 -1
View File
@@ -44,7 +44,7 @@ func canonicalPrivateDir(path string) (string, error) {
if err != nil {
return "", err
}
if err := ensurePrivateDir(canonical); err != nil {
if err := EnsurePrivateDir(canonical); err != nil {
return "", err
}
return canonical, nil
+77 -1
View File
@@ -20,6 +20,10 @@ type AnalysisResult struct {
TooComplex bool
// Programs lists the distinct top-level command names found, for diagnostics.
Programs []string
// GitInit is set when the script would create a git repository. It is a
// separate signal from Destructive and Network because the decision it feeds
// depends on WHERE the workspace sits, which the analyzer cannot see.
GitInit bool
}
// destructivePrograms are commands that can irrecoverably destroy data.
@@ -183,6 +187,9 @@ func analyzeInto(script string, result *AnalysisResult, seen map[string]bool, de
if commandUsesNetwork(prog, rest) {
result.Network = true
}
if commandCreatesGitRepository(call, prog, rest) {
result.GitInit = true
}
if destructivePrograms[prog] ||
(prog == "rm" && hasRecursiveForce(rest)) ||
(powerShellRemoveItemPrograms[prog] && hasPowerShellRecursiveForce(rest)) ||
@@ -277,8 +284,77 @@ func packageManagerOffline(words []string) bool {
return false
}
// gitGlobalOptionsTakingValue are git's own options that consume the NEXT word.
//
// firstSubcommand skips words beginning with "-" but not the value that follows
// one, so "git -C sub clone <url>" made it answer "sub" and the command was
// classified as touching no network at all. The "--opt=value" spelling is one
// token and needs no entry here.
//
// Keys are lowercase because the analyzer lowercases every word before it gets
// here, which also means -C and -c arrive identically. That is fine: both
// consume a value, and nothing below needs to tell them apart.
var gitGlobalOptionsTakingValue = map[string]bool{
"-c": true, "-C": true,
"--git-dir": true, "--work-tree": true, "--namespace": true,
"--exec-path": true, "--config-env": true, "--super-prefix": true,
"--attr-source": true,
}
// gitSubcommand returns git's subcommand, skipping global options AND the values
// they consume. Returns "" when the words carry no subcommand.
func gitSubcommand(words []string) string {
for index := 0; index < len(words); index++ {
word := words[index]
if word == "" {
continue
}
if !strings.HasPrefix(word, "-") {
return word
}
// "--opt=value" is one token and carries its own value.
if strings.HasPrefix(word, "--") && strings.Contains(word, "=") {
continue
}
if gitGlobalOptionsTakingValue[word] {
index++
}
}
return ""
}
// commandCreatesGitRepository reports whether this call would create a git
// repository. It shares gitSubcommand with the network gate deliberately, so the
// global options that already bypassed that gate cannot bypass this one either:
// "git -C sub init" and "git -c k=v init" both resolve to init.
//
// init-db is git's original spelling and still works today. clone creates a
// repository as surely as init does, with its config and hooks written by the
// fetch rather than by hand: "git clone <url> ." into a workspace governed by an
// ancestor repository lands a root .git whose carveouts setup never planned, so
// it is the same nested-repository decision. The network prompt is a separate
// gate and granting it does not answer this one. Reported by @gnanam1990.
//
// The subcommand is the one git runs after alias resolution, which git_alias.go
// models: definitions from the command line and from the environment the call
// sets, expanded with git's own quoting and its in-alias option handling. A
// definition this analyzer cannot read makes the command unclassifiable, and
// under this guard that is a refusal.
func commandCreatesGitRepository(call *syntax.CallExpr, prog string, args []*syntax.Word) bool {
if prog != "git" {
return false
}
words := literalWordTexts(args)
aliases := gitAliasTable{}
if !gitEnvironmentAliases(aliases, callAssignments(call, args)) {
return true
}
gitInlineAliases(aliases, words)
return gitSubcommandCreatesRepository(gitSubcommand(words), aliases)
}
func gitUsesNetwork(words []string) bool {
switch firstSubcommand(words, nil) {
switch gitSubcommand(words) {
case "clone", "fetch", "pull", "push", "ls-remote", "archive":
return true
default:
+13
View File
@@ -394,6 +394,19 @@ func (engine *Engine) Evaluate(ctx context.Context, request Request) Decision {
return deny(request, risk, block.Code, block.Path, block.Reason, false)
}
}
// BEFORE THE NETWORK GATE, because this one cannot be approved away.
//
// `git clone` is both a network command and a repository-creating one. With
// the network gate first, a clone in a governed nested workspace under the
// default NetworkDeny came back as a network prompt: the operator was asked
// to approve network access for a command that approval could never make
// runnable, and the reason that actually decides it was never shown. The
// refusal below does not depend on policy, permission or mode, so it is the
// answer whatever the network gate would have said, and it is the one with a
// remedy the operator can act on. Reported by @jatmn.
if HasRiskCategory(risk, "nested_git_init") {
return deny(request, risk, BlockNestedGitInit, "", ReasonNestedGitInit, false)
}
netMode := engine.effectiveNetworkMode(policy)
if netMode == NetworkDeny && HasRiskCategory(risk, "network") && !engine.toolNetworkExempt(request) {
if request.SideEffect == SideEffectShell && request.PermissionMode != PermissionUnsafe {
+376
View File
@@ -0,0 +1,376 @@
package sandbox
import (
"strconv"
"strings"
"mvdan.cc/sh/v3/syntax"
)
// THE NESTED-REPOSITORY GUARD CLASSIFIES THE COMMAND GIT RUNS, NOT THE ONE
// TYPED. Git rewrites its argument vector before choosing a builtin: an alias
// defined on the command line, in the environment or through --config-env is
// split with shell-style quoting, its own leading global options are applied,
// and the result is looked up again until a builtin is reached. Reading the
// literal token, or the first whitespace-separated field of an alias value,
// let `git -c alias.a='-c alias.b=init b' a .` and `git -c 'alias.a="init"' a .`
// create a repository the workspace profile carves nothing out for. What
// follows models that rewrite, and where the model runs out it refuses rather
// than guesses: under this guard the safe answer to "could this make a
// repository" is yes. Reported by @gnanam1990.
// gitAliasTable maps a lowercased alias name to every definition the command
// supplies for it. Git keeps one value per key, the last one written, and the
// order in which the environment, -c and --config-env feed that list is not
// something this guard needs to reproduce: a definition git would discard but
// which reaches init here costs one refusal, while the opposite mistake costs
// a repository. So every definition is kept, and any of them reaching init
// refuses. For the same reason an alias that shadows a builtin, which git
// ignores, is followed here rather than skipped: this file carries no list of
// git's commands, and refusing `-c alias.status=init status` loses nothing.
type gitAliasTable map[string][]gitAliasDefinition
// gitAliasDefinition is one alias value. unknown marks a definition whose text
// cannot be read statically, such as --config-env=alias.x=VAR or a
// GIT_CONFIG_VALUE_n written as $var: git will run whatever it holds, and
// this guard cannot say what that is.
type gitAliasDefinition struct {
text string
unknown bool
}
func (table gitAliasTable) define(name, text string) {
name = strings.ToLower(strings.TrimSpace(name))
if name == "" {
return
}
table[name] = append(table[name], gitAliasDefinition{text: strings.ToLower(text)})
}
func (table gitAliasTable) defineUnknown(name string) {
name = strings.ToLower(strings.TrimSpace(name))
if name == "" {
return
}
table[name] = append(table[name], gitAliasDefinition{unknown: true})
}
// defineSetting records a `key=value` config setting when key names an alias.
// readable is false when the value is only known by reference, which makes the
// alias unknown rather than absent. A setting without "=" is a boolean in git
// (`alias.x` expands to "true") and defines nothing worth following.
func (table gitAliasTable) defineSetting(setting string, readable bool) {
name, value, found := strings.Cut(setting, "=")
if !found {
return
}
alias, ok := strings.CutPrefix(strings.ToLower(strings.TrimSpace(name)), "alias.")
if !ok {
return
}
if !readable {
table.defineUnknown(alias)
return
}
table.define(alias, value)
}
// splitGitAliasExpansion tokenizes an alias value the way git's split_cmdline
// does: whitespace separates words, a single or double quote opens a quoted
// span anywhere inside a word, and a backslash outside single quotes escapes
// the next byte. An unclosed quote or a trailing backslash is a fatal error in
// git ("bad alias string"), so ok is false and nothing would have run.
func splitGitAliasExpansion(text string) (argv []string, ok bool) {
var current strings.Builder
var quoted byte
inWord := false
for index := 0; index < len(text); index++ {
c := text[index]
switch {
case quoted == 0 && isGitSpace(c):
if inWord {
argv = append(argv, current.String())
current.Reset()
inWord = false
}
case quoted == 0 && (c == '\'' || c == '"'):
quoted = c
inWord = true
case c == quoted:
quoted = 0
default:
if c == '\\' && quoted != '\'' {
index++
if index >= len(text) {
return nil, false
}
c = text[index]
}
current.WriteByte(c)
inWord = true
}
}
if quoted != 0 {
return nil, false
}
if inWord {
argv = append(argv, current.String())
}
return argv, true
}
func isGitSpace(c byte) bool {
switch c {
case ' ', '\t', '\n', '\r', '\v', '\f':
return true
}
return false
}
// gitAliasExpansionSubcommand runs a split expansion through git's own
// handling of global options inside an alias and returns the subcommand git
// would look up next. Inside an expansion git accepts -c and --config-env,
// which push settings the next lookup sees (that is how `-c alias.b=init b`
// reaches init), and the pager switches, which change nothing that runs. An
// option that changes the environment (-C, --git-dir, --bare, ...) is fatal
// inside an alias, and an expansion made only of options is an empty alias;
// both return ok false. So does an option this guard does not model, because
// "git would refuse this" and "this guard cannot read this" end the same way.
func gitAliasExpansionSubcommand(argv []string, aliases gitAliasTable) (subcommand string, ok bool) {
for index := 0; index < len(argv); index++ {
word := argv[index]
if word == "" {
return "", false
}
if !strings.HasPrefix(word, "-") {
return word, true
}
switch {
case word == "-c", word == "--config-env":
if index+1 >= len(argv) {
return "", false
}
index++
aliases.defineSetting(argv[index], word == "-c")
case strings.HasPrefix(word, "--config-env="):
aliases.defineSetting(strings.TrimPrefix(word, "--config-env="), false)
case word == "-p", word == "--paginate", word == "-P", word == "--no-pager":
default:
return "", false
}
}
return "", false
}
// gitSubcommandCreatesRepository reports whether subcommand, resolved through
// aliases the way git resolves it, is init, init-db or clone. The chain is
// followed to its end with the names on the current path kept, so a cycle is a
// refusal here the way "alias loop detected" is fatal in git. A shell alias
// runs a program this analyzer cannot classify; an expansion git cannot split,
// cannot run, or that leaves no subcommand behind is the same case, and so is
// a definition whose text is not readable. Every one of those refuses.
func gitSubcommandCreatesRepository(subcommand string, aliases gitAliasTable) bool {
return gitAliasPathCreatesRepository(subcommand, aliases, nil)
}
func gitAliasPathCreatesRepository(subcommand string, aliases gitAliasTable, path []string) bool {
switch subcommand {
case "init", "init-db", "clone":
return true
}
definitions, ok := aliases[subcommand]
if !ok {
return false
}
for _, seen := range path {
if seen == subcommand {
return true
}
}
path = append(path, subcommand)
for _, definition := range definitions {
if definition.unknown || strings.HasPrefix(definition.text, "!") {
return true
}
argv, ok := splitGitAliasExpansion(definition.text)
if !ok {
return true
}
next, ok := gitAliasExpansionSubcommand(argv, aliases)
if !ok {
return true
}
if gitAliasPathCreatesRepository(next, aliases, path) {
return true
}
}
return false
}
// gitInlineAliases records the alias definitions supplied ahead of the
// subcommand: `-c alias.NAME=EXPANSION`, and `--config-env alias.NAME=VAR` in
// both spellings, whose value lives in a variable this analyzer does not read.
// Git accepts no attached `-cNAME=VALUE` spelling ("unknown option"), so none
// is recognised here. Other global options that take a value are stepped over
// the way gitSubcommand steps over them, so a value that happens to look like
// a subcommand does not end the scan early.
func gitInlineAliases(aliases gitAliasTable, words []string) {
for index := 0; index < len(words); index++ {
word := words[index]
if word == "" {
continue
}
if !strings.HasPrefix(word, "-") {
return
}
switch {
case word == "-c", word == "--config-env":
if index+1 < len(words) {
index++
aliases.defineSetting(words[index], word == "-c")
}
case strings.HasPrefix(word, "--config-env="):
aliases.defineSetting(strings.TrimPrefix(word, "--config-env="), false)
case strings.HasPrefix(word, "--") && strings.Contains(word, "="):
case gitGlobalOptionsTakingValue[word]:
index++
}
}
}
// shellAssignment is one NAME=value the command hands to git's environment.
// readable is false when the value is an expansion this analyzer cannot see.
type shellAssignment struct {
value string
readable bool
}
// callAssignments collects the assignments in force for the program: the
// shell prefix (FOO=bar git ...) and the NAME=value words an env wrapper
// forwards (env FOO=bar git ...), which sit ahead of the program word.
func callAssignments(call *syntax.CallExpr, rest []*syntax.Word) map[string]shellAssignment {
assignments := map[string]shellAssignment{}
if call == nil {
return assignments
}
for _, assign := range call.Assigns {
if assign == nil || assign.Name == nil {
continue
}
readable := !assign.Append && assign.Array == nil && assign.Index == nil &&
(assign.Value == nil || isLiteralWord(assign.Value))
assignments[assign.Name.Value] = shellAssignment{value: wordText(assign.Value), readable: readable}
}
program := len(call.Args) - len(rest) - 1
for index := 0; index < program && index < len(call.Args); index++ {
name, value, found := strings.Cut(wordText(call.Args[index]), "=")
if !found || !isEnvName(name) {
continue
}
assignments[name] = shellAssignment{value: value, readable: isLiteralWord(call.Args[index])}
}
return assignments
}
func isEnvName(name string) bool {
if name == "" {
return false
}
for index, r := range name {
switch {
case r == '_', r >= 'a' && r <= 'z', r >= 'A' && r <= 'Z':
case r >= '0' && r <= '9' && index > 0:
default:
return false
}
}
return true
}
// gitEnvironmentAliases records the alias definitions the command hands git
// through its environment, which git reads exactly as it reads -c:
// GIT_CONFIG_COUNT with GIT_CONFIG_KEY_n and GIT_CONFIG_VALUE_n, and
// GIT_CONFIG_PARAMETERS. It reports false when a definition this guard needs
// cannot be read: a count, a key or the parameter list written as an
// expansion, or the value of an alias key written that way. A count git would
// reject, or a numbered key with no value, is reported the same way; git dies
// on those, so refusing them costs nothing.
func gitEnvironmentAliases(aliases gitAliasTable, env map[string]shellAssignment) bool {
if parameters, ok := env["GIT_CONFIG_PARAMETERS"]; ok {
if !parameters.readable {
return false
}
settings, ok := splitGitConfigParameters(parameters.value)
if !ok {
return false
}
for _, setting := range settings {
aliases.defineSetting(setting, true)
}
}
count, ok := env["GIT_CONFIG_COUNT"]
if !ok {
return true
}
if !count.readable {
return false
}
n, err := strconv.Atoi(strings.TrimSpace(count.value))
if err != nil || n < 0 || n > 1024 {
return false
}
for index := 0; index < n; index++ {
key, ok := env["GIT_CONFIG_KEY_"+strconv.Itoa(index)]
if !ok || !key.readable {
return false
}
value, ok := env["GIT_CONFIG_VALUE_"+strconv.Itoa(index)]
if !ok {
return false
}
aliases.defineSetting(key.value+"="+value.value, value.readable)
}
return true
}
// splitGitConfigParameters dequotes GIT_CONFIG_PARAMETERS the way git does:
// whitespace-separated entries, each single-quoted, with `'\”` and `'\!'`
// standing for a quote or a bang inside one. Anything else is "bogus format"
// in git, a fatal error, so ok is false.
func splitGitConfigParameters(text string) (settings []string, ok bool) {
index := 0
for {
for index < len(text) && isGitSpace(text[index]) {
index++
}
if index >= len(text) {
return settings, true
}
if text[index] != '\'' {
return nil, false
}
index++
var current strings.Builder
for {
if index >= len(text) {
return nil, false
}
c := text[index]
index++
if c != '\'' {
current.WriteByte(c)
continue
}
if index+2 < len(text) && text[index] == '\\' && (text[index+1] == '\'' || text[index+1] == '!') && text[index+2] == '\'' {
current.WriteByte(text[index+1])
index += 3
continue
}
if index >= len(text) || isGitSpace(text[index]) {
settings = append(settings, current.String())
break
}
return nil, false
}
}
}
+103
View File
@@ -0,0 +1,103 @@
package sandbox
import (
"reflect"
"testing"
)
// The tokenizer has to agree with git's split_cmdline on the forms that decide
// which subcommand runs: quotes anywhere in a word, backslash escapes outside
// single quotes, and the two errors git dies on.
func TestSplitGitAliasExpansionMatchesGitQuoting(t *testing.T) {
for _, tc := range []struct {
expansion string
want []string
ok bool
}{
{"init", []string{"init"}, true},
{`"init"`, []string{"init"}, true},
{`in"it"`, []string{"init"}, true},
{`in\it`, []string{"init"}, true},
{`'in\it'`, []string{`in\it`}, true},
{`"in\"it"`, []string{`in"it`}, true},
{`-c alias.b=init b`, []string{"-c", "alias.b=init", "b"}, true},
{`-c "alias.b=init x" b`, []string{"-c", "alias.b=init x", "b"}, true},
{`'-c' 'alias.b=init' b`, []string{"-c", "alias.b=init", "b"}, true},
{" init \t ", []string{"init"}, true},
{"", nil, true},
{`"init`, nil, false},
{`'init`, nil, false},
{`init\`, nil, false},
} {
got, ok := splitGitAliasExpansion(tc.expansion)
if ok != tc.ok || !reflect.DeepEqual(got, tc.want) {
t.Errorf("splitGitAliasExpansion(%q) = %q, %v; want %q, %v", tc.expansion, got, ok, tc.want, tc.ok)
}
}
}
// GIT_CONFIG_PARAMETERS is git's own single-quoted list; an entry git would
// call bogus makes the whole variable unreadable rather than partly read.
func TestSplitGitConfigParametersDequotesLikeGit(t *testing.T) {
for _, tc := range []struct {
text string
want []string
ok bool
}{
{`'alias.a=init'`, []string{"alias.a=init"}, true},
{`'alias.a=init' 'x=y'`, []string{"alias.a=init", "x=y"}, true},
{` 'alias.a=in'\''it' `, []string{"alias.a=in'it"}, true},
{`'alias.a=in'\!'it'`, []string{"alias.a=in!it"}, true},
{"", nil, true},
{`alias.a=init`, nil, false},
{`'alias.a=init`, nil, false},
{`'a'x`, nil, false},
} {
got, ok := splitGitConfigParameters(tc.text)
if ok != tc.ok || !reflect.DeepEqual(got, tc.want) {
t.Errorf("splitGitConfigParameters(%q) = %q, %v; want %q, %v", tc.text, got, ok, tc.want, tc.ok)
}
}
}
// Resolution applies git's in-alias option handling: a -c inside an expansion
// defines the alias the next lookup uses, pager switches are stepped over, an
// environment-changing option or an unreadable definition refuses, and only a
// chain that ends in a real repository-creating command is creation.
func TestGitAliasResolutionFollowsExpansionOptions(t *testing.T) {
for _, tc := range []struct {
name string
subcommand string
aliases map[string]string
unknown []string
creates bool
}{
{name: "option inside expansion defines the next alias", subcommand: "a", aliases: map[string]string{"a": "-c alias.b=init b"}, creates: true},
{name: "quoted expansion", subcommand: "a", aliases: map[string]string{"a": `"init"`}, creates: true},
{name: "pager switch does not hide init", subcommand: "a", aliases: map[string]string{"a": "--no-pager init"}, creates: true},
{name: "environment-changing option refuses", subcommand: "a", aliases: map[string]string{"a": "-C . init"}, creates: true},
{name: "unclosed quote refuses", subcommand: "a", aliases: map[string]string{"a": `"in`}, creates: true},
{name: "options only refuses", subcommand: "a", aliases: map[string]string{"a": "-c x=y"}, creates: true},
{name: "config-env inside expansion is unreadable", subcommand: "a", aliases: map[string]string{"a": "--config-env=alias.b=var b"}, creates: true},
{name: "redefinition loop refuses", subcommand: "a", aliases: map[string]string{"a": "-c alias.a=init a"}, creates: true},
{name: "unknown definition refuses", subcommand: "a", unknown: []string{"a"}, creates: true},
{name: "harmless option-bearing alias", subcommand: "st", aliases: map[string]string{"st": "-c color.ui=always status"}, creates: false},
{name: "harmless quoted alias", subcommand: "st", aliases: map[string]string{"st": `"status"`}, creates: false},
{name: "harmless pager alias", subcommand: "l", aliases: map[string]string{"l": "--no-pager log --oneline"}, creates: false},
{name: "harmless chain through quotes", subcommand: "s", aliases: map[string]string{"s": "st", "st": `sta"tus"`}, creates: false},
{name: "not an alias", subcommand: "status", creates: false},
} {
t.Run(tc.name, func(t *testing.T) {
table := gitAliasTable{}
for name, expansion := range tc.aliases {
table.define(name, expansion)
}
for _, name := range tc.unknown {
table.defineUnknown(name)
}
if got := gitSubcommandCreatesRepository(tc.subcommand, table); got != tc.creates {
t.Fatalf("gitSubcommandCreatesRepository(%q) = %v, want %v", tc.subcommand, got, tc.creates)
}
})
}
}
@@ -0,0 +1,58 @@
package sandbox
import "testing"
// GIT'S GLOBAL OPTIONS CONSUME THE NEXT WORD, AND THE CLASSIFIER HAS TO KNOW.
//
// firstSubcommand skips words beginning with "-" but not the value that follows
// one. So "git -C sub clone <url>" made it answer "sub", the command classified
// as touching no network at all, and the network gate never fired. Two spellings
// an ordinary user types by habit walked straight through it.
//
// Driven through AnalyzeCommand rather than the helper, because the gate reads
// the analysis and a helper-level assertion would not have caught this.
func TestGitGlobalOptionsDoNotHideTheSubcommand(t *testing.T) {
for _, testCase := range []struct {
script string
want bool
}{
{script: "git clone https://example.com/x", want: true},
{script: "git -C sub clone https://example.com/x", want: true},
{script: "git -c user.name=x clone https://example.com/x", want: true},
{script: "git -c a=b -C sub clone https://example.com/x", want: true},
{script: "git --git-dir=/tmp/g clone https://example.com/x", want: true},
{script: "git --namespace ns fetch origin", want: true},
{script: "git -C sub push origin main", want: true},
// Local-only work stays local, or the fix would be "call everything network".
{script: "git status", want: false},
{script: "git -C sub status", want: false},
{script: "git -c a=b commit -m x", want: false},
{script: "git init", want: false},
} {
if got := AnalyzeCommand(testCase.script).Network; got != testCase.want {
t.Errorf("AnalyzeCommand(%q).Network = %v, want %v", testCase.script, got, testCase.want)
}
}
}
// The subcommand parser itself, including the option that consumes a value and
// the self-contained "--opt=value" spelling that does not.
func TestGitSubcommandSkipsOptionValues(t *testing.T) {
for _, testCase := range []struct {
words []string
want string
}{
{words: []string{"clone", "url"}, want: "clone"},
{words: []string{"-c", "sub", "clone"}, want: "clone"},
{words: []string{"--git-dir=/tmp/g", "clone"}, want: "clone"},
{words: []string{"--namespace", "ns", "fetch"}, want: "fetch"},
{words: []string{"-c", "a=b", "-c", "sub", "push"}, want: "push"},
{words: []string{"--no-pager", "status"}, want: "status"},
{words: []string{}, want: ""},
{words: []string{"-c", "a=b"}, want: ""},
} {
if got := gitSubcommand(testCase.words); got != testCase.want {
t.Errorf("gitSubcommand(%v) = %q, want %q", testCase.words, got, testCase.want)
}
}
}
@@ -0,0 +1,451 @@
package sandbox
import (
"context"
"os"
"path/filepath"
"testing"
)
// nestedGitWorkspace returns an ancestor repository and a workspace inside it
// that carries no git metadata of its own, which is the shape the whole refusal
// is about.
func nestedGitWorkspace(t *testing.T) (ancestor string, workspace string) {
t.Helper()
ancestor = t.TempDir()
if err := os.MkdirAll(filepath.Join(ancestor, ".git"), 0o700); err != nil {
t.Fatal(err)
}
workspace = filepath.Join(ancestor, "packages", "app")
if err := os.MkdirAll(workspace, 0o700); err != nil {
t.Fatal(err)
}
if _, err := os.Lstat(filepath.Join(workspace, ".git")); err == nil {
t.Fatal("SETUP INVALID: the workspace carries its own .git, which is the protected case, not this one")
}
return ancestor, workspace
}
func gitCommandRequest(workspace string, command string) Request {
return Request{
ToolName: "bash",
SideEffect: SideEffectShell,
Permission: PermissionPrompt,
PermissionMode: PermissionModeAsk,
WorkspaceRoot: workspace,
Args: map[string]any{"command": command},
}
}
func gitWorkspaceEngine(t *testing.T, workspace string) *Engine {
t.Helper()
return NewEngine(EngineOptions{
WorkspaceRoot: workspace,
Policy: DefaultPolicy(),
Backend: nativeWrappingBackend,
})
}
// THE LIFECYCLE, END TO END: the workspace is protected at write time AND the
// command that would create a repository there is refused with an explanation.
//
// The setup guard is still load-bearing, but it now asserts the opposite of
// what it once did. The carveouts were restored for a nested workspace, because
// skipping them left nothing denying writes to <root>/.git and a repository
// could be assembled there without running git at all. So the refusal is no
// longer the only thing standing between a sandboxed command and a writable
// config; it is the layer that tells an operator why, while the deny ACE is
// what stops it. If the carveouts disappear again this fails here, because the
// refusal on its own does not cover mkdir.
func TestNestedWorkspaceRefusesGitInit(t *testing.T) {
ancestor, workspace := nestedGitWorkspace(t)
carved := map[string]bool{}
for _, carveout := range gitMetadataWriteCarveouts(workspace) {
carved[filepath.Base(carveout)] = true
}
if !carved["config"] || !carved["hooks"] {
t.Fatalf("SETUP INVALID: the nested workspace planned %v, so config and hooks are not denied and the refusal below is the only protection again", gitMetadataWriteCarveouts(workspace))
}
engine := gitWorkspaceEngine(t, workspace)
decision := engine.Evaluate(context.Background(), gitCommandRequest(workspace, "git init"))
if decision.Action != ActionDeny {
t.Fatalf("git init inside the repository at %s was %s, not denied; the repository it creates gets a writable config and hooks under the workspace grant", ancestor, decision.Action)
}
if decision.Block == nil || decision.Block.Code != BlockNestedGitInit {
t.Fatalf("block = %#v, want code %s so the operator gets the nested-repository explanation and not a generic denial", decision.Block, BlockNestedGitInit)
}
}
// The refusal sits ahead of every allow path in Evaluate, so a tool already
// cleared by permissions does not walk through it.
func TestNestedGitInitRefusalOutranksAnAllowPermission(t *testing.T) {
_, workspace := nestedGitWorkspace(t)
engine := gitWorkspaceEngine(t, workspace)
request := gitCommandRequest(workspace, "git init")
request.Permission = PermissionAllow
if decision := engine.Evaluate(context.Background(), request); decision.Action != ActionDeny {
t.Fatalf("an allow permission carried git init through: %#v", decision)
}
request = gitCommandRequest(workspace, "git init")
request.PermissionMode = PermissionUnsafe
request.PermissionGranted = true
if decision := engine.Evaluate(context.Background(), request); decision.Action != ActionDeny {
t.Fatalf("unsafe mode carried git init through: %#v", decision)
}
}
// The global options that bypassed the network gate must not bypass this one.
// These are the exact spellings that classified a clone as network=false before
// gitSubcommand learned which options take a value.
func TestNestedGitInitRefusalSurvivesGitGlobalOptions(t *testing.T) {
_, workspace := nestedGitWorkspace(t)
engine := gitWorkspaceEngine(t, workspace)
for _, command := range []string{
"git init",
"git init-db",
"git -C packages/app init",
"git -c core.hooksPath=/tmp/h init",
"git --git-dir=/tmp/g init",
"git --namespace ns init",
"sh -c \"git init\"",
"sudo git init",
"git status && git init",
} {
t.Run(command, func(t *testing.T) {
decision := engine.Evaluate(context.Background(), gitCommandRequest(workspace, command))
if decision.Action != ActionDeny {
t.Fatalf("%q was %s, not denied", command, decision.Action)
}
})
}
}
// CONTROL: ordinary git in a nested workspace is untouched.
//
// Discovery still walks up to the ancestor and every command that uses it keeps
// working; only creation is refused. Without this, returning deny for anything
// containing the word git would pass the tests above.
func TestNestedWorkspaceStillRunsOrdinaryGitCommands(t *testing.T) {
_, workspace := nestedGitWorkspace(t)
engine := gitWorkspaceEngine(t, workspace)
for _, command := range []string{
"git status",
"git add .",
"git commit -m init",
"git log --oneline",
"git worktree list",
"git submodule update --init",
} {
t.Run(command, func(t *testing.T) {
decision := engine.Evaluate(context.Background(), gitCommandRequest(workspace, command))
if decision.Action == ActionDeny {
t.Fatalf("%q was denied in a nested workspace: %s", command, decision.Reason)
}
})
}
}
// CONTROL: a standalone workspace still creates repositories.
//
// It keeps its materialized config and hooks carveouts, so the protection the
// refusal stands in for is actually there and the command is allowed.
func TestStandaloneWorkspaceStillAllowsGitInit(t *testing.T) {
workspace := t.TempDir()
if gitMetadataGovernedByAncestor(workspace) {
t.Skip("this temp directory sits inside a repository, so it is not the standalone case")
}
if len(gitMetadataWriteCarveouts(workspace)) == 0 {
t.Fatal("SETUP INVALID: a standalone workspace planned no carveouts, so it has no protection to allow git init against")
}
engine := gitWorkspaceEngine(t, workspace)
decision := engine.Evaluate(context.Background(), gitCommandRequest(workspace, "git init"))
if decision.Action == ActionDeny {
t.Fatalf("git init was refused in a standalone workspace: %s", decision.Reason)
}
}
// CONTROL: a linked worktree is a workspace whose .git is a FILE.
//
// It owns git metadata, keeps its pointer-file carveout, and is not somebody
// else's repository, so nothing here is refused. Zero's own development
// worktrees are this shape, so getting it wrong would refuse git init for the
// people writing this code.
func TestLinkedWorktreeWorkspaceStillAllowsGitInit(t *testing.T) {
ancestor := t.TempDir()
if err := os.MkdirAll(filepath.Join(ancestor, ".git", "worktrees", "w"), 0o700); err != nil {
t.Fatal(err)
}
workspace := filepath.Join(ancestor, "checkout")
if err := os.MkdirAll(workspace, 0o700); err != nil {
t.Fatal(err)
}
pointer := filepath.Join(workspace, ".git")
if err := os.WriteFile(pointer, []byte("gitdir: ../.git/worktrees/w\n"), 0o600); err != nil {
t.Fatal(err)
}
// SETUP: the pointer carveout is intact, or this proves nothing about
// worktrees keeping their protection.
specs := gitMetadataWriteCarveoutSpecs(workspace)
if len(specs) != 1 || specs[0].Path != pointer || !specs[0].IsFile {
t.Fatalf("SETUP INVALID: linked worktree carveouts = %+v, want the file-shaped pointer %s", specs, pointer)
}
engine := gitWorkspaceEngine(t, workspace)
if decision := engine.Evaluate(context.Background(), gitCommandRequest(workspace, "git init")); decision.Action == ActionDeny {
t.Fatalf("git init was refused in a linked worktree, which owns its git metadata: %s", decision.Reason)
}
}
// And the workspace-level question is asked of the workspace itself, so a
// workspace that already carries .git is never treated as nested no matter what
// is above it.
func TestWorkspaceOwningGitIsNotTreatedAsNested(t *testing.T) {
ancestor := t.TempDir()
if err := os.MkdirAll(filepath.Join(ancestor, ".git"), 0o700); err != nil {
t.Fatal(err)
}
workspace := filepath.Join(ancestor, "vendored")
if err := os.MkdirAll(filepath.Join(workspace, ".git"), 0o700); err != nil {
t.Fatal(err)
}
if workspaceGovernedByAncestorRepository(workspace) {
t.Fatal("a workspace that owns .git was reported as governed by its ancestor, so its own protection would be refused instead of applied")
}
}
// CLONE IS CREATION TOO, AND THE NETWORK GRANT DOES NOT ANSWER FOR IT.
//
// "git clone <url> ." into a workspace governed by an ancestor repository lands
// a root .git whose config and hooks setup never planned carveouts for, exactly
// the state git init produces, but the guard only knew the init spelling. With
// network explicitly allowed and the shell grant already given, the clone came
// back as an ordinary allow. The repository-creation refusal is a separate
// decision from the network prompt and has to stand on its own. Reported by
// @gnanam1990.
func TestNestedWorkspaceRefusesGitCloneIntoTheRoot(t *testing.T) {
ancestor, workspace := nestedGitWorkspace(t)
policy := DefaultPolicy()
policy.Network = NetworkAllow
engine := NewEngine(EngineOptions{WorkspaceRoot: workspace, Policy: policy, Backend: nativeWrappingBackend})
for _, command := range []string{
"git clone https://example.invalid/repo.git .",
"git -C . clone https://example.invalid/repo.git .",
"git clone --depth 1 https://example.invalid/repo.git vendor/dep",
} {
request := gitCommandRequest(workspace, command)
request.Permission = PermissionAllow
request.PermissionGranted = true
decision := engine.Evaluate(context.Background(), request)
if decision.Action != ActionDeny {
t.Fatalf("%q inside the repository at %s was %s, not denied; the repository it creates gets a writable config and hooks under the workspace grant", command, ancestor, decision.Action)
}
if decision.Block == nil || decision.Block.Code != BlockNestedGitInit {
t.Fatalf("%q block = %#v, want code %s", command, decision.Block, BlockNestedGitInit)
}
}
// CONTROLS: ordinary git operations and the submodule init form stay clear
// of this guard, and a standalone workspace is not governed by anything.
for _, command := range []string{"git status", "git submodule update --init", "git fetch origin"} {
request := gitCommandRequest(workspace, command)
request.Permission = PermissionAllow
request.PermissionGranted = true
if decision := engine.Evaluate(context.Background(), request); decision.Action == ActionDeny && decision.Block != nil && decision.Block.Code == BlockNestedGitInit {
t.Fatalf("%q was refused as nested repository creation; it creates no repository", command)
}
}
standalone := t.TempDir()
if workspaceGovernedByAncestorRepository(standalone) {
t.Fatalf("SETUP INVALID: %s is governed by an ancestor repository", standalone)
}
request := gitCommandRequest(standalone, "git clone https://example.invalid/repo.git .")
request.Permission = PermissionAllow
request.PermissionGranted = true
if decision := gitWorkspaceEngine(t, standalone).Evaluate(context.Background(), request); decision.Block != nil && decision.Block.Code == BlockNestedGitInit {
t.Fatalf("clone into a standalone workspace was refused as nested: %#v", decision)
}
}
// AN INLINE ALIAS IS STILL INIT. The refusal used to read the literal
// subcommand token, and `git -c alias.bootstrap=init bootstrap` passed it with
// shell and network granted and created a repository the profile carves nothing
// out for. The alias is resolved to the subcommand git runs; a chained alias
// follows the chain; a shell alias, which this analyzer cannot classify, counts
// as creation under this guard and nowhere else.
func TestNestedWorkspaceRefusesAnInlineGitAliasForInit(t *testing.T) {
ancestor, workspace := nestedGitWorkspace(t)
policy := DefaultPolicy()
policy.Network = NetworkAllow
engine := NewEngine(EngineOptions{WorkspaceRoot: workspace, Policy: policy, Backend: nativeWrappingBackend})
for _, command := range []string{
"git init",
"git -c alias.bootstrap=init bootstrap",
"git -c alias.mk=init-db mk",
"git -c alias.get=clone get https://example.invalid/repo.git .",
"git -c alias.two=bootstrap -c alias.bootstrap=init two",
"git -c alias.a=b -c alias.b=c -c alias.c=d -c alias.d=e -c alias.e=init a .",
"git -c alias.a=b -c alias.b=a a",
"git -c alias.dangling=nowhere -c alias.nowhere= dangling",
"git -C . -c alias.bootstrap=init bootstrap",
"git -c alias.sh=!sh -c 'git init' sh",
// THE EXPANSION IS PARSED THE WAY GIT PARSES IT. A -c inside the
// expansion defines the alias the next lookup uses, and quotes are
// stripped before the subcommand is read; both of the first two
// spellings created a repository while only the first whitespace
// field of the expansion was classified.
"git -c alias.a='-c alias.b=init b' a .",
"git -c 'alias.a=\"init\"' a .",
"git -c 'alias.a=in\"it\"' a",
"git -c 'alias.a=in\\it' a",
"git -c alias.a='--no-pager init' a",
"git -c alias.a='-c alias.a=init a' a",
// Git dies on these before running anything; refusing them costs
// nothing and keeps the rule that an expansion this analyzer cannot
// read is not evidence of safety.
"git -c 'alias.a=\"in' a",
"git -c 'alias.a=-C . init' a",
// An alias defined by reference, or through the environment the call
// sets, is the same command with its definition moved out of sight.
"git --config-env=alias.a=zz a .",
"git --config-env alias.a=zz a .",
"GIT_CONFIG_COUNT=1 GIT_CONFIG_KEY_0=alias.a GIT_CONFIG_VALUE_0=init git a .",
"env GIT_CONFIG_COUNT=1 GIT_CONFIG_KEY_0=alias.a GIT_CONFIG_VALUE_0=init git a .",
"GIT_CONFIG_PARAMETERS=\"'alias.a=init'\" git a .",
"GIT_CONFIG_PARAMETERS=$params git a .",
"GIT_CONFIG_COUNT=1 GIT_CONFIG_KEY_0=alias.a GIT_CONFIG_VALUE_0=$cmd git a .",
} {
request := gitCommandRequest(workspace, command)
request.Permission = PermissionAllow
request.PermissionGranted = true
decision := engine.Evaluate(context.Background(), request)
if decision.Action != ActionDeny || decision.Block == nil || decision.Block.Code != BlockNestedGitInit {
t.Fatalf("%q inside the repository at %s was not refused as nested repository creation: action=%s block=%#v", command, ancestor, decision.Action, decision.Block)
}
}
// CONTROLS: a harmless alias, an unrelated -c setting, ordinary use, and
// the quoted, option-bearing and environment-defined spellings of an alias
// that runs something harmless.
for _, command := range []string{
"git -c alias.st=status st",
"git -c core.autocrlf=false status",
"git -c alias.bootstrap=init status",
"git -c alias.lg=log lg --oneline",
"git -c alias.a=b -c alias.b=c -c alias.c=d -c alias.d=e -c alias.e=status a",
"git -c alias.st='-c color.ui=always status' st",
"git -c 'alias.st=\"status\"' st",
"git -c 'alias.st=sta\"tus\"' st",
"git -c alias.l='--no-pager log --oneline' l",
"git -c alias.s=st -c 'alias.st=\"status\"' s",
"git --config-env=core.pager=p status",
"GIT_CONFIG_COUNT=1 GIT_CONFIG_KEY_0=alias.st GIT_CONFIG_VALUE_0=status git st",
"GIT_CONFIG_PARAMETERS=\"'alias.st=status'\" git st",
"GIT_CONFIG_COUNT=1 GIT_CONFIG_KEY_0=core.pager GIT_CONFIG_VALUE_0=$pager git log",
} {
request := gitCommandRequest(workspace, command)
request.Permission = PermissionAllow
request.PermissionGranted = true
if decision := engine.Evaluate(context.Background(), request); decision.Action == ActionDeny && decision.Block != nil && decision.Block.Code == BlockNestedGitInit {
t.Fatalf("%q was refused as nested repository creation; it creates no repository", command)
}
}
// And a standalone workspace is not governed at all, alias or not.
standalone := t.TempDir()
for _, command := range []string{
"git -c alias.bootstrap=init bootstrap",
"git -c alias.a='-c alias.b=init b' a .",
"git -c 'alias.a=\"init\"' a .",
"GIT_CONFIG_COUNT=1 GIT_CONFIG_KEY_0=alias.a GIT_CONFIG_VALUE_0=init git a .",
} {
request := gitCommandRequest(standalone, command)
request.Permission = PermissionAllow
request.PermissionGranted = true
if decision := gitWorkspaceEngine(t, standalone).Evaluate(context.Background(), request); decision.Block != nil && decision.Block.Code == BlockNestedGitInit {
t.Fatalf("%q in a standalone workspace was refused as nested: %#v", command, decision)
}
}
}
// THE REFUSAL THAT CANNOT BE APPROVED IS THE ONE THE OPERATOR HAS TO SEE.
//
// `git clone` carries both risks: it uses the network and it creates a
// repository. The clone test above sets NetworkAllow, which is the only policy
// under which the nested-repository branch was ever reached. Under the DEFAULT
// policy the network gate ran first and answered with a prompt, so the operator
// was asked to approve network access for a command no approval could make
// runnable, and ReasonNestedGitInit, the reason with a remedy in it, was never
// shown. Reported by @jatmn.
func TestNestedCloneIsRefusedAsNestedUnderTheDefaultNetworkPolicy(t *testing.T) {
_, workspace := nestedGitWorkspace(t)
policy := DefaultPolicy()
if policy.Network != NetworkDeny {
t.Fatalf("SETUP INVALID: the default network policy is %q, so this does not exercise the ordering", policy.Network)
}
engine := NewEngine(EngineOptions{WorkspaceRoot: workspace, Policy: policy, Backend: nativeWrappingBackend})
for _, granted := range []bool{false, true} {
request := gitCommandRequest(workspace, "git clone https://example.invalid/repo.git vendor/dep")
request.PermissionGranted = granted
decision := engine.Evaluate(context.Background(), request)
if decision.Action != ActionDeny || decision.Block == nil || decision.Block.Code != BlockNestedGitInit {
t.Fatalf("granted=%v: clone in a governed workspace was %s (block %#v, reason %q), want a %s denial", granted, decision.Action, decision.Block, decision.Reason, BlockNestedGitInit)
}
if decision.Reason != ReasonNestedGitInit {
t.Errorf("granted=%v: reason = %q, want the nested-repository reason and its remedy", granted, decision.Reason)
}
}
// CONTROLS. A network command that creates no repository still gets the
// network answer, so the reordering did not swallow that gate, and a clone
// into a standalone workspace is a network question and nothing else.
fetch := engine.Evaluate(context.Background(), gitCommandRequest(workspace, "git fetch origin"))
if fetch.Action != ActionPrompt || fetch.Reason != ReasonNetworkBlocked {
t.Errorf("git fetch in the governed workspace was %s (%q), want the network prompt", fetch.Action, fetch.Reason)
}
standalone := t.TempDir()
if workspaceGovernedByAncestorRepository(standalone) {
t.Fatalf("SETUP INVALID: %s is governed by an ancestor repository", standalone)
}
standaloneEngine := NewEngine(EngineOptions{WorkspaceRoot: standalone, Policy: policy, Backend: nativeWrappingBackend})
clone := standaloneEngine.Evaluate(context.Background(), gitCommandRequest(standalone, "git clone https://example.invalid/repo.git ."))
if clone.Action != ActionPrompt || clone.Reason != ReasonNetworkBlocked {
t.Errorf("clone into a standalone workspace was %s (%q), want the network prompt", clone.Action, clone.Reason)
}
}
// THE LIMIT OF THIS GUARD, WRITTEN DOWN SO IT IS NOT MISTAKEN FOR COVERAGE.
//
// The nested-repository rule recognises git creating a repository. It does not
// recognise a repository assembled by other means, and it cannot: mkdir and a
// few writes, an archive, or a script in any language all produce the same
// directory, and none of them is a git command. These legs are allowed today.
// They are here so that anyone reading the rule as containment of the .git
// pathname finds a test saying otherwise, and so that a change which DOES close
// it at the decision layer has to come and update this deliberately.
//
// It is not a statement that the behaviour is acceptable. A repository built
// this way carries whatever config its author wrote, and a plain `git status`
// outside the sandbox honours it. That has to be closed where the carveouts
// live, at write time. Reported by @jatmn.
func TestHandAssembledRepositoryIsNotWhatThisGuardCatches(t *testing.T) {
_, workspace := nestedGitWorkspace(t)
engine := gitWorkspaceEngine(t, workspace)
for _, command := range []string{
"mkdir .git",
"mkdir -p .git/objects .git/refs && printf 'ref: refs/heads/main\n' > .git/HEAD",
"cp -r ../template-repo/.git .git",
"python3 -c \"import os; os.makedirs('.git/refs')\"",
"tar -xf repo.tar",
} {
decision := engine.Evaluate(context.Background(), gitCommandRequest(workspace, command))
if decision.Block != nil && decision.Block.Code == BlockNestedGitInit {
t.Errorf("%q is now refused as nested repository creation. If that is deliberate, this test and the WHAT THIS IS NOT note in risk.go both need to say what the rule covers now", command)
}
}
}
@@ -0,0 +1,263 @@
package sandbox
import (
"os"
"os/exec"
"path/filepath"
"strings"
"testing"
)
// A WORKSPACE INSIDE ANOTHER REPOSITORY KEEPS ITS CARVEOUTS.
//
// This branch skipped them for a while, so that Zero would not create a .git in
// a repository it does not own. The cost was worse than the thing avoided:
// nothing then denied writes to <root>/.git, so a sandboxed command could build
// a repository there by hand and put core.fsmonitor in its config, and Zero runs
// git outside the sandbox against that workspace. The nested-repository refusal
// recognises git creating a repository; it cannot recognise mkdir.
//
// TestCarveoutsInsideAnAncestorRepositoryDoNotCaptureDiscovery measures the
// reason the skip existed and shows it does not hold.
func TestCarveoutsAreSynthesizedInsideAnAncestorRepository(t *testing.T) {
parent := t.TempDir()
if err := os.MkdirAll(filepath.Join(parent, ".git"), 0o700); err != nil {
t.Fatal(err)
}
workspace := filepath.Join(parent, "sub", "project")
if err := os.MkdirAll(workspace, 0o700); err != nil {
t.Fatal(err)
}
// SETUP: the workspace itself has no .git, or this is a different case.
if _, err := os.Lstat(filepath.Join(workspace, ".git")); err == nil {
t.Fatal("SETUP INVALID: the workspace already carries .git")
}
if !gitMetadataGovernedByAncestor(workspace) {
t.Fatal("SETUP INVALID: the ancestor is not detected, so this proves nothing")
}
specs := gitMetadataWriteCarveoutSpecs(workspace)
want := map[string]bool{
filepath.Join(workspace, ".git", "config"): true,
filepath.Join(workspace, ".git", "hooks"): true,
}
for _, spec := range specs {
delete(want, spec.Path)
}
for path := range want {
t.Errorf("a workspace inside another repository gets no carveout for %s, so nothing denies writing it", path)
}
}
// The reason the skip existed, measured rather than argued: materializing only
// config and hooks does not make the directory a repository, so git's discovery
// walk still reaches the ancestor and a config planted there is never read.
// If a future git changes that, this fails and the trade has to be reopened.
func TestCarveoutsInsideAnAncestorRepositoryDoNotCaptureDiscovery(t *testing.T) {
git, err := exec.LookPath("git")
if err != nil {
t.Skip("no git on PATH")
}
parent := t.TempDir()
run := func(dir string, args ...string) (string, error) {
command := exec.Command(git, args...)
command.Dir = dir
command.Env = append(os.Environ(), "GIT_CONFIG_NOSYSTEM=1", "HOME="+parent, "USERPROFILE="+parent)
out, err := command.CombinedOutput()
return strings.TrimSpace(string(out)), err
}
if out, err := run(parent, "init", "-q", "."); err != nil {
t.Skipf("cannot create the ancestor repository: %v: %s", err, out)
}
workspace := filepath.Join(parent, "sub", "project")
if err := os.MkdirAll(workspace, 0o700); err != nil {
t.Fatal(err)
}
ancestor, err := run(workspace, "rev-parse", "--show-toplevel")
if err != nil {
t.Skipf("cannot resolve the ancestor: %v: %s", err, ancestor)
}
// Materialize exactly what the plan materializes, and make the config as
// hostile as a sandboxed command would if it could write one.
for _, spec := range gitMetadataWriteCarveoutSpecs(workspace) {
if spec.IsFile {
if err := os.MkdirAll(filepath.Dir(spec.Path), 0o700); err != nil {
t.Fatal(err)
}
if err := os.WriteFile(spec.Path, []byte("[core]\n\tfsmonitor = \"exit 9\"\n"), 0o600); err != nil {
t.Fatal(err)
}
continue
}
if err := os.MkdirAll(spec.Path, 0o700); err != nil {
t.Fatal(err)
}
}
after, err := run(workspace, "rev-parse", "--show-toplevel")
if err != nil {
t.Fatalf("git stopped working in the workspace after the carveouts were materialized: %v: %s", err, after)
}
if after != ancestor {
t.Fatalf("discovery moved from %s to %s: the materialized carveouts captured the walk, which is the trade this test exists to watch", ancestor, after)
}
if out, err := run(workspace, "status", "--porcelain"); err != nil {
t.Fatalf("git status failed in the workspace, so the planted config was read: %v: %s", err, out)
}
}
// And a standalone directory keeps the materialized carveouts, or the guard
// above would be satisfied by returning nothing everywhere and the protection
// would be gone for the case it was written for.
func TestCarveoutsStillCoverAStandaloneDirectory(t *testing.T) {
workspace := t.TempDir()
if gitMetadataGovernedByAncestor(workspace) {
t.Skip("this temp directory sits inside a repository, so it is not the standalone case")
}
specs := gitMetadataWriteCarveoutSpecs(workspace)
wantConfig := filepath.Join(workspace, ".git", "config")
wantHooks := filepath.Join(workspace, ".git", "hooks")
var sawConfig, sawHooks bool
for _, spec := range specs {
switch spec.Path {
case wantConfig:
sawConfig = true
if !spec.IsFile {
t.Errorf("%s is planned as a directory; creating .git/config as a directory makes git init fail", spec.Path)
}
case wantHooks:
sawHooks = true
}
}
if !sawConfig || !sawHooks {
t.Fatalf("a standalone directory lost its carveouts: config=%t hooks=%t specs=%+v", sawConfig, sawHooks, specs)
}
}
// A linked worktree is unchanged: the pointer file is denied and nothing beneath
// it is named, which is what keeps elevated setup from descending through a
// regular file.
func TestCarveoutsStillDenyTheLinkedWorktreePointer(t *testing.T) {
workspace := t.TempDir()
pointer := filepath.Join(workspace, ".git")
if err := os.WriteFile(pointer, []byte("gitdir: ../real/.git/worktrees/w\n"), 0o600); err != nil {
t.Fatal(err)
}
specs := gitMetadataWriteCarveoutSpecs(workspace)
if len(specs) != 1 || specs[0].Path != pointer || !specs[0].IsFile {
t.Fatalf("linked worktree carveouts = %+v, want exactly the file-shaped pointer %s", specs, pointer)
}
}
// The ancestor test itself has to distinguish shapes, because a linked worktree
// or submodule ancestor carries .git as a FILE and still owns this directory.
func TestAncestorDetectionAcceptsBothGitShapes(t *testing.T) {
for _, shape := range []struct {
name string
make func(t *testing.T, parent string)
}{
{name: "directory", make: func(t *testing.T, parent string) {
if err := os.MkdirAll(filepath.Join(parent, ".git"), 0o700); err != nil {
t.Fatal(err)
}
}},
{name: "pointer file", make: func(t *testing.T, parent string) {
if err := os.WriteFile(filepath.Join(parent, ".git"), []byte("gitdir: elsewhere\n"), 0o600); err != nil {
t.Fatal(err)
}
}},
} {
t.Run(shape.name, func(t *testing.T) {
parent := t.TempDir()
shape.make(t, parent)
workspace := filepath.Join(parent, "nested", "deep")
if err := os.MkdirAll(workspace, 0o700); err != nil {
t.Fatal(err)
}
if !gitMetadataGovernedByAncestor(workspace) {
t.Fatalf("an ancestor carrying .git as a %s was not recognised as governing %s", shape.name, workspace)
}
})
}
}
// A NESTED WORKSPACE THAT OWNS ITS OWN REPOSITORY KEEPS ITS OWN CARVEOUTS.
//
// The ancestor branch above exists so Zero does not synthesize a control
// directory inside somebody else's repository. It was asked unconditionally,
// so a workspace that already HAS its own .git lost the hooks and config
// carveouts too — and those are its own metadata, not the ancestor's. Nothing
// compensated: workspaceGovernedByAncestorRepository answers the same question
// by testing for a local .git, so it reported this workspace as not governed
// and the initialization refusal never fired. Commands then received plain
// workspace write access over a live .git/config and .git/hooks, which is
// exactly the configuration that decides what git executes. Reported by
// @jatmn.
//
// Asserted through the profile as well as the spec helper, because the spec
// list is only load-bearing if it reaches ReadOnlySubpaths.
func TestNestedWorkspaceOwningGitKeepsItsOwnCarveouts(t *testing.T) {
outer := t.TempDir()
if err := os.MkdirAll(filepath.Join(outer, ".git"), 0o700); err != nil {
t.Fatal(err)
}
workspace := filepath.Join(outer, "project")
if err := os.MkdirAll(filepath.Join(workspace, ".git"), 0o700); err != nil {
t.Fatal(err)
}
wantHooks := filepath.Join(workspace, ".git", "hooks")
wantConfig := filepath.Join(workspace, ".git", "config")
specs := gitMetadataWriteCarveoutSpecs(workspace)
foundHooks, foundConfig := false, false
for _, spec := range specs {
switch {
case spec.Path == wantHooks && !spec.IsFile:
foundHooks = true
case spec.Path == wantConfig && spec.IsFile:
foundConfig = true
}
}
if !foundHooks || !foundConfig {
t.Fatalf("a workspace owning its own .git lost its carveouts: hooks=%v config=%v specs=%+v",
foundHooks, foundConfig, specs)
}
// The specs only matter if they reach the profile the runner enforces.
profile := PermissionProfileFromPolicy(workspace, DefaultPolicy(), nil)
var root *WritableRoot
for index := range profile.FileSystem.WriteRoots {
if sameGitTestPath(profile.FileSystem.WriteRoots[index].Root, workspace) {
root = &profile.FileSystem.WriteRoots[index]
break
}
}
if root == nil {
t.Fatalf("no writable root for the workspace: %+v", profile.FileSystem.WriteRoots)
}
for _, want := range []string{wantHooks, wantConfig} {
covered := false
for _, sub := range root.ReadOnlySubpaths {
if sameGitTestPath(sub, want) {
covered = true
break
}
}
if !covered {
t.Errorf("%s is not read-only in the workspace write root: %+v", want, root.ReadOnlySubpaths)
}
}
}
// Compared through the profile's own canonicalization. PermissionProfileFromPolicy
// stores normalizeProfilePath(root), which resolves symlinks, so a raw t.TempDir()
// path does not match it on a runner where the temp directory is reached through
// one: macOS /var -> /private/var, and the Windows short-name expansion of the
// runner's profile directory. Comparing cleaned strings passed locally and failed
// on both CI runners for that reason alone.
func sameGitTestPath(a, b string) bool {
return normalizeProfilePath(a) == normalizeProfilePath(b)
}
@@ -0,0 +1,119 @@
//go:build windows
package sandbox
import (
"os"
"path/filepath"
"testing"
)
func pointerWorkspace(t *testing.T) (workspace string, pointer string) {
t.Helper()
workspace = t.TempDir()
pointer = filepath.Join(workspace, ".git")
if err := os.WriteFile(pointer, []byte("gitdir: ../real/.git/worktrees/w\n"), 0o600); err != nil {
t.Fatal(err)
}
return workspace, pointer
}
func pointerPlanConfig(t *testing.T, workspace string) WindowsSandboxCommandConfig {
t.Helper()
return WindowsSandboxCommandConfig{
SandboxHome: t.TempDir(),
CommandCWD: workspace,
WorkspaceRoots: []string{workspace},
PermissionProfile: PermissionProfile{
FileSystem: FileSystemPolicy{
Kind: FileSystemRestricted,
WriteRoots: []WritableRoot{{
Root: workspace,
ReadOnlySubpaths: gitMetadataWriteCarveouts(workspace),
ProtectedMetadataNames: sandboxFullyProtectedMetadataNames,
}},
},
},
}
}
// THE SHAPE HAS TO SURVIVE THE STAGE BOUNDARY, NOT JUST BE CORRECT AT STAGE ONE.
//
// gitMetadataWriteCarveoutSpecs types a linked worktree's .git as a file. That
// typed result was flattened to a path before ACL planning, and the planner tried
// to recover the shape by deriving suffixes under a sentinel root whose .git never
// exists. The derivation therefore always took the directory branch, and a bare
// <root>\.git could never match as a file.
//
// The window that turns a wrong plan into damage is the caller-to-elevated-helper
// gap: the profile is built in the user's shell and the plan is applied in a
// separately launched helper, across the UAC prompt. If the pointer goes away in
// between, the applier materializes a DIRECTORY at the pointer path and the
// worktree is broken, persistently, because the runner discards the rollback.
//
// Driven through BuildWindowsACLPlan and applyWindowsACLPlan with the pointer
// removed after planning, which is the only place this is visible. A stage-one
// assertion on specs[0].IsFile passed throughout the whole time the bug was live.
func TestALinkedWorktreePointerIsNeverMaterializedAsADirectory(t *testing.T) {
workspace, pointer := pointerWorkspace(t)
plan, err := BuildWindowsACLPlan(pointerPlanConfig(t, workspace))
if err != nil {
t.Fatalf("BuildWindowsACLPlan: %v", err)
}
// SETUP: the plan really does carry the pointer, typed as a file.
var found bool
for _, entry := range plan.Entries {
if entry.Path == pointer && entry.Action == WindowsACLDenyWrite {
found = true
if !entry.MaterializeFile {
t.Fatalf("the plan types %s as a directory; applying it would replace the worktree pointer with a directory", pointer)
}
}
}
if !found {
t.Fatalf("SETUP INVALID: no deny-write entry for the pointer %s: %+v", pointer, plan.Entries)
}
// The window: the pointer goes away between planning and applying.
if err := os.Remove(pointer); err != nil {
t.Fatal(err)
}
if _, err := applyWindowsACLPlan(plan); err != nil {
t.Skipf("cannot apply an ACL plan here: %v", err)
}
info, err := os.Lstat(pointer)
if err != nil {
// Nothing recreated is also acceptable: what must not happen is a directory.
return
}
if info.IsDir() {
t.Fatalf("a directory was created at the worktree pointer %s, which breaks the worktree", pointer)
}
}
// Control: with the pointer present at apply, it stays a file and is not
// replaced. Without this, the assertion above could be satisfied by an apply
// that does nothing at all.
func TestALinkedWorktreePointerSurvivesAnApply(t *testing.T) {
workspace, pointer := pointerWorkspace(t)
plan, err := BuildWindowsACLPlan(pointerPlanConfig(t, workspace))
if err != nil {
t.Fatalf("BuildWindowsACLPlan: %v", err)
}
if _, err := applyWindowsACLPlan(plan); err != nil {
t.Skipf("cannot apply an ACL plan here: %v", err)
}
info, err := os.Lstat(pointer)
if err != nil {
t.Fatalf("the pointer vanished across the apply: %v", err)
}
if info.IsDir() {
t.Fatalf("the pointer at %s became a directory", pointer)
}
body, err := os.ReadFile(pointer)
if err != nil || len(body) == 0 {
t.Fatalf("the pointer lost its contents: body=%q err=%v", body, err)
}
}
+195 -14
View File
@@ -96,28 +96,209 @@ var protectedMetadataNames = []string{".git", ".zero", ".agents"}
// gitMetadataWriteCarveouts below.
var sandboxFullyProtectedMetadataNames = []string{".zero", ".agents"}
// gitMetadataWriteCarveouts returns the .git paths that stay write-denied under
// the OS-level sandbox even though the rest of .git is writable to git
// subprocesses. Worktrees and submodules store .git as a regular pointer file,
// so they protect that file itself: constructing .git/hooks below it makes
// bwrap fail before the command starts. All other entry and error states retain
// the legacy child paths. The pointer is deliberately not parsed here;
// repository-controlled metadata must not redirect sandbox rules elsewhere.
// sandboxRenameProtectedMetadataName is the metadata directory that cannot be
// fully write-protected but must still not be REPLACEABLE.
//
// It is deliberately not in the list above. That list denies write, and git has
// to write index, objects and refs. But the carveouts guarding it are attached
// to .git/config and .git/hooks as objects, so a principal that renames .git and
// recreates it gets fresh paths inheriting the workspace allow with no denies,
// which restores credential.helper and core.hooksPath. The Windows ACL plan
// therefore denies DELETE on this directory alone, uninherited.
const sandboxRenameProtectedMetadataName = ".git"
// gitMetadataWriteCarveouts returns the .git subpaths that stay write-denied
// under the OS-level sandbox even though the rest of .git is writable to git
// subprocesses. Nonexistent paths are harmless no-ops in every backend's
// enforcement (seatbelt regex, bwrap ro-bind, Windows ACL deny entry).
func gitMetadataWriteCarveouts(root string) []string {
return gitMetadataWriteCarveoutsWithLstat(root, os.Lstat)
}
// gitMetadataWriteCarveoutsWithLstat is the seam the worktree tests drive.
// Which carveouts apply is decided by the SHAPE of .git, and a test cannot
// create every shape it needs to cover: an lstat that fails is a real state
// (a racing checkout, a permission error) with its own required answer, and
// there is no filesystem it can be staged on.
func gitMetadataWriteCarveoutsWithLstat(root string, lstat func(string) (os.FileInfo, error)) []string {
specs := gitMetadataWriteCarveoutSpecsWithLstat(root, lstat)
out := make([]string, 0, len(specs))
for _, spec := range specs {
out = append(out, spec.Path)
}
return out
}
// gitMetadataCarveout is a write-denied .git path together with the shape git
// expects it to have. The shape matters to exactly one backend: the Windows ACL
// plan creates a missing carveout so the deny ACE is in place before git first
// runs, and creating .git/config as a directory makes `git init` fail outright.
// Every other backend only ever names the path, so it can ignore IsFile.
type gitMetadataCarveout struct {
Path string
IsFile bool
}
// gitMetadataWriteCarveoutSpecs is the single source of truth for the carveout
// set. gitMetadataWriteCarveouts derives its list from this so a path can never
// be added in one place and have its shape forgotten in the other.
func gitMetadataWriteCarveoutSpecs(root string) []gitMetadataCarveout {
return gitMetadataWriteCarveoutSpecsWithLstat(root, os.Lstat)
}
func gitMetadataWriteCarveoutSpecsWithLstat(root string, lstat func(string) (os.FileInfo, error)) []gitMetadataCarveout {
gitPath := filepath.Join(root, ".git")
children := []string{
filepath.Join(gitPath, "hooks"),
filepath.Join(gitPath, "config"),
// A LINKED WORKTREE OR SUBMODULE HAS .git AS A FILE, NOT A DIRECTORY.
//
// It holds a `gitdir:` pointer to the real control directory, which lives
// outside this write root. Naming .git/config and .git/hooks there asks the
// Windows plan to materialize them by descending through .git as a directory,
// which cannot open a child beneath a regular file, so opted-in elevated setup
// aborts and the sandbox is unusable in any worktree. Zero's own development
// worktrees are exactly this shape.
//
// Deny the pointer file itself instead. It is the right protection rather than
// a lesser one: a principal that can rewrite `gitdir:` repoints the whole
// repository at a control directory it chooses, which subsumes editing config
// or dropping a hook. The real control directory is outside the write root, so
// the principal has no inherited access to it and needs no carveout there.
//
// Stat, not a lexical guess. Whether .git is a file is a property of the
// checkout, and the two layouts want different ACEs. A missing .git (git has
// not run yet) keeps the directory-shaped carveouts, which is what makes them
// materialize before git first runs.
//
// A REGULAR FILE, NOT MERELY A NON-DIRECTORY. The pointer this recognises is
// the `gitdir:` file git writes for a linked worktree or submodule. A symlink
// named .git, dangling or not, and a special entry such as a fifo are neither
// that nor a checkout git will use, so they keep the legacy child carveouts
// rather than being handed the stronger single-object protection on the
// strength of not being a directory.
gitInfo, gitErr := lstat(gitPath)
if gitErr == nil && gitInfo.Mode().IsRegular() {
return []gitMetadataCarveout{{Path: gitPath, IsFile: true}}
}
info, err := lstat(gitPath)
if err != nil || !info.Mode().IsRegular() {
return children
// EVERY WRITE ROOT GETS THE CARVEOUTS, INCLUDING ONE INSIDE ANOTHER REPOSITORY.
//
// The directory-shaped carveouts below are materialized by the Windows plan so
// the deny ACE is in place before git first runs. For a while this branch
// skipped them when an ancestor owned the git metadata, on the argument that
// creating .git/config and .git/hooks there synthesizes a control directory
// competing with the ancestor's for git's discovery walk. Measured against the
// git this repository builds against, it does not: a .git holding only config
// and hooks is not a valid repository, so `rev-parse --show-toplevel` still
// answers with the ancestor, `status` still works, and a core.fsmonitor
// written into that config is never executed. The test named below drives real
// git and fails if that ever stops being true.
//
// Skipping them cost much more than it saved. With no carveout on this root
// nothing denies writes to <root>/.git at all, so a sandboxed command can
// assemble a repository there by hand, with mkdir and a few file writes and
// not one git command among them, and put core.fsmonitor in its config. Zero
// then runs `git -C <workspace> status` OUTSIDE the sandbox (scratch_files.go,
// internal/repoinfo, internal/zerogit) and git executes it. The nested-repository
// refusal in risk.go does not cover that and cannot: no static reading of a
// shell command enumerates the ways to create a directory. It stays as the
// layer that explains itself to an operator, not as the boundary.
//
// So the boundary is here, where it is enforced at write time: config and
// hooks are denied on every write root, whatever owns the metadata above it.
return []gitMetadataCarveout{
{Path: filepath.Join(root, ".git", "hooks")},
{Path: filepath.Join(root, ".git", "config"), IsFile: true},
}
return []string{gitPath}
}
// workspaceGovernedByAncestorRepository is the same question the carveouts ask,
// named for the caller that asks it about a whole workspace rather than about
// one write root. Sharing the rule is the point: the reason a workspace gets no
// carveouts is exactly the reason it may not create a repository.
func workspaceGovernedByAncestorRepository(workspaceRoot string) bool {
cleaned := strings.TrimSpace(workspaceRoot)
if cleaned == "" {
return false
}
if _, err := os.Lstat(filepath.Join(cleaned, ".git")); err == nil {
// It already owns git metadata, so setup protected it and nothing here is
// being created inside a repository that is not this workspace's.
return false
}
return gitMetadataGovernedByAncestor(cleaned)
}
// gitMetadataGovernedByAncestor reports whether an ancestor of root carries git
// metadata, which is git's own discovery rule: the nearest ancestor with a .git
// entry owns this directory.
//
// Lstat rather than a resolved walk, because a .git of either shape answers the
// question: a directory is an ordinary repository root and a file is a linked
// worktree or submodule pointer. Both mean the metadata is not ours to create.
func gitMetadataGovernedByAncestor(root string) bool {
current := filepath.Clean(strings.TrimSpace(root))
if current == "" || current == "." {
return false
}
for {
parent := filepath.Dir(current)
if parent == current {
return false
}
if _, err := os.Lstat(filepath.Join(parent, ".git")); err == nil {
return true
}
current = parent
}
}
// gitMetadataCarveoutSuffixBase is a sentinel root used only to recover the
// trailing segments of the carveout specs. It is never touched on disk.
const gitMetadataCarveoutSuffixBase = string(filepath.Separator) + "zero-carveout-base"
// gitMetadataCarveoutIsFile reports whether path names a carveout git expects
// to be a file.
//
// It matches on the trailing segments rather than on a whole reconstructed
// path. The subpaths reaching the ACL plan are already normalized — resolved
// through EvalSymlinks where that succeeds — while a rebuilt spec path cannot
// be, because .git/config does not exist yet at setup and resolution falls back
// to a plain Clean. On a host where two spellings of the same path differ (an
// 8.3 short name, different casing) a whole-path equality check silently misses
// and the carveout is created as a directory again, which is the original bug
// reintroduced quietly. The suffix cannot drift from the spec list because it
// is derived from it.
func gitMetadataCarveoutIsFile(path string) bool {
candidate := strings.ToLower(filepath.Clean(strings.TrimSpace(path)))
if candidate == "" {
return false
}
// A BARE .git CARVEOUT IS THE LINKED-WORKTREE POINTER, AND ONLY THAT.
//
// The suffix derivation below runs specs against a sentinel root whose .git
// never exists, so it always takes the directory branch and yields exactly one
// file-shaped suffix, .gitconfig. A bare <root>.git could therefore never
// match, and both planners emitted MaterializeFile:false for a path the profile
// stage had already typed correctly as a file. With the pointer absent at apply
// time, the plan then created a DIRECTORY at the pointer path and broke the
// worktree.
//
// The carveout SET already carries the answer. gitMetadataWriteCarveoutSpecs is
// the only producer of ReadOnlySubpaths, and it emits a bare .git in exactly one
// case: the linked-worktree or submodule pointer. The directory case emits
// .githooks and .gitconfig and never the parent. So the shape is not being
// guessed from a pathname here, it is being read off which carveout this is.
if strings.EqualFold(filepath.Base(candidate), ".git") {
return true
}
for _, spec := range gitMetadataWriteCarveoutSpecs(gitMetadataCarveoutSuffixBase) {
if !spec.IsFile {
continue
}
suffix := strings.ToLower(strings.TrimPrefix(spec.Path, gitMetadataCarveoutSuffixBase))
if suffix != "" && strings.HasSuffix(candidate, suffix) {
return true
}
}
return false
}
func PermissionProfileFromPolicy(workspaceRoot string, policy Policy, scope *Scope) PermissionProfile {
+79
View File
@@ -0,0 +1,79 @@
package sandbox
import (
"os"
"path/filepath"
"strings"
"testing"
)
// A LINKED WORKTREE HAS .git AS A FILE.
//
// The Windows principal plan materializes every carveout, and it does so by
// descending through .git as a directory. Against a `gitdir:` pointer file that
// walk cannot open a child, so opted-in elevated setup aborts and the sandbox
// cannot be used in a worktree at all. Zero's own development worktrees have
// exactly this layout, so this is the common case for anyone working on the
// sandbox itself.
func TestGitCarveoutsHandleAWorktreeGitfile(t *testing.T) {
root := t.TempDir()
gitFile := filepath.Join(root, ".git")
// The real shape git writes for a linked worktree.
if err := os.WriteFile(gitFile, []byte("gitdir: "+filepath.Join(root, "..", "main", ".git", "worktrees", "wt")+"\n"), 0o600); err != nil {
t.Fatalf("WriteFile: %v", err)
}
specs := gitMetadataWriteCarveoutSpecs(root)
if len(specs) != 1 {
t.Fatalf("carveout specs = %#v, want only the .git pointer file", specs)
}
if filepath.Clean(specs[0].Path) != filepath.Clean(gitFile) {
t.Fatalf("carveout path = %s, want the .git pointer file %s", specs[0].Path, gitFile)
}
if !specs[0].IsFile {
t.Fatal("the .git pointer carveout is not marked as a file, so materialization would create a directory where git needs a file")
}
// Nothing may name a path BENEATH the pointer file, which is what forces the
// directory descent that aborts setup.
for _, path := range gitMetadataWriteCarveouts(root) {
rest := strings.TrimPrefix(filepath.Clean(path), filepath.Clean(gitFile))
if rest != "" {
t.Errorf("carveout %s descends through the .git pointer file, which cannot have children", path)
}
}
}
// The ordinary repository layout must keep the config and hooks carveouts. They
// are the whole reason the set exists: without them a principal reinstates
// credential.helper or core.hooksPath through inherited workspace write access.
func TestGitCarveoutsKeepConfigAndHooksForARealGitDir(t *testing.T) {
root := t.TempDir()
if err := os.MkdirAll(filepath.Join(root, ".git"), 0o700); err != nil {
t.Fatalf("MkdirAll: %v", err)
}
paths := gitMetadataWriteCarveouts(root)
for _, want := range []string{filepath.Join(root, ".git", "hooks"), filepath.Join(root, ".git", "config")} {
found := false
for _, got := range paths {
if filepath.Clean(got) == filepath.Clean(want) {
found = true
break
}
}
if !found {
t.Errorf("carveout %s missing for an ordinary .git directory: %#v", want, paths)
}
}
}
// A workspace where git has never run keeps the directory-shaped carveouts. That
// is what lets the Windows plan create them before git first runs, so the deny
// ACEs are already in place rather than being applied to paths git will create
// later with inherited write access.
func TestGitCarveoutsKeepConfigAndHooksWhenGitIsAbsent(t *testing.T) {
root := t.TempDir()
paths := gitMetadataWriteCarveouts(root)
if len(paths) != 2 {
t.Fatalf("carveouts = %#v, want the config and hooks pair when .git is absent", paths)
}
}
+39
View File
@@ -135,6 +135,45 @@ func classifyWithScope(request Request, scope *Scope) Risk {
if analysis.Destructive {
add("destructive", RiskCritical)
}
// A REPOSITORY CREATED INSIDE SOMEBODY ELSE'S IS NOT PROTECTABLE LATER.
//
// gitMetadataWriteCarveoutSpecs returns NOTHING for a workspace governed by
// an ancestor repository, on every backend. That is deliberate: naming
// <root>/.git/config and <root>/.git/hooks makes the Windows plan create a
// control directory, and the bubblewrap helper mount one, that competes with
// the ancestor's for git's discovery walk inside a repository Zero does not
// own. So the workspace carries no config or hooks protection at all.
//
// A repository created here DURING the command therefore lands under the
// plain workspace write grant with nothing denying credential.helper or
// core.hooksPath, and on Windows nothing denying DELETE on .git either. The
// serialized plan never changed, so the cached setup marker stays valid and
// the next run will not notice.
//
// Refused rather than protected, because the protection would have to be
// established at a moment the sandbox is no longer at.
//
// WHAT THIS IS NOT. It refuses GIT creating a repository, by every spelling
// git offers. It is not containment of the .git pathname. A command that
// assembles a repository by other means (mkdir and a few file writes, an
// archive, a script in any language) is not recognised here, and no static
// reading of a shell command can recognise all of them, so this rule must
// not be described or relied on as the boundary. A repository assembled
// that way carries whatever config its author wrote, and an ordinary
// `git status` run outside the sandbox honours it, core.fsmonitor included.
// Closing that is the carveouts' job, at write time, not this rule's.
// TestHandAssembledRepositoryIsNotWhatThisGuardCatches pins the limit so it
// cannot be mistaken for coverage. Reported by @jatmn.
//
// The condition is the WORKSPACE, not the directory the command names.
// Resolving that directory would mean tracking -C and cwd through the
// script, which is precisely the option-parsing surface that let
// "git -C sub clone" past the network gate. Refusing a git init outside the
// workspace too is the conservative side of that trade, and the reason text
// says so.
if analysis.GitInit && workspaceGovernedByAncestorRepository(request.WorkspaceRoot) {
add("nested_git_init", RiskCritical)
}
if analysis.TooComplex {
add("unparseable_command", RiskHigh)
}
@@ -36,10 +36,14 @@ func TestWindowsRestrictedTokenRealSandboxSmoke(t *testing.T) {
Network: NetworkPolicy{Mode: NetworkDeny},
}
config := WindowsSandboxCommandArgsOptions{
SandboxHome: sandboxHome,
CommandCWD: root,
WorkspaceRoots: []string{root},
PermissionProfile: profile,
SandboxHome: sandboxHome,
CommandCWD: root,
WorkspaceRoots: []string{root},
// The setup builder folds the runtime roots into its profile before the
// helper sees it; the command builder does not. Passing the bare profile
// here made every command disagree with the marker setup wrote, nine
// entries against five, before the first write probe ran.
PermissionProfile: WindowsSandboxProfileWithRuntimeRoots(profile, []string{root}),
SandboxLevel: WindowsSandboxLevelRestrictedToken,
}
runWindowsRealSmokeSetup(t, setupExe, WindowsSandboxSetupArgsOptions{
@@ -393,6 +397,15 @@ func realSmokeExecutable(t *testing.T, envKey string, fallbackName string) strin
func runWindowsRealSmokeSetup(t *testing.T, setupExe string, options WindowsSandboxSetupArgsOptions) {
t.Helper()
// options.PrincipalOptIn is deliberately left nil by both call sites, which
// makes BuildWindowsSandboxSetupArgs resolve the opt-in from this process's
// environment — the same value the command half resolves, since the smoke
// WindowsSandboxCommandArgsOptions carries no explicit entry either. Do not
// "fix" this by setting it to false: anyone running this suite with
// ZERO_WINDOWS_SANDBOX_IDENTITY=1 (the only way to exercise the principal
// backend) would then serialize `--sandbox-principal 0`, disagree with the
// command half, and fail every command at marker validation instead of
// testing the sandbox.
args, err := BuildWindowsSandboxSetupArgs(options)
if err != nil {
t.Fatalf("BuildWindowsSandboxSetupArgs: %v", err)
@@ -0,0 +1,33 @@
//go:build !windows
package sandbox
import (
"os"
"path/filepath"
)
// physicalTempDir returns os.TempDir with every symlink in its ancestry
// resolved, so the fallback anchor's parent chain is physical and only the
// anchor itself is a new component.
//
// peermsg.EnsurePrivateDir walks from the root with O_NOFOLLOW and refuses any
// component that is a link. That is right for the owned tail and wrong for the
// ancestors above it: on macOS os.TempDir lives under /var, which is a symlink
// to /private/var, so the first version of this fix refused every fallback on
// every Mac with "refusing non-directory or symlink runtime path component
// var". The constraint jatmn stated for #901 applies here identically:
// redirected cache and TEMP locations above the owned tail are the operator's
// business and must keep working; the restriction is on what Zero owns.
//
// EvalSymlinks is the correct resolver off Windows, where the only reparse
// shape is a symlink and it traverses them.
func physicalTempDir() (string, error) {
return physicalDir(os.TempDir())
}
// physicalDir resolves any directory the same way, for the other places that
// have to hand EnsurePrivateDir a physical parent.
func physicalDir(path string) (string, error) {
return filepath.EvalSymlinks(path)
}
@@ -0,0 +1,63 @@
//go:build windows
package sandbox
import (
"fmt"
"os"
"golang.org/x/sys/windows"
)
// physicalTempDir returns os.TempDir as the object it actually names, so the
// fallback anchor's parent chain is physical and only the anchor itself is a
// new component.
//
// peermsg.EnsurePrivateDir walks from the volume root with OBJ_DONT_REPARSE and
// refuses any component that is a reparse point. That is right for the owned
// tail and wrong for the ancestors above it: a redirected %LOCALAPPDATA% is an
// ordinary Windows configuration, and TEMP sits beneath it. The constraint
// jatmn stated for #901 applies here identically: redirected cache and TEMP
// locations above the owned tail must keep working; the restriction is on what
// Zero owns.
//
// GetFinalPathNameByHandle rather than filepath.EvalSymlinks, because
// EvalSymlinks does not traverse a junction on Windows: it returns the
// junction's own path and the walker then refuses it. The handle answers where
// the directory actually is. Same recipe as verifyWindowsACLTargetNotRedirected,
// which is why the flag constants and the prefix trim are shared.
func physicalTempDir() (string, error) {
return physicalDir(os.TempDir())
}
// physicalDir resolves any directory through a handle, for the other places
// that have to hand EnsurePrivateDir a physical parent. GetFinalPathNameByHandle
// rather than EvalSymlinks, because EvalSymlinks does not traverse a junction.
func physicalDir(path string) (string, error) {
utf16Path, err := windows.UTF16PtrFromString(path)
if err != nil {
return "", fmt.Errorf("encode directory %s: %w", path, err)
}
handle, err := windows.CreateFile(
utf16Path,
windows.FILE_READ_ATTRIBUTES|windows.SYNCHRONIZE,
windows.FILE_SHARE_READ|windows.FILE_SHARE_WRITE|windows.FILE_SHARE_DELETE,
nil,
windows.OPEN_EXISTING,
windows.FILE_FLAG_BACKUP_SEMANTICS,
0,
)
if err != nil {
return "", fmt.Errorf("open directory %s: %w", path, err)
}
defer windows.CloseHandle(handle)
buffer := make([]uint16, windows.MAX_LONG_PATH)
n, err := windows.GetFinalPathNameByHandle(handle, &buffer[0], uint32(len(buffer)), windowsFileNameNormalized|windowsVolumeNameDOS)
if err != nil {
return "", fmt.Errorf("resolve directory %s: %w", path, err)
}
if int(n) < len(buffer) {
buffer = buffer[:n]
}
return trimWindowsExtendedPathPrefix(windows.UTF16ToString(buffer)), nil
}
@@ -0,0 +1,157 @@
//go:build windows
package sandbox
import (
"os"
"os/exec"
"path/filepath"
"strings"
"testing"
)
// DETERMINISM IS NOT OWNERSHIP.
//
// The fallback runtime root moved from a fresh os.MkdirTemp parent to a
// predictable name so that elevated setup and the later command agree on it.
// That is required. But a predictable path beneath the shared system temp is
// not a private allocation: whatever another local user, or a stray earlier
// process, has already placed at that name is what preparation then leases,
// creates, chmods and cleans through. The anchor beneath which the tree lives
// must therefore be proven to be this user's private directory before anything
// is built under it, on BOTH paths that can hand back a fallback root.
//
// Junctions need no privilege on Windows, so the "attacker-precreated parent"
// jatmn described is modelled as a junction at the anchor pointing into a
// directory the test owns and watches. Either trigger must refuse, and the
// watched directory must stay empty.
// fallbackAnchorFixture redirects TEMP so the anchor lands inside a directory
// this test owns, plants a junction at the anchor into a watched target, and
// returns the target. The junction is the shape that defeats a pathname walk:
// it is not a symlink to os.ModeSymlink, and EvalSymlinks will not traverse it.
func fallbackAnchorFixture(t *testing.T) (target string) {
t.Helper()
tempRoot := t.TempDir()
target = t.TempDir()
t.Setenv("TMP", tempRoot)
t.Setenv("TEMP", tempRoot)
// The anchor's parent is the PHYSICAL temp dir, so compare against the
// resolved form of the redirect rather than its spelling: t.TempDir can
// come back as an 8.3 short name or in a different case from what the
// handle reports, and a prefix check on the raw string would fail for a
// correct anchor.
anchor := fallbackRuntimeAnchor()
resolvedTempRoot, err := physicalTempDir()
if err != nil {
t.Fatalf("SETUP INVALID: cannot resolve the redirected TEMP %s: %v", tempRoot, err)
}
if !pathWithinRoot(resolvedTempRoot, anchor) {
t.Fatalf("SETUP INVALID: anchor %s is not under the redirected TEMP %s (resolved %s)", anchor, tempRoot, resolvedTempRoot)
}
if out, err := exec.Command("cmd", "/c", "mklink", "/J", anchor, target).CombinedOutput(); err != nil {
t.Fatalf("mklink /J: %v\n%s", err, out)
}
return target
}
func assertNothingUnder(t *testing.T, target string) {
t.Helper()
entries, err := os.ReadDir(target)
if err != nil {
t.Fatal(err)
}
if len(entries) != 0 {
names := make([]string, 0, len(entries))
for _, entry := range entries {
names = append(names, entry.Name())
}
t.Errorf("preparation built %v beneath the junction target, which is somebody else's directory", names)
}
}
// Trigger one: the user cache resolves INSIDE the workspace, so
// sandboxRuntimeRootFor itself returns the fallback root and the first lease
// attempt is already against it.
func TestFallbackAnchorIsRefusedWhenTheCacheLandsInsideTheWorkspace(t *testing.T) {
isolateSandboxRuntimeRoots(t)
target := fallbackAnchorFixture(t)
workspace := t.TempDir()
previous := sandboxUserCacheDir
t.Cleanup(func() { sandboxUserCacheDir = previous })
sandboxUserCacheDir = func() (string, error) { return filepath.Join(workspace, ".cache"), nil }
_, release, err := prepareSandboxRuntime(workspace)
if err == nil {
release()
t.Fatal("preparation went through a junction at the fallback anchor and reported success")
}
if !strings.Contains(err.Error(), "fallback anchor") {
t.Errorf("the refusal does not name the anchor, so the operator cannot act on it: %v", err)
}
assertNothingUnder(t, target)
}
// Trigger two: the cache root cannot be leased (a FILE sits where the cache
// runtime tree would go), so preparation falls back explicitly.
func TestFallbackAnchorIsRefusedWhenTheCacheRootCannotBeLeased(t *testing.T) {
isolateSandboxRuntimeRoots(t)
target := fallbackAnchorFixture(t)
workspace := t.TempDir()
// Make the cache-derived root unleasable at its ROOT: the user cache is a
// regular file, so nothing beneath it can be created and the first lease
// fails, which is the path that asks for the fallback explicitly. The
// first draft planted the file at the derived leaf instead, and the
// preparation failed on that mkdir before ever reaching the fallback
// branch, so the trigger under test never fired.
cache := filepath.Join(t.TempDir(), "cache-is-a-file")
if err := os.WriteFile(cache, []byte("not a directory"), 0o600); err != nil {
t.Fatal(err)
}
previous := sandboxUserCacheDir
t.Cleanup(func() { sandboxUserCacheDir = previous })
sandboxUserCacheDir = func() (string, error) { return cache, nil }
_, release, err := prepareSandboxRuntime(workspace)
if err == nil {
release()
t.Fatal("preparation fell back through a junction at the anchor and reported success")
}
if !strings.Contains(err.Error(), "fallback anchor") {
t.Errorf("the refusal does not name the anchor: %v", err)
}
assertNothingUnder(t, target)
}
// And the honest control: with nothing planted, the fallback prepares, the
// anchor is a real directory this test can see, and the runtime tree sits
// beneath it.
func TestFallbackAnchorIsCreatedPrivatelyWhenNothingIsInTheWay(t *testing.T) {
tempRoot := t.TempDir()
t.Setenv("TMP", tempRoot)
t.Setenv("TEMP", tempRoot)
workspace := t.TempDir()
previous := sandboxUserCacheDir
t.Cleanup(func() { sandboxUserCacheDir = previous })
sandboxUserCacheDir = func() (string, error) { return filepath.Join(workspace, ".cache"), nil }
runtimeState, release, err := prepareSandboxRuntime(workspace)
if err != nil {
t.Fatalf("a clean fallback was refused: %v", err)
}
defer release()
anchor := fallbackRuntimeAnchor()
info, err := os.Lstat(anchor)
if err != nil || !info.IsDir() {
t.Fatalf("the anchor was not created as a directory: err=%v", err)
}
if !pathWithinRoot(anchor, runtimeState.Root) {
t.Errorf("runtime root %s is not beneath the anchor %s", runtimeState.Root, anchor)
}
}
+85
View File
@@ -0,0 +1,85 @@
package sandbox
import (
"path/filepath"
"strings"
"testing"
)
// SETUP AND EVERY COMMAND RUNNER MUST DERIVE THE SAME FALLBACK ROOT.
//
// They are separate processes. The fallback used to call os.MkdirTemp and cache
// the answer in a process-global map, so elevated setup granted the sandbox
// principal write access to the directory IT made, and each later
// __windows-command-runner made a different one and pointed TMP, GOCACHE and npm
// there. Those directories are created by the calling user and carry no ACE for
// the principal, so ordinary cache writes failed with a bare ACCESS_DENIED.
//
// A repeated call is what a second process looks like from here: no shared
// state, same inputs. The old implementation could not pass this, because the
// only thing that made repeat calls agree was the in-process map.
func TestFallbackRuntimeRootIsTheSameForEveryProcess(t *testing.T) {
workspace := filepath.Join(t.TempDir(), "ws")
first, err := fallbackSandboxRuntimeRoot(workspace)
if err != nil {
t.Fatalf("fallbackSandboxRuntimeRoot: %v", err)
}
second, err := fallbackSandboxRuntimeRoot(workspace)
if err != nil {
t.Fatalf("fallbackSandboxRuntimeRoot (second process): %v", err)
}
if first != second {
t.Fatalf("two processes derived different runtime roots, so setup grants one and commands write to another:\n %s\n %s", first, second)
}
if first == "" {
t.Fatal("no runtime root derived")
}
}
// Different workspaces must not share a runtime tree, or one workspace's
// principal would hold an ACE on another's caches.
func TestFallbackRuntimeRootIsPerWorkspace(t *testing.T) {
base := t.TempDir()
first, err := fallbackSandboxRuntimeRoot(filepath.Join(base, "alpha"))
if err != nil {
t.Fatal(err)
}
second, err := fallbackSandboxRuntimeRoot(filepath.Join(base, "beta"))
if err != nil {
t.Fatal(err)
}
if first == second {
t.Fatalf("two workspaces share the runtime root %q", first)
}
}
// It must NAME the tree without creating it. Teardown asks for this path on its
// way out, and materializing a directory there would leave one behind on every
// teardown.
func TestFallbackRuntimeRootCreatesNothing(t *testing.T) {
workspace := filepath.Join(t.TempDir(), "ws")
root, err := fallbackSandboxRuntimeRoot(workspace)
if err != nil {
t.Fatal(err)
}
if pathExists(root) {
t.Errorf("naming the runtime root created %s", root)
}
}
// The root must land outside the workspace, which is the entire reason this
// branch exists.
func TestFallbackRuntimeRootStaysOutsideTheWorkspace(t *testing.T) {
workspace := filepath.Join(t.TempDir(), "ws")
root, err := fallbackSandboxRuntimeRoot(workspace)
if err != nil {
t.Fatal(err)
}
if pathWithinRoot(workspace, root) {
t.Errorf("runtime root %q is inside workspace %q", root, workspace)
}
if !strings.Contains(root, "zero") {
t.Errorf("runtime root %q does not look like a zero-owned tree", root)
}
}
+12
View File
@@ -24,6 +24,18 @@ func acquireSandboxRuntimeLease(root string) (*sandboxRuntimeLease, error) {
return &sandboxRuntimeLease{handle: handle}, nil
}
// acquireSandboxRuntimeLeaseIn takes the shared lease named name inside parent,
// which the caller has just validated: the directory is opened without
// following a link at its final component and the lease file is created or
// opened relative to that handle, never by a fresh pathname walk.
func acquireSandboxRuntimeLeaseIn(parent, name string) (*sandboxRuntimeLease, error) {
handle, err := acquireSharedRuntimeLeaseIn(parent, name)
if err != nil {
return nil, fmt.Errorf("acquire sandbox runtime lease: %w", err)
}
return &sandboxRuntimeLease{handle: handle}, nil
}
func tryAcquireSandboxRuntimeCleanupLease(root string) (*sandboxRuntimeLease, bool, error) {
handle, inUse, err := tryAcquireExclusiveRuntimeLease(sandboxRuntimeLeasePath(root))
if err != nil || inUse {
@@ -0,0 +1,87 @@
//go:build !windows
package sandbox
import (
"os"
"path/filepath"
"strings"
"testing"
)
// THE REUSABLE CHILD OF THE FALLBACK ANCHOR IS VALIDATED BEFORE THE LEASE.
//
// The anchor was checked, but its reusable "v1" child was created by pathname
// and the lease opened beside it, so a symlink planted at v1 by an earlier
// same-user sandboxed command sent the .lease into another directory before
// validation ever ran. With the fallback root now predictable and persistent,
// that state carried across processes. Preparation must refuse without any
// effect in the redirected target.
func TestPrepareSandboxRuntimeRefusesARedirectedFallbackChild(t *testing.T) {
_, tempRoot := isolateSandboxRuntimeRoots(t)
workspace := filepath.Join(t.TempDir(), "ws")
if err := os.MkdirAll(workspace, 0o700); err != nil {
t.Fatal(err)
}
// Force the fallback: the cache root inside the workspace is unusable.
original := sandboxUserCacheDir
sandboxUserCacheDir = func() (string, error) { return filepath.Join(workspace, ".cache"), nil }
t.Cleanup(func() { sandboxUserCacheDir = original })
anchor := fallbackRuntimeAnchor()
// Compared physically: the anchor is derived from the resolved temp root,
// and on macOS the fixture temp under /var resolves to /private/var.
physicalTemp, err := filepath.EvalSymlinks(tempRoot)
if err != nil {
t.Fatalf("resolve fixture temp: %v", err)
}
if rel, err := filepath.Rel(physicalTemp, anchor); err != nil || rel == ".." || filepath.IsAbs(rel) || strings.HasPrefix(rel, "..") {
t.Fatalf("SETUP INVALID: fallback anchor %s is not under the fixture temp %s", anchor, physicalTemp)
}
if err := os.MkdirAll(anchor, 0o700); err != nil {
t.Fatal(err)
}
elsewhere := filepath.Join(t.TempDir(), "elsewhere")
if err := os.MkdirAll(elsewhere, 0o700); err != nil {
t.Fatal(err)
}
if err := os.Symlink(elsewhere, filepath.Join(anchor, "v1")); err != nil {
t.Fatalf("symlink: %v", err)
}
_, release, err := prepareSandboxRuntime(workspace)
if release != nil {
release()
}
if err == nil {
t.Fatal("preparation followed a redirected v1 instead of refusing")
}
entries, readErr := os.ReadDir(elsewhere)
if readErr != nil {
t.Fatal(readErr)
}
if len(entries) != 0 {
names := make([]string, 0, len(entries))
for _, entry := range entries {
names = append(names, entry.Name())
}
t.Fatalf("preparation left %v in the redirected target before refusing", names)
}
// CONTROL: with v1 an ordinary directory, or absent, preparation works and
// its lease lands beside the root it selected.
if err := os.Remove(filepath.Join(anchor, "v1")); err != nil {
t.Fatal(err)
}
state, release, err := prepareSandboxRuntime(workspace)
if err != nil {
t.Fatalf("ordinary preparation: %v", err)
}
defer release()
if filepath.Dir(state.Root) != filepath.Join(anchor, "v1") {
t.Fatalf("selected root %s is not under the fallback anchor's v1", state.Root)
}
if _, err := os.Lstat(sandboxRuntimeLeasePath(state.Root)); err != nil {
t.Fatalf("lease was not created beside the selected root: %v", err)
}
}
@@ -0,0 +1,81 @@
//go:build windows
package sandbox
import (
"os"
"path/filepath"
"strings"
"testing"
)
// THE REUSABLE CHILD OF THE FALLBACK ANCHOR IS VALIDATED BEFORE THE LEASE.
//
// The anchor was checked, but its reusable "v1" child was created by pathname
// and the lease opened beside it, so a junction planted at v1 sent the .lease
// into another directory before validation ever ran. Preparation must refuse
// without any effect in the redirected target. A junction, not a symlink,
// because that is what an unprivileged account on this platform can create.
func TestPrepareSandboxRuntimeRefusesARedirectedFallbackChild(t *testing.T) {
_, tempRoot := isolateSandboxRuntimeRoots(t)
workspace := filepath.Join(t.TempDir(), "ws")
if err := os.MkdirAll(workspace, 0o700); err != nil {
t.Fatal(err)
}
// Force the fallback: the cache root inside the workspace is unusable.
original := sandboxUserCacheDir
sandboxUserCacheDir = func() (string, error) { return filepath.Join(workspace, ".cache"), nil }
t.Cleanup(func() { sandboxUserCacheDir = original })
anchor := fallbackRuntimeAnchor()
if !strings.HasPrefix(strings.ToLower(anchor), strings.ToLower(tempRoot)) {
physical, _ := physicalDir(tempRoot)
if physical == "" || !strings.HasPrefix(strings.ToLower(anchor), strings.ToLower(physical)) {
t.Fatalf("SETUP INVALID: fallback anchor %s is not under the fixture temp %s", anchor, tempRoot)
}
}
if err := os.MkdirAll(anchor, 0o700); err != nil {
t.Fatal(err)
}
elsewhere := filepath.Join(t.TempDir(), "elsewhere")
if err := os.MkdirAll(elsewhere, 0o700); err != nil {
t.Fatal(err)
}
makeJunction(t, filepath.Join(anchor, "v1"), elsewhere)
_, release, err := prepareSandboxRuntime(workspace)
if release != nil {
release()
}
if err == nil {
t.Fatal("preparation followed a redirected v1 instead of refusing")
}
entries, readErr := os.ReadDir(elsewhere)
if readErr != nil {
t.Fatal(readErr)
}
if len(entries) != 0 {
names := make([]string, 0, len(entries))
for _, entry := range entries {
names = append(names, entry.Name())
}
t.Fatalf("preparation left %v in the redirected target before refusing", names)
}
// CONTROL: with the junction gone, preparation works and its lease lands
// beside the root it selected.
if err := os.Remove(filepath.Join(anchor, "v1")); err != nil {
t.Fatal(err)
}
state, release, err := prepareSandboxRuntime(workspace)
if err != nil {
t.Fatalf("ordinary preparation: %v", err)
}
defer release()
if !strings.EqualFold(filepath.Dir(state.Root), filepath.Join(anchor, "v1")) {
t.Fatalf("selected root %s is not under the fallback anchor's v1", state.Root)
}
if _, err := os.Lstat(sandboxRuntimeLeasePath(state.Root)); err != nil {
t.Fatalf("lease was not created beside the selected root: %v", err)
}
}
+20
View File
@@ -4,7 +4,9 @@ package sandbox
import (
"errors"
"fmt"
"os"
"path/filepath"
"golang.org/x/sys/unix"
)
@@ -13,6 +15,24 @@ type runtimeLeaseHandle struct {
file *os.File
}
func acquireSharedRuntimeLeaseIn(parent, name string) (runtimeLeaseHandle, error) {
dirFD, err := unix.Open(parent, unix.O_RDONLY|unix.O_DIRECTORY|unix.O_NOFOLLOW|unix.O_CLOEXEC, 0)
if err != nil {
return runtimeLeaseHandle{}, fmt.Errorf("open sandbox runtime parent %s: %w", parent, err)
}
defer unix.Close(dirFD)
fd, err := unix.Openat(dirFD, name, unix.O_CREAT|unix.O_RDWR|unix.O_NOFOLLOW|unix.O_CLOEXEC, 0o600)
if err != nil {
return runtimeLeaseHandle{}, fmt.Errorf("open sandbox runtime lease %s: %w", name, err)
}
file := os.NewFile(uintptr(fd), filepath.Join(parent, name))
if err := unix.Flock(int(file.Fd()), unix.LOCK_SH); err != nil {
_ = file.Close()
return runtimeLeaseHandle{}, err
}
return runtimeLeaseHandle{file: file}, nil
}
func acquireSharedRuntimeLease(path string) (runtimeLeaseHandle, error) {
file, err := os.OpenFile(path, os.O_CREATE|os.O_RDWR, 0o600)
if err != nil {
+55
View File
@@ -4,7 +4,10 @@ package sandbox
import (
"errors"
"fmt"
"os"
"path/filepath"
"unsafe"
"golang.org/x/sys/windows"
)
@@ -14,6 +17,58 @@ type runtimeLeaseHandle struct {
overlapped windows.Overlapped
}
// acquireSharedRuntimeLeaseIn opens or creates the lease relative to a handle on
// its parent that refuses a reparse point at the final component, so the
// pathname the caller just validated cannot be swapped underneath the open.
func acquireSharedRuntimeLeaseIn(parent, name string) (runtimeLeaseHandle, error) {
dir, err := openWindowsACLDirectoryNoFollow(parent)
if err != nil {
return runtimeLeaseHandle{}, fmt.Errorf("open sandbox runtime parent: %w", err)
}
defer func() { _ = windows.CloseHandle(dir) }()
if err := validateWindowsACLComponent(name); err != nil {
return runtimeLeaseHandle{}, err
}
objectName, err := windows.NewNTUnicodeString(name)
if err != nil {
return runtimeLeaseHandle{}, fmt.Errorf("encode sandbox runtime lease %s: %w", name, err)
}
attributes := windows.OBJECT_ATTRIBUTES{
RootDirectory: dir,
ObjectName: objectName,
Attributes: windows.OBJ_CASE_INSENSITIVE,
}
attributes.Length = uint32(unsafe.Sizeof(attributes))
var handle windows.Handle
var status windows.IO_STATUS_BLOCK
if err := windows.NtCreateFile(
&handle,
windows.GENERIC_READ|windows.GENERIC_WRITE|windows.SYNCHRONIZE,
&attributes,
&status,
nil,
windows.FILE_ATTRIBUTE_NORMAL,
windows.FILE_SHARE_READ|windows.FILE_SHARE_WRITE|windows.FILE_SHARE_DELETE,
windows.FILE_OPEN_IF,
windows.FILE_NON_DIRECTORY_FILE|windows.FILE_OPEN_REPARSE_POINT|windows.FILE_SYNCHRONOUS_IO_NONALERT,
0,
0,
); err != nil {
return runtimeLeaseHandle{}, fmt.Errorf("open sandbox runtime lease %s: %w", name, err)
}
if err := rejectWindowsACLReparseHandle(handle, name); err != nil {
_ = windows.CloseHandle(handle)
return runtimeLeaseHandle{}, err
}
file := os.NewFile(uintptr(handle), filepath.Join(parent, name))
lease := runtimeLeaseHandle{file: file}
if err := windows.LockFileEx(windows.Handle(file.Fd()), 0, 0, 1, 0, &lease.overlapped); err != nil {
_ = file.Close()
return runtimeLeaseHandle{}, err
}
return lease, nil
}
func acquireSharedRuntimeLease(path string) (runtimeLeaseHandle, error) {
file, err := os.OpenFile(path, os.O_CREATE|os.O_RDWR, 0o600)
if err != nil {
+234 -37
View File
@@ -7,10 +7,14 @@ import (
"fmt"
"os"
"path/filepath"
"runtime"
"sort"
"strconv"
"strings"
"sync"
"time"
"github.com/Twigpine/zero/internal/peermsg"
)
var sandboxUserCacheDir = os.UserCacheDir
@@ -21,11 +25,6 @@ const (
sandboxRuntimeMaxRoots = 64
)
var fallbackSandboxRuntimes = struct {
sync.Mutex
roots map[string]string
}{roots: make(map[string]string)}
type SandboxRuntime struct {
Root string `json:"root,omitempty"`
Cache string `json:"cache,omitempty"`
@@ -33,8 +32,37 @@ type SandboxRuntime struct {
Temp string `json:"temp,omitempty"`
}
// sandboxRuntimeRootFor derives the per-workspace runtime root. It is separated
// from prepareSandboxRuntime because the elevated Windows setup path needs the
// same answer WITHOUT taking a lease or creating anything: a sandbox principal
// is a separate account with no inherited rights under the user cache, so setup
// has to grant it write access to this tree before any command runs.
//
// Both callers must agree exactly. If they ever drift, setup grants the ACE on
// one directory while commands write to another, and the failure is a bare
// ACCESS_DENIED from npm or go build with nothing pointing at the sandbox.
func sandboxRuntimeRootFor(workspaceRoot string, cacheRoot string) (string, error) {
if root, ok := deterministicSandboxRuntimeRoot(workspaceRoot, cacheRoot); ok {
return root, nil
}
return fallbackSandboxRuntimeRoot(workspaceRoot)
}
// deterministicSandboxRuntimeRoot returns the cache-derived runtime root and
// whether it is usable, meaning it lands outside the workspace.
//
// Neither this nor the fallback creates anything now, so a caller that only
// needs to NAME the tree can safely go through sandboxRuntimeRootFor and get the
// answer commands will actually use. This remains separate for callers that need
// to distinguish the cache-derived root from the temp-derived one.
func deterministicSandboxRuntimeRoot(workspaceRoot string, cacheRoot string) (string, bool) {
digest := sha256.Sum256([]byte(workspaceRoot))
root := filepath.Join(cacheRoot, "zero", "runtime", "v1", hex.EncodeToString(digest[:8]))
return root, !pathWithinRoot(workspaceRoot, root)
}
func prepareSandboxRuntime(workspaceRoot string) (SandboxRuntime, func(), error) {
workspaceRoot = filepath.Clean(strings.TrimSpace(workspaceRoot))
workspaceRoot = canonicalSandboxWorkspaceRoot(workspaceRoot)
if workspaceRoot == "" || workspaceRoot == "." {
return SandboxRuntime{}, nil, errors.New("sandbox runtime requires a workspace root")
}
@@ -42,17 +70,30 @@ func prepareSandboxRuntime(workspaceRoot string) (SandboxRuntime, func(), error)
if err != nil {
return SandboxRuntime{}, nil, fmt.Errorf("resolve user cache directory: %w", err)
}
cacheRoot = filepath.Clean(strings.TrimSpace(cacheRoot))
// Canonicalized the SAME way as the workspace root, because
// sandboxRuntimeRootFor compares the two: it falls back to a private temp
// tree when the derived runtime root would land inside the workspace.
// Normalizing only one side made that comparison run on two different
// spellings of the same path — /var vs /private/var on macOS, an 8.3 short
// name vs its long form on Windows — so the containment check missed and the
// fallback never fired.
cacheRoot = canonicalSandboxWorkspaceRoot(cacheRoot)
if cacheRoot == "" || cacheRoot == "." {
return SandboxRuntime{}, nil, errors.New("user cache directory is unavailable")
}
digest := sha256.Sum256([]byte(workspaceRoot))
root := filepath.Join(cacheRoot, "zero", "runtime", "v1", hex.EncodeToString(digest[:8]))
if pathWithinRoot(workspaceRoot, root) {
root, err = fallbackSandboxRuntimeRoot(workspaceRoot)
if err != nil {
return SandboxRuntime{}, nil, err
}
root, err := sandboxRuntimeRootFor(workspaceRoot, cacheRoot)
if err != nil {
return SandboxRuntime{}, nil, err
}
// THE ANCHOR IS PROVEN BEFORE THE TREE IS BUILT, on both paths that can
// hand back a fallback root: sandboxRuntimeRootFor returns one itself when
// the cache lands inside the workspace, and the branch below asks for one
// when the cache root cannot be leased. A deterministic name under the
// shared temp is only safe beneath a directory this user owns; if the anchor
// is a link, or exists and belongs to someone else, this refuses rather than
// leasing, creating and chmod-ing through it.
if err := ensureFallbackRuntimeAnchor(root); err != nil {
return SandboxRuntime{}, nil, err
}
lease, err := prepareSandboxRuntimeLease(root)
if err != nil {
@@ -60,6 +101,9 @@ func prepareSandboxRuntime(workspaceRoot string) (SandboxRuntime, func(), error)
if err != nil {
return SandboxRuntime{}, nil, err
}
if err := ensureFallbackRuntimeAnchor(root); err != nil {
return SandboxRuntime{}, nil, err
}
lease, err = prepareSandboxRuntimeLease(root)
if err != nil {
return SandboxRuntime{}, nil, err
@@ -90,13 +134,13 @@ func prepareSandboxRuntime(workspaceRoot string) (SandboxRuntime, func(), error)
filepath.Join(runtimeState.Data, "go-mod"),
filepath.Join(runtimeState.Data, "cargo"),
}
for _, directory := range directories {
if err := os.MkdirAll(directory, 0o700); err != nil {
return SandboxRuntime{}, nil, fmt.Errorf("create sandbox runtime directory %s: %w", directory, err)
}
if err := os.Chmod(directory, 0o700); err != nil {
return SandboxRuntime{}, nil, fmt.Errorf("secure sandbox runtime directory %s: %w", directory, err)
}
// Handle-relative and no-follow below the operator-owned base. The tree is
// persistent input from the previous sandboxed command, which is granted write
// access to cache, data and tmp and can leave a link in place of one of them.
// os.MkdirAll and os.Chmod both follow, so the host process created package
// caches wherever that command pointed them. See ensureRuntimeTreeDirs.
if err := ensureRuntimeTreeDirs(runtimeState.Root, directories); err != nil {
return SandboxRuntime{}, nil, err
}
now := sandboxRuntimeNow()
if err := os.Chtimes(runtimeState.Root, now, now); err != nil {
@@ -108,10 +152,20 @@ func prepareSandboxRuntime(workspaceRoot string) (SandboxRuntime, func(), error)
}
func prepareSandboxRuntimeLease(root string) (*sandboxRuntimeLease, error) {
if err := os.MkdirAll(filepath.Dir(root), 0o700); err != nil {
return nil, fmt.Errorf("create sandbox runtime parent: %w", err)
// THE OWNED TAIL IS VALIDATED BEFORE THE FIRST EFFECT, AND THE LEASE IS
// OPENED THROUGH THAT VALIDATION. The anchor check above this covers the
// anchor; the reusable "v1" child beneath it is the runtime's too, and
// creating it by pathname followed whatever was sitting at that name.
// Redirect v1 into another directory and the old sequence created a .lease
// there and only then failed validation. EnsurePrivateDir walks each
// component without following links and creates what is missing in place;
// the lease is then opened relative to a no-follow handle on that parent, so
// a component swapped in after the check cannot move the open either.
parent := filepath.Dir(root)
if err := peermsg.EnsurePrivateDir(parent); err != nil {
return nil, fmt.Errorf("sandbox runtime parent %s is not a private directory owned by this user: %w", parent, err)
}
return acquireSandboxRuntimeLease(root)
return acquireSandboxRuntimeLeaseIn(parent, filepath.Base(root)+sandboxRuntimeLeaseSuffix)
}
// cleanupSandboxRuntimeRoots applies a conservative age/count policy. Cleanup
@@ -174,22 +228,109 @@ func combineSandboxCleanups(cleanups ...func()) func() {
}
}
// fallbackRuntimeAnchor is the per-user directory the deterministic fallback
// runtime tree lives beneath.
//
// DETERMINISM IS NOT OWNERSHIP. The fallback moved from a fresh, private
// os.MkdirTemp parent to a predictable name so that elevated setup and the
// later command process agree on the runtime root. That agreement is required
// and must stay. But a predictable path directly under the shared system temp
// is not a private allocation: on an ordinary shared /tmp another local user
// can create /tmp/zero with mode 0700 first, and every affected user then fails
// before the sandbox command starts; a pre-existing redirected component makes
// host-side preparation operate somewhere other than the derived tree.
//
// So the tree is rooted beneath an anchor that names THIS user, and the anchor
// is created and validated by peermsg.EnsurePrivateDir before anything is
// built under it: handle-relative descent, no-follow, refused if any component
// is a link or the leaf is not owned by the current user, mode 0700. On Unix
// the uid is in the name because /tmp is shared between users; on Windows
// os.TempDir is already per-user, and the private descriptor plus the owner
// check do the rest.
func fallbackRuntimeAnchor() string {
tag := "user"
if runtime.GOOS != "windows" {
tag = strconv.Itoa(os.Getuid())
}
// PHYSICAL PARENT, OWNED LEAF. The validator walks every component no-follow
// and refuses links, which is right for the anchor Zero owns and wrong for
// the operator's ancestors above it: macOS puts TempDir under /var, a
// symlink to /private/var, and a redirected %LOCALAPPDATA% is ordinary on
// Windows. The first version handed the validator the unresolved path and
// refused every fallback on every Mac. Resolving the parent first means the
// only new component the validator sees is the anchor itself.
//
// On a resolve error the unresolved path is used, deliberately: the
// validator is still the fail-closed check, and refusing there names the
// real component rather than hiding it behind a resolver failure.
base := os.TempDir()
if physical, err := physicalTempDir(); err == nil && physical != "" {
base = physical
}
return filepath.Join(base, "zero-runtime-"+tag)
}
// isFallbackRuntimeRoot reports whether root was derived by
// fallbackSandboxRuntimeRoot, so the caller knows the anchor must be validated
// before the tree beneath it is prepared. Both candidates a command derives can
// be fallback roots: sandboxRuntimeRootFor returns one itself when the cache
// lands inside the workspace, and prepareSandboxRuntime asks for one when the
// cache root cannot be leased.
func isFallbackRuntimeRoot(root string) bool {
// pathWithinRoot(parent, child): is root beneath the anchor. The first
// draft had these reversed, which asked whether the anchor was beneath the
// root, answered false every time, and skipped the validation entirely
// while every test that depended on it reported success through a
// junction. Argument order is the whole function.
return pathWithinRoot(fallbackRuntimeAnchor(), root)
}
// ensureFallbackRuntimeAnchor validates the anchor beneath which a fallback
// runtime tree is about to be built, and fails closed. Called only when the
// root is a fallback root; the cache-derived root lives under the user cache,
// which is already the user's own directory.
func ensureFallbackRuntimeAnchor(root string) error {
if !isFallbackRuntimeRoot(root) {
return nil
}
anchor := fallbackRuntimeAnchor()
if err := peermsg.EnsurePrivateDir(anchor); err != nil {
return fmt.Errorf("sandbox runtime fallback anchor %s is not a private directory owned by this user: %w", anchor, err)
}
return nil
}
// fallbackSandboxRuntimeRoot returns the runtime root for a workspace whose
// cache-derived root would land inside itself.
//
// DERIVED, not minted, and that is the whole of the fix. It used to call
// os.MkdirTemp and remember the answer in a process-global map, which made the
// result private to whichever process asked first. Elevated Windows setup
// granted the sandbox principal write access to the directory IT created, then
// every later __windows-command-runner process created a DIFFERENT one and
// pointed TMP, GOCACHE, npm and the rest at it. Those directories are created by
// the calling user and carry no ACE for the principal, so ordinary cache and
// temp writes failed with a bare ACCESS_DENIED and nothing naming the sandbox.
//
// sandboxRuntimeRootFor already documents that both callers must agree exactly.
// Hashing the workspace, the same way the cache-derived root does, is what makes
// that true for this branch too: every process reaches the same path without
// having to share any state.
//
// It creates nothing, so deterministicSandboxRuntimeRoot's promise about naming
// a tree without materializing it now holds for the fallback as well.
func fallbackSandboxRuntimeRoot(workspaceRoot string) (string, error) {
fallbackSandboxRuntimes.Lock()
defer fallbackSandboxRuntimes.Unlock()
if root := fallbackSandboxRuntimes.roots[workspaceRoot]; root != "" {
return root, nil
}
parent, err := os.MkdirTemp("", "zero-runtime-")
if err != nil {
return "", fmt.Errorf("create fallback sandbox runtime: %w", err)
}
root := filepath.Join(parent, "runtime")
digest := sha256.Sum256([]byte(workspaceRoot))
root := filepath.Join(fallbackRuntimeAnchor(), "v1", hex.EncodeToString(digest[:8]))
if pathWithinRoot(workspaceRoot, root) {
_ = os.RemoveAll(parent)
return "", fmt.Errorf("fallback sandbox runtime root %q must be outside workspace %q", root, workspaceRoot)
// Both candidates land inside the workspace, so there is nowhere left to
// put a runtime tree the workspace's own policy does not govern. Refused
// rather than pointed somewhere arbitrary: a runtime root inside the
// workspace makes the sandbox's own cache writes indistinguishable from
// the work it is meant to be confining.
return "", fmt.Errorf("sandbox runtime root %q would fall inside workspace %q; "+
"open the workspace somewhere other than the cache or temp directory", root, workspaceRoot)
}
fallbackSandboxRuntimes.roots[workspaceRoot] = root
return root, nil
}
@@ -226,3 +367,59 @@ func permissionProfileWithRuntime(profile PermissionProfile, runtimeState Sandbo
profile.FileSystem.WriteRoots = append(profile.FileSystem.WriteRoots, WritableRoot{Root: runtimeState.Root})
return profile
}
// canonicalSandboxWorkspaceRoot normalizes a workspace root the way
// Engine.resolveCommandDir already does — clean, absolutize, then resolve
// symlinks — so every derivation keyed to a workspace agrees on the string.
//
// The runtime root is a hash of this, and the elevated Windows setup grants the
// principal that tree while commands derive it again. Cleaning alone was not
// enough for the two to agree, and it does not take a symlink for them to
// differ: a path opened in different casing, or through an 8.3 short name (what
// a Windows CI runner's TEMP looks like), resolves to a different spelling.
// Setup then granted one tree and every command used another, so the grant that
// makes npm/go/pip caches writable landed where nothing reads and surfaced as a
// bare ACCESS_DENIED.
//
// Resolution failing is not an error: an unresolvable root still needs a stable
// key, and falling back to the cleaned absolute path is what the command path
// does too.
func canonicalSandboxWorkspaceRoot(root string) string {
cleaned := filepath.Clean(strings.TrimSpace(root))
if cleaned == "" || cleaned == "." {
return ""
}
if !filepath.IsAbs(cleaned) {
if absolute, err := filepath.Abs(cleaned); err == nil {
cleaned = absolute
}
}
// EvalSymlinks fails outright when the LEAF does not exist, which is the
// normal case for a cache or runtime root that has not been created yet. A
// plain call therefore resolved an existing workspace while leaving a
// not-yet-created cache root unresolved, and the two were compared against
// each other — the containment check that decides whether the runtime tree
// must move out of the workspace then ran on /private/var/... versus
// /var/..., missed, and left the tree inside the workspace.
//
// Resolve the longest existing ancestor and re-append the rest, so a path
// normalizes the same way whether or not its final segments exist yet.
remainder := ""
current := cleaned
for {
if resolved, err := filepath.EvalSymlinks(current); err == nil {
if remainder == "" {
return resolved
}
return filepath.Join(resolved, remainder)
}
parent := filepath.Dir(current)
if parent == current {
// Nothing along the path resolved; the cleaned absolute form is the
// best stable key available.
return cleaned
}
remainder = filepath.Join(filepath.Base(current), remainder)
current = parent
}
}
+107
View File
@@ -10,6 +10,7 @@ import (
)
func TestPrepareSandboxRuntimeStaysOutsideWorkspace(t *testing.T) {
isolateSandboxRuntimeRoots(t)
workspace := t.TempDir()
cacheRoot := t.TempDir()
original := sandboxUserCacheDir
@@ -39,6 +40,7 @@ func TestPrepareSandboxRuntimeStaysOutsideWorkspace(t *testing.T) {
}
func TestPrepareSandboxRuntimeCleansExpiredSibling(t *testing.T) {
isolateSandboxRuntimeRoots(t)
workspace := t.TempDir()
cacheRoot := t.TempDir()
now := time.Date(2026, 7, 20, 12, 0, 0, 0, time.UTC)
@@ -70,6 +72,7 @@ func TestPrepareSandboxRuntimeCleansExpiredSibling(t *testing.T) {
}
func TestPrepareSandboxRuntimeFallsBackWhenUserCacheIsInsideWorkspace(t *testing.T) {
isolateSandboxRuntimeRoots(t)
workspace := t.TempDir()
original := sandboxUserCacheDir
sandboxUserCacheDir = func() (string, error) { return filepath.Join(workspace, ".cache"), nil }
@@ -89,6 +92,7 @@ func TestPrepareSandboxRuntimeFallsBackWhenUserCacheIsInsideWorkspace(t *testing
}
func TestCleanupSandboxRuntimeSkipsActiveLease(t *testing.T) {
isolateSandboxRuntimeRoots(t)
workspace := t.TempDir()
cacheRoot := t.TempDir()
now := time.Date(2026, 7, 20, 12, 0, 0, 0, time.UTC)
@@ -329,3 +333,106 @@ func TestEngineCommandPlanCarriesManagedRuntime(t *testing.T) {
}
cleanupLease.release()
}
// sandboxRuntimeRootFor compares the workspace root against the derived runtime
// root to decide whether to fall back to a private temp tree. Both sides
// therefore have to be the same spelling of the same path.
//
// Canonicalizing only the workspace root broke this on CI: the workspace
// resolved (/var to /private/var on macOS, an 8.3 short name to its long form
// on Windows) while the cache root kept its original spelling, so the
// containment check compared two different strings, the fallback never fired,
// and the runtime tree was placed inside the workspace it exists to stay out of.
//
// A symlink is the portable way to produce a spelling that only resolution
// reconciles — Clean cannot see through one. Windows refuses to create symlinks
// without privilege, so this skips there; the platforms that CI caught the bug
// on are the ones that run it.
func TestPrepareSandboxRuntimeNormalizesTheCacheRootBeforeComparingIt(t *testing.T) {
isolateSandboxRuntimeRoots(t)
workspace := t.TempDir()
link := filepath.Join(t.TempDir(), "workspace-link")
if err := os.Symlink(workspace, link); err != nil {
t.Skipf("cannot create a symlink here: %v", err)
}
// The cache root reaches us spelled through the symlink; the workspace does
// not. Resolved, it is plainly inside the workspace and the fallback must
// fire. Unresolved, the two strings share no prefix and it does not.
original := sandboxUserCacheDir
sandboxUserCacheDir = func() (string, error) { return filepath.Join(link, ".cache"), nil }
t.Cleanup(func() { sandboxUserCacheDir = original })
runtimeState, release, err := prepareSandboxRuntime(workspace)
if err != nil {
t.Fatalf("prepareSandboxRuntime: %v", err)
}
if release != nil {
defer release()
}
// Resolve before comparing. Spelled through the link the runtime root shares
// no textual prefix with the workspace, so an unresolved comparison would
// call it "outside" while it sits physically inside — the test would pass
// against the very bug it exists for.
resolved := runtimeState.Root
if actual, err := filepath.EvalSymlinks(runtimeState.Root); err == nil {
resolved = actual
}
if pathWithinRoot(workspace, resolved) {
t.Fatalf("runtime root %q resolves to %q, inside workspace %q; the containment check did not see through the cache root's spelling", runtimeState.Root, resolved, workspace)
}
}
// A path whose final segments do not exist yet must still normalize the same
// way as one that does. This is the shape macOS CI hit: t.TempDir() sits under
// /var, a symlink to /private/var, and the cache root it derives has not been
// created when it is first normalized. Resolving only the workspace left the
// two sides of the containment check spelled differently.
func TestCanonicalSandboxWorkspaceRootResolvesThroughAMissingLeaf(t *testing.T) {
real := t.TempDir()
link := filepath.Join(t.TempDir(), "link")
if err := os.Symlink(real, link); err != nil {
t.Skipf("cannot create a symlink here: %v", err)
}
existing := canonicalSandboxWorkspaceRoot(link)
if existing != canonicalSandboxWorkspaceRoot(real) {
t.Fatalf("an existing symlinked dir did not resolve: %q vs %q", existing, canonicalSandboxWorkspaceRoot(real))
}
// The leaf, and its parent, do not exist.
missing := filepath.Join(link, ".cache", "zero")
got := canonicalSandboxWorkspaceRoot(missing)
want := filepath.Join(existing, ".cache", "zero")
if got != want {
t.Errorf("missing leaf normalized to %q, want %q — the ancestor was not resolved", got, want)
}
if !pathWithinRoot(existing, got) {
t.Errorf("%q should be inside %q once both are canonical", got, existing)
}
}
// isolateSandboxRuntimeRoots gives a test its own cache root AND its own temp
// root, so every runtime tree the production code can select, the preferred
// cache-derived one and the temp-derived fallback, lands under the fixture.
// Workspace isolation is not runtime-storage isolation: those paths come from
// separate resolver inputs, and a test that redirected only the workspace ran
// real setup, preparation and reclamation against the developer's own cache
// and temp. Both roots are returned for assertions on where things landed.
func isolateSandboxRuntimeRoots(t *testing.T) (cacheRoot, tempRoot string) {
t.Helper()
cacheRoot = filepath.Join(t.TempDir(), "cache")
tempRoot = filepath.Join(t.TempDir(), "temp")
for _, dir := range []string{cacheRoot, tempRoot} {
if err := os.MkdirAll(dir, 0o700); err != nil {
t.Fatal(err)
}
}
previous := sandboxUserCacheDir
sandboxUserCacheDir = func() (string, error) { return cacheRoot, nil }
t.Cleanup(func() { sandboxUserCacheDir = previous })
// os.TempDir reads these at call time on every platform this runs on.
t.Setenv("TMP", tempRoot)
t.Setenv("TEMP", tempRoot)
t.Setenv("TMPDIR", tempRoot)
return cacheRoot, tempRoot
}
+88
View File
@@ -0,0 +1,88 @@
package sandbox
import (
"fmt"
"path/filepath"
"strings"
)
// ensureRuntimeTreeDirs creates every directory of the runtime tree without ever
// following a link below the operator-owned base.
//
// THE TREE IS PERSISTENT INPUT FROM THE PREVIOUS SANDBOXED COMMAND.
//
// The runtime root is deterministic so setup and later runners agree on one
// path, and the sandboxed command is granted write access to cache, data and
// tmp. So the command can replace one of them with a symlink or a Windows
// junction on its way out. The next preparation ran os.MkdirAll and os.Chmod on
// raw pathnames, which follow, and the HOST Zero process, the ordinary user
// rather than the confined principal, then created package-cache directories
// inside a target the previous command chose.
//
// The anchor check is not enough on its own: it proves the per-user anchor and
// says nothing about the reusable root or any descendant beneath it.
//
// NOT peermsg.EnsurePrivateDir. That ends in a protected-DACL write, which on
// Windows strips the sandbox principal's grant that elevated setup installed on
// the runtime tree and brings back the bare access denials from npm and go that
// the grant exists to prevent. This descent validates and creates; it does not
// re-secure.
func ensureRuntimeTreeDirs(root string, directories []string) error {
// Canonicalized the same way the rest of the runtime state is, because
// runtimeCandidateBase decides ownership with a containment test and that
// test runs on spellings. An 8.3 short name (C:UsersRUNNER~1) or a
// symlinked temp compares unequal to the long form of the same directory,
// which reads as "no operator-owned base" for a perfectly ordinary tree.
if canonical := canonicalSandboxWorkspaceRoot(root); canonical != "" {
root = canonical
}
base, ok := runtimeCandidateBase(root)
if !ok || strings.TrimSpace(base) == "" {
return fmt.Errorf("sandbox runtime root %s has no operator-owned base to descend from", root)
}
// Physical, so a redirected cache or TEMP above the tree stays the operator's
// business while everything Zero owns below it is addressed no-follow.
physical, err := physicalDir(base)
if err != nil {
return fmt.Errorf("resolve the sandbox runtime base %s: %w", base, err)
}
for _, directory := range directories {
tail, err := runtimeTreeTail(physical, base, directory)
if err != nil {
return err
}
if err := ensureRuntimeTreeDir(physical, tail); err != nil {
return err
}
}
return nil
}
// runtimeTreeTail returns the components of directory below the base, which are
// the ones Zero owns and the ones that must not be links.
func runtimeTreeTail(physicalBase string, base string, directory string) ([]string, error) {
cleaned := filepath.Clean(strings.TrimSpace(directory))
relative, err := filepath.Rel(base, cleaned)
if err != nil || relative == "." || strings.HasPrefix(relative, "..") {
// Try the physical spelling too: the caller's path may already be physical.
relative, err = filepath.Rel(physicalBase, cleaned)
if err != nil || relative == "." || strings.HasPrefix(relative, "..") {
return nil, fmt.Errorf("sandbox runtime directory %s does not sit under its base %s", directory, base)
}
}
parts := strings.Split(relative, string(filepath.Separator))
out := make([]string, 0, len(parts))
for _, part := range parts {
if part == "" || part == "." {
continue
}
if part == ".." {
return nil, fmt.Errorf("sandbox runtime directory %s escapes its base %s", directory, base)
}
out = append(out, part)
}
if len(out) == 0 {
return nil, fmt.Errorf("sandbox runtime directory %s resolves to its own base", directory)
}
return out, nil
}
+49
View File
@@ -0,0 +1,49 @@
//go:build !windows
package sandbox
import (
"fmt"
"os"
"path/filepath"
"golang.org/x/sys/unix"
)
// ensureRuntimeTreeDir creates the owned tail beneath a physical base using
// openat and mkdirat with O_NOFOLLOW, so a symlink planted at any component is
// refused rather than followed.
//
// fchmod on the retained descriptor rather than chmod on the pathname: chmod(2)
// follows symlinks, which is the half of this defect that actually applies here.
// Every owned component gets the mode, not only the leaf, because every one of
// them is ours.
func ensureRuntimeTreeDir(physicalBase string, tail []string) error {
parent, err := unix.Open(physicalBase, unix.O_RDONLY|unix.O_DIRECTORY|unix.O_CLOEXEC, 0)
if err != nil {
return fmt.Errorf("open the sandbox runtime base %s: %w", physicalBase, err)
}
defer func() { _ = unix.Close(parent) }()
current := physicalBase
for _, name := range tail {
current = filepath.Join(current, name)
if err := unix.Mkdirat(parent, name, 0o700); err != nil && err != unix.EEXIST {
return fmt.Errorf("create sandbox runtime directory %s: %w", current, err)
}
child, openErr := unix.Openat(parent, name, unix.O_RDONLY|unix.O_DIRECTORY|unix.O_NOFOLLOW|unix.O_CLOEXEC, 0)
if openErr != nil {
if openErr == unix.ELOOP || openErr == unix.ENOTDIR {
return fmt.Errorf("sandbox runtime component %s is a link or not a directory, so a previous sandboxed command may have redirected it: %w", current, os.ErrInvalid)
}
return fmt.Errorf("open sandbox runtime directory %s: %w", current, openErr)
}
if err := unix.Fchmod(child, 0o700); err != nil {
_ = unix.Close(child)
return fmt.Errorf("secure sandbox runtime directory %s: %w", current, err)
}
_ = unix.Close(parent)
parent = child
}
return nil
}
@@ -0,0 +1,193 @@
//go:build windows
package sandbox
import (
"os"
"os/exec"
"path/filepath"
"testing"
)
// A PREVIOUS SANDBOXED COMMAND CAN LEAVE A REDIRECT BEHIND.
//
// The runtime root is deterministic so setup and later runners agree on one
// path, and the sandboxed command is granted write access to cache, data and
// tmp. So it can replace one of them with a junction on its way out. The next
// preparation used os.MkdirAll and os.Chmod on raw pathnames, which follow, and
// the HOST Zero process, the ordinary user rather than the confined principal,
// then created package-cache directories inside a target the previous command
// chose.
//
// The anchor check does not cover this: it proves the per-user anchor and says
// nothing about the reusable root or anything beneath it.
//
// A junction needs no privilege, so the previous command's half runs here on an
// ordinary unelevated box.
func TestRuntimeTreePreparationRefusesARedirectedDescendant(t *testing.T) {
base := runtimeTreeTestBase(t)
target := t.TempDir()
root := filepath.Join(base, "zero", "runtime", "v1", "abcdef0123456789")
cache := filepath.Join(root, "cache")
if err := os.MkdirAll(root, 0o700); err != nil {
t.Fatal(err)
}
// The previous lifetime leaves a junction where cache used to be.
if out, err := exec.Command("cmd", "/c", "mklink", "/J", cache, target).CombinedOutput(); err != nil {
t.Skipf("mklink /J unavailable here: %v\n%s", err, out)
}
// SETUP: the junction really redirects, or a clean target proves nothing.
probe := filepath.Join(cache, "probe.txt")
if err := os.WriteFile(probe, []byte("x"), 0o600); err != nil {
t.Skipf("the junction does not accept writes here: %v", err)
}
if _, err := os.Stat(filepath.Join(target, "probe.txt")); err != nil {
t.Skipf("SETUP: the junction does not redirect on this filesystem: %v", err)
}
if err := os.Remove(probe); err != nil {
t.Fatal(err)
}
err := ensureRuntimeTreeDirs(root, []string{root, cache, filepath.Join(cache, "npm")})
if err == nil {
t.Fatal("preparation descended through a junction the previous sandboxed command planted")
}
entries, readErr := os.ReadDir(target)
if readErr != nil {
t.Fatal(readErr)
}
if len(entries) != 0 {
names := make([]string, 0, len(entries))
for _, entry := range entries {
names = append(names, entry.Name())
}
t.Fatalf("preparation created %v beneath the redirected target", names)
}
}
// And an ordinary tree is still created, or the refusal above would be satisfied
// by a preparation that refuses everything.
func TestRuntimeTreePreparationStillCreatesAnOrdinaryTree(t *testing.T) {
base := runtimeTreeTestBase(t)
root := filepath.Join(base, "zero", "runtime", "v1", "abcdef0123456789")
cache := filepath.Join(root, "cache")
npm := filepath.Join(cache, "npm")
if err := ensureRuntimeTreeDirs(root, []string{root, cache, npm}); err != nil {
t.Fatalf("an ordinary runtime tree was refused: %v", err)
}
for _, dir := range []string{root, cache, npm} {
info, err := os.Stat(dir)
if err != nil || !info.IsDir() {
t.Fatalf("%s was not created: err=%v", dir, err)
}
}
}
// Reusing an existing tree is the common case and must not be refused.
func TestRuntimeTreePreparationIsIdempotent(t *testing.T) {
base := runtimeTreeTestBase(t)
root := filepath.Join(base, "zero", "runtime", "v1", "abcdef0123456789")
dirs := []string{root, filepath.Join(root, "cache"), filepath.Join(root, "cache", "npm")}
if err := ensureRuntimeTreeDirs(root, dirs); err != nil {
t.Fatalf("first preparation: %v", err)
}
if err := ensureRuntimeTreeDirs(root, dirs); err != nil {
t.Fatalf("second preparation over an existing tree was refused: %v", err)
}
}
// AND THE PRODUCTION ENTRY POINT USES IT, WHICH THE HELPER TESTS CANNOT SEE.
//
// The three tests above call ensureRuntimeTreeDirs directly, so reverting
// prepareSandboxRuntime to the old pathname loop leaves every one of them green.
// The defect was in what the entry point called, so this drives the entry point.
func TestPrepareSandboxRuntimeRefusesARedirectedDescendant(t *testing.T) {
isolateSandboxRuntimeRoots(t)
cacheRoot := t.TempDir()
target := t.TempDir()
previous := sandboxUserCacheDir
t.Cleanup(func() { sandboxUserCacheDir = previous })
sandboxUserCacheDir = func() (string, error) { return cacheRoot, nil }
workspace := t.TempDir()
root, ok := deterministicSandboxRuntimeRoot(canonicalSandboxWorkspaceRoot(workspace), canonicalSandboxWorkspaceRoot(cacheRoot))
if !ok {
t.Fatalf("SETUP INVALID: no deterministic runtime root for %s", workspace)
}
cache := filepath.Join(root, "cache")
if err := os.MkdirAll(root, 0o700); err != nil {
t.Fatal(err)
}
if out, err := exec.Command("cmd", "/c", "mklink", "/J", cache, target).CombinedOutput(); err != nil {
t.Skipf("mklink /J unavailable here: %v\n%s", err, out)
}
probe := filepath.Join(cache, "probe.txt")
if err := os.WriteFile(probe, []byte("x"), 0o600); err != nil {
t.Skipf("the junction does not accept writes here: %v", err)
}
if _, err := os.Stat(filepath.Join(target, "probe.txt")); err != nil {
t.Skipf("SETUP: the junction does not redirect on this filesystem: %v", err)
}
if err := os.Remove(probe); err != nil {
t.Fatal(err)
}
_, release, err := prepareSandboxRuntime(workspace)
if release != nil {
release()
}
if err == nil {
t.Fatal("prepareSandboxRuntime descended through a junction the previous sandboxed command planted")
}
entries, readErr := os.ReadDir(target)
if readErr != nil {
t.Fatal(readErr)
}
if len(entries) != 0 {
names := make([]string, 0, len(entries))
for _, entry := range entries {
names = append(names, entry.Name())
}
t.Fatalf("prepareSandboxRuntime created %v beneath the redirected target", names)
}
}
// And an ordinary workspace still prepares through the entry point.
func TestPrepareSandboxRuntimeStillPreparesAnOrdinaryTree(t *testing.T) {
isolateSandboxRuntimeRoots(t)
cacheRoot := t.TempDir()
previous := sandboxUserCacheDir
t.Cleanup(func() { sandboxUserCacheDir = previous })
sandboxUserCacheDir = func() (string, error) { return cacheRoot, nil }
runtimeState, release, err := prepareSandboxRuntime(t.TempDir())
if err != nil {
t.Fatalf("an ordinary workspace was refused: %v", err)
}
defer release()
for _, dir := range []string{runtimeState.Root, runtimeState.Cache, runtimeState.Data, runtimeState.Temp} {
info, statErr := os.Stat(dir)
if statErr != nil || !info.IsDir() {
t.Fatalf("%s was not created: err=%v", dir, statErr)
}
}
}
// runtimeTreeTestBase makes the operator-owned base deterministic.
//
// runtimeCandidateBase answers by containment against the user cache directory,
// so a bare t.TempDir() only works where temp happens to sit under it. On a CI
// runner it does not, or its 8.3 short name compares unequal to the long form,
// and the tree is reported as having no owned base. Stubbing the cache root is
// what makes these tests about the descent rather than about where temp lives.
func runtimeTreeTestBase(t *testing.T) string {
t.Helper()
base := canonicalSandboxWorkspaceRoot(t.TempDir())
previous := sandboxUserCacheDir
t.Cleanup(func() { sandboxUserCacheDir = previous })
sandboxUserCacheDir = func() (string, error) { return base, nil }
return base
}
+44
View File
@@ -0,0 +1,44 @@
//go:build windows
package sandbox
import (
"fmt"
"golang.org/x/sys/windows"
)
// ensureRuntimeTreeDir creates the owned tail beneath a physical base, one
// component at a time, from retained handles.
//
// Every open and create goes through the NtCreateFile helpers with
// OBJ_DONT_REPARSE and FILE_OPEN_REPARSE_POINT, so a junction planted at any
// component is seen as the link it is and refused rather than descended. No
// component name is resolved twice, so there is no interval for a swap to land
// in.
//
// No chmod. On Windows os.Chmod only toggles READONLY, and against a junction it
// lands on the link rather than the target, so it bought nothing here. The
// directory's protection is the ACL that elevated setup applied, which this
// descent deliberately does not touch.
func ensureRuntimeTreeDir(physicalBase string, tail []string) error {
parent, err := openWindowsACLDirectoryNoFollow(physicalBase)
if err != nil {
return fmt.Errorf("open the sandbox runtime base %s: %w", physicalBase, err)
}
defer func() { _ = windows.CloseHandle(parent) }()
for _, name := range tail {
child, _, createErr := createWindowsACLChildDirectory(parent, name)
if createErr != nil {
existing, openErr := openWindowsACLChildDirectory(parent, name)
if openErr != nil {
return fmt.Errorf("prepare the sandbox runtime component %s beneath %s: %w", name, physicalBase, createErr)
}
child = existing
}
_ = windows.CloseHandle(parent)
parent = child
}
return nil
}
+9
View File
@@ -104,12 +104,21 @@ const (
BlockNetwork BlockCode = "network"
BlockDestructiveCommand BlockCode = "destructive_command"
BlockPersistentDeny BlockCode = "persistent_deny"
BlockNestedGitInit BlockCode = "nested_git_init"
// BlockDenied is the catch-all for a denied decision that carries no more
// specific block code.
BlockDenied BlockCode = "denied"
)
const ReasonNetworkBlocked = "network access requires approval"
// ReasonNestedGitInit explains a refusal the operator can act on: the remedy is
// to run git init outside the sandbox, or to open the repository itself as the
// workspace rather than a subdirectory of it.
const ReasonNestedGitInit = "this workspace sits inside an existing git repository, so the sandbox has no git protection here to extend to a new one: " +
"a repository created now would carry a writable config and hooks. " +
"Every git init in the command is refused, because the sandbox does not resolve which directory each one targets. " +
"Run git init outside the sandbox, or open the repository root as the workspace"
const ReasonEscalatedSandboxRequired = "unsandboxed shell command requires approval"
const (
+276 -8
View File
@@ -7,12 +7,72 @@ import (
"strings"
)
// isWindowsVolumeRoot reports whether a cleaned path is the top of a volume,
// with nothing above it: `C:\`, a bare separator, or a UNC share root.
//
// Detected structurally rather than by pattern matching drive letters, because
// filepath.Dir of a root is that same root and of anything else is strictly
// shorter. That holds for drive-qualified paths, for the separator alone, and
// for UNC roots, on either build host.
func isWindowsVolumeRoot(path string) bool {
cleaned := filepath.Clean(strings.TrimSpace(path))
if cleaned == "" || cleaned == "." {
return false
}
return filepath.Dir(cleaned) == cleaned
}
// validateWindowsACLComponent rejects anything that is not a single path
// component.
//
// This is load-bearing in two places, which is why it lives in the portable file
// rather than beside either of them.
//
// At apply time NtCreateFile happily resolves a RELATIVE name containing
// separators, and it resolves it the ordinary way, so an intermediate junction
// inside that name is followed and the object lands outside the pinned parent.
// A name with a separator reopens exactly the hole the parent handle exists to
// close.
//
// At plan time the same shape escapes the write root: a name is joined onto the
// root to place a deny ACE, so ".." or a separator puts that ACE on a directory
// outside the workspace entirely.
//
// The separators are checked explicitly rather than via filepath.Base, because
// these are Windows paths whatever the build host is, and on Linux
// filepath.Base leaves a backslash-joined name untouched and would wave it
// through. A colon is rejected too: it names an alternate data stream or a
// drive, neither of which is a child.
func validateWindowsACLComponent(name string) error {
switch {
case name == "":
return errors.New("windows ACL path component is empty")
case name == "." || name == "..":
return fmt.Errorf("windows ACL path component %q is a relative reference, not a child", name)
case strings.ContainsAny(name, `\/`):
return fmt.Errorf("windows ACL path component %q contains a separator, so it would resolve through intermediate directories instead of staying a child", name)
case strings.Contains(name, ":"):
return fmt.Errorf("windows ACL path component %q contains a colon, which names a stream or a drive rather than a child", name)
}
return nil
}
type WindowsACLAction string
const (
WindowsACLAllowWrite WindowsACLAction = "allow-write"
WindowsACLDenyRead WindowsACLAction = "deny-read"
WindowsACLDenyWrite WindowsACLAction = "deny-write"
// WindowsACLDenyDelete denies removing or renaming the object it names,
// WITHOUT denying writes to it or inside it, and without inheriting.
//
// It exists for .git. The write-denied carveouts live on .git/config and
// .git/hooks as objects, so replacing the .git directory discards them: the
// recreated config and hooks inherit the workspace allow with no deny, which
// restores credential.helper and core.hooksPath. .git cannot simply join
// sandboxFullyProtectedMetadataNames, because DenyWrite's mask includes
// FILE_GENERIC_WRITE and git must write index, objects and refs.
WindowsACLDenyDelete WindowsACLAction = "deny-delete"
// WindowsACLRevokeCapability removes any existing ACE (allow or deny) for
// Capability at Path, without itself granting or denying anything (applied
// via SetEntriesInAclW's SET_ACCESS mode with a zero mask, not
@@ -41,6 +101,11 @@ type WindowsACLEntry struct {
// sandbox. Empty for an operator-named path, which has no owned tail.
Anchor string `json:"anchor,omitempty"`
Materialize bool `json:"materialize,omitempty"`
// MaterializeFile makes Materialize create an empty FILE instead of a
// directory. Only meaningful with Materialize. .git/config is the case that
// forces the distinction: created as a directory it does not merely carry
// the wrong ACL, it makes `git init` fail outright.
MaterializeFile bool `json:"materializeFile,omitempty"`
}
type WindowsACLPlan struct {
@@ -62,6 +127,34 @@ func BuildWindowsACLPlan(config WindowsSandboxCommandConfig) (WindowsACLPlan, er
Path: capability.Root,
Capability: capability.SID,
})
// The grant above carries DELETE, so the same object guard the principal
// plan has must come with it: not DenyWrite (git writes index, objects and
// refs), not materialized (git creates .git, and an empty one breaks
// git init), and not inherited, so everything underneath stays writable.
entries = append(entries, WindowsACLEntry{
Action: WindowsACLDenyDelete,
Path: windowsRenameProtectedObject(capability.Root),
Capability: capability.SID,
})
// MATERIALIZED, LIKE THE PRINCIPAL PLAN'S, AND FOR TWO REASONS.
//
// First, a guard attached to an object that does not exist is not applied.
// On a workspace that had no .git when setup ran, the first pass skipped all
// three of these as missing and the deferred pass skipped them again,
// because nothing else in this plan created them. Setup still recorded
// success. A later git init then created .git, config and hooks beneath the
// already-granted workspace, where they inherit the allow, DELETE included,
// with no object-specific deny of their own: the sandboxed command could
// rename .git aside, recreate it, and get credential.helper and
// core.hooksPath back.
//
// Second, materializing these is what lets the applier's deferred pass land
// the deny-delete on .git above, since creating .gitconfig and .githooks
// creates .git as their parent.
//
// The principal planner has done this from the start. Sharing the shape
// rather than only the pathname is the point: this tier is the DEFAULT
// backend, so the weaker of the two rules was the one almost everyone got.
for _, path := range capability.ProtectedWriteDenyPaths {
// ANCHORED ONLY WHERE THE ANCHOR IS TRUE. Most of these are derived
// from the root and sit under it, and holding those inside it is the
@@ -75,10 +168,58 @@ func BuildWindowsACLPlan(config WindowsSandboxCommandConfig) (WindowsACLPlan, er
anchor = capability.Root
}
entries = append(entries, WindowsACLEntry{
Action: WindowsACLDenyWrite,
Action: WindowsACLDenyWrite,
Path: path,
Capability: capability.SID,
Anchor: anchor,
Materialize: true,
MaterializeFile: gitMetadataCarveoutIsFile(path),
})
}
}
// Read roots, granted to the read-capability SID.
//
// A profile carrying DenyRead runs the command on a strict token rather than a
// WRITE_RESTRICTED one, and the strict token applies the restricted-SID check
// to reads. Read roots reached that check granted only to the principal's own
// account SID, which the write jail keeps out of the restricting set on
// purpose, so every read failed it — including opening the executable. The
// principal plan still grants the account SID; this is the other half of the
// same grant, so the allow-list and the restriction now come from one place.
// AND IT REFUSES TO EXPRESS "READ EVERYWHERE" AS AN ACE ON THE VOLUME ROOT.
//
// Production profiles seed ReadRoots with the bare filesystem root, so this
// loop used to add an inheritable allow-read for the synthetic read SID at
// "C:\". SetSecurityInfo propagates inheritable ACEs onto existing children,
// so that is not one sandbox-owned object being changed: it walks and rewrites
// DACL inheritance across unrelated system, application and user trees on the
// drive, and a locked or exclusively opened descendant makes the result depend
// on ambient filesystem state.
//
// It is not even complete after paying that price. A bare root resolves on one
// volume, while the executables, DLLs and tool installations a command needs
// can sit on another without appearing as their own read roots, so the strict
// token still fails before its executable starts. Measured: with the read SID
// granted nowhere the strict token cannot open C:WindowsSystem32cmd.exe.
//
// So the profile that needs this is refused, at both setup tiers, rather than
// half-served by a persistent volume-wide ACL edit. That leaves denyRead
// unavailable on Windows until there is a bounded authorization model covering
// the real platform, runtime and executable dependencies on every relevant
// volume, which is what #869 tracks.
readSID, err := windowsReadAllowCapabilitySID(config)
if err != nil {
return WindowsACLPlan{}, err
}
if readSID != "" {
for _, path := range config.PermissionProfile.FileSystem.ReadRoots {
if path = strings.TrimSpace(path); path == "" {
continue
}
entries = append(entries, WindowsACLEntry{
Action: WindowsACLAllowRead,
Path: path,
Capability: capability.SID,
Anchor: anchor,
Capability: readSID,
})
}
}
@@ -114,6 +255,102 @@ func BuildWindowsACLPlan(config WindowsSandboxCommandConfig) (WindowsACLPlan, er
return WindowsACLPlan{Entries: dedupeWindowsACLEntries(entries)}, nil
}
// WindowsACLPlanReadGrantRefusal reports why a plan must not be applied, or "".
//
// ONE ANSWER FOR EVERY TIER THAT APPLIES A PLAN. This started inside the
// unelevated tier, because that is where it was first observed: an ordinary user
// cannot write the volume root's DACL, so every command failed there with a
// generic diagnosis. Elevated setup CAN write it, and that is worse rather than
// better. SetSecurityInfo propagates inheritable ACEs to existing children, so
// applying it rewrites DACL inheritance across unrelated trees, and it still does
// not cover a second volume, so the strict token can fail to open its own
// executable after all that.
//
// KEYED ON THE READ GRANT, NOT ON THE VOLUME ROOT. Checking for a volume root
// tested a symptom of the production profile rather than the thing that is
// unsafe. permissionProfileReadRoots happens to seed the bare filesystem root, so
// that check covered production by coincidence; a profile with a narrowed read
// list and a denyRead still put an inheritable ACE on C:Windows and passed. The
// grant itself is what cannot be applied safely to a directory Zero does not own,
// and the grant exists only for a denyRead profile, so that is what is refused.
func WindowsACLPlanReadGrantRefusal(plan WindowsACLPlan) string {
root := windowsPlanReadGrantTarget(plan)
if root == "" {
return ""
}
return "this sandbox profile configures denyRead, which selects a fully restricted token, and that token applies its restricted-SID check to reads as well as writes. " +
"Serving it needs the read capability granted on directories Zero does not own, starting at " + root + ", which cannot be done safely: the grant is inheritable, so applying it rewrites permissions across unrelated system, application and user directories, " +
"and it still would not cover executables or libraries on another volume. " +
"denyRead is therefore not available on Windows yet (see #869). Remove denyRead from the sandbox configuration to run on a write-restricted token, which keeps the workspace write jail intact"
}
// windowsPlanReadGrantTarget returns the broadest path the plan would grant the
// read capability on that Zero does not already own, preferring a volume root so
// the diagnostic names the worst of them.
//
// A read grant on a write root is Zero's own directory and is not the problem;
// the objection is to writing an inheritable ACE onto somebody else's tree. So
// the write roots are excluded, and an empty answer means every read grant lands
// on a directory this sandbox already governs, which needs no refusal.
func windowsPlanReadGrantTarget(plan WindowsACLPlan) string {
owned := make(map[string]struct{})
for _, entry := range plan.Entries {
if entry.Action == WindowsACLAllowWrite {
owned[strings.ToLower(normalizeProfilePath(entry.Path))] = struct{}{}
}
}
first := ""
for _, entry := range plan.Entries {
if entry.Action != WindowsACLAllowRead {
continue
}
normalized := normalizeProfilePath(entry.Path)
if _, ours := owned[strings.ToLower(normalized)]; ours {
continue
}
if isWindowsVolumeRoot(normalized) {
return entry.Path
}
if first == "" {
first = entry.Path
}
}
return first
}
// windowsPlanVolumeRootGrant returns the first volume root the plan would have
// to change permissions on, or empty when it needs none.
//
// Only elevated setup can write a volume-root DACL, so this is the one entry
// that decides whether a plan is applicable by the unelevated tier at all. The
// check is on the PLAN rather than on the profile because the plan is what gets
// applied: a future entry that lands at a volume root for some other reason is
// caught by the same test.
func windowsPlanVolumeRootGrant(plan WindowsACLPlan) string {
for _, entry := range plan.Entries {
if isWindowsVolumeRoot(normalizeProfilePath(entry.Path)) {
return entry.Path
}
}
return ""
}
// windowsRenameProtectedObject names the object whose DELETE must be denied on
// a write root, whatever trustee holds the grant.
//
// ONE DERIVATION, BECAUSE TWO PLANNERS CONSUME IT. The allow-write mask both
// backends share includes DELETE, and it inherits from the write root onto .git.
// The carveouts that actually protect git live on .git/config and .git/hooks as
// OBJECTS, so renaming .git aside and recreating it discards them: the fresh
// config and hooks inherit the workspace allow with no deny of their own, which
// hands back credential.helper and core.hooksPath. The principal planner denied
// DELETE here and the capability planner did not, so the default restricted-token
// backend was missing the guard entirely. Deriving it in one place is what stops
// a change to the shared mask from updating one consumer and not the other.
func windowsRenameProtectedObject(root string) string {
return filepath.Join(root, sandboxRenameProtectedMetadataName)
}
type windowsWriteRootCapability struct {
Root string
SID string
@@ -175,17 +412,32 @@ func windowsWriteCapabilitySIDs(capabilities []windowsWriteRootCapability) []str
}
func windowsReadDenyCapabilitySIDs(config WindowsSandboxCommandConfig, writeSIDs []string) ([]string, error) {
if len(writeSIDs) > 0 {
return writeSIDs, nil
}
if len(config.PermissionProfile.FileSystem.DenyRead) == 0 {
return nil, nil
}
caps, err := LoadOrCreateWindowsCapabilitySIDs(config.SandboxHome)
// The read-capability SID must be denied here as well as granted above. It
// holds read on the read roots, and those start at the filesystem root, so a
// carveout sitting inside one of them would stay readable through that grant
// and the deny list would quietly stop meaning anything.
// Every SID the token can carry has to be denied, not just the newest one.
// With no write roots the token's only capability is ReadOnly, so dropping it
// here would leave the deny naming a SID the command never holds.
denySIDs := append([]string{}, writeSIDs...)
if len(denySIDs) == 0 {
caps, err := LoadOrCreateWindowsCapabilitySIDs(config.SandboxHome)
if err != nil {
return nil, err
}
denySIDs = append(denySIDs, caps.ReadOnly)
}
readSID, err := windowsReadAllowCapabilitySID(config)
if err != nil {
return nil, err
}
return []string{caps.ReadOnly}, nil
if readSID != "" {
denySIDs = append(denySIDs, readSID)
}
return denySIDs, nil
}
func planWindowsDenyReadPaths(paths []string) []string {
@@ -232,3 +484,19 @@ func dedupeWindowsACLEntries(entries []WindowsACLEntry) []WindowsACLEntry {
}
return out
}
// windowsReadAllowCapabilitySID returns the read-capability SID when this profile
// will run on a strict token, and "" otherwise.
//
// Gated on DenyRead because that is exactly what selects the strict token in the
// runner: with no DenyRead the token stays WRITE_RESTRICTED, reads skip the
// restricted-SID check entirely, and granting read on roots as broad as the
// filesystem root would add ACEs that buy nothing. Derived purely from the
// profile, so the setup half and the command half reach the same answer without
// consulting anything ambient.
func windowsReadAllowCapabilitySID(config WindowsSandboxCommandConfig) (string, error) {
if len(config.PermissionProfile.FileSystem.DenyRead) == 0 {
return "", nil
}
return WindowsReadAllowSID(config.SandboxHome)
}
+602 -44
View File
@@ -6,6 +6,8 @@ import (
"errors"
"fmt"
"os"
"path/filepath"
"slices"
"sort"
"strings"
"unsafe"
@@ -26,28 +28,128 @@ type windowsACLPathGroup struct {
Path string
// Anchor is the write root Path was derived from, empty when the operator
// named the path. See verifyWindowsACLHandleUnderAnchor.
Anchor string
Entries []WindowsACLEntry
Materialize bool
Anchor string
Entries []WindowsACLEntry
Materialize bool
MaterializeFile bool
}
// windowsACLChainStep is one directory component beneath the anchor, and
// whether THIS run created it. The flag comes from the kernel rather than from
// "it was missing when we looked", because something else can win the gap
// between the probe and the create, and removing a directory the sandbox did not
// make is how a rollback deletes a user's data.
type windowsACLChainStep struct {
Name string
Made bool
// ID is the identity of the directory this run created at Name, read from
// the handle that created it. Rollback removes only an object with this
// identity: a created name says the parent is unchanged, not that the
// child has not been renamed aside and replaced since.
ID windowsFileIdentity
}
// windowsACLMaterialization is exactly what materialization created, recorded in
// the shape rollback needs to undo it without resolving a single pathname below
// the anchor.
//
// The anchor is the deepest directory that already existed, and it is the ONLY
// pathname rollback re-resolves. Everything under it is a list of single
// components walked one handle at a time, because a name containing a separator
// is resolved the ordinary way by the kernel and would follow an intermediate
// junction straight out of the approved tree.
type windowsACLMaterialization struct {
AnchorPath string
AnchorID windowsFileIdentity
// Chain is every component between the anchor and the target, shallow to
// deep. All of them are needed to descend at rollback time; only the ones
// with Made set are removed.
Chain []windowsACLChainStep
// File is the leaf file component created inside the deepest Chain entry,
// for the .git/config carveout. Empty when the target is a directory.
File string
FileMade bool
// FileID identifies the leaf file this run created, for the same reason.
FileID windowsFileIdentity
}
func (materialization windowsACLMaterialization) createdAnything() bool {
if materialization.FileMade {
return true
}
for _, step := range materialization.Chain {
if step.Made {
return true
}
}
return false
}
// windowsACLRestoreHook observes restore order. Nil in production; the ordering
// it exposes is load-bearing and was previously pinned by nothing at all,
// despite a comment claiming otherwise.
var windowsACLRestoreHook func(path string)
type windowsACLSnapshot struct {
Path string
Descriptor *windows.SECURITY_DESCRIPTOR
Materialized bool
Path string
Descriptor *windows.SECURITY_DESCRIPTOR
Created windowsACLMaterialization
// TargetID is the object the DACL was read from, so the restore can prove it
// is writing back to that same object rather than to whatever the pathname
// resolves to at rollback time.
//
// A no-follow re-open catches a REPARSE POINT swapped in since apply, and
// that is what the restore relied on. It cannot catch the other
// substitution: rename the target aside and put an ordinary directory of the
// same name in its place. Nothing about that decoy is a reparse point, so the
// re-open succeeds and the old DACL is written onto the attacker's object
// while the real one keeps the aborted setup's ACEs.
//
// Volume serial plus file index is the same identity the materialization
// unwind already anchors on. See reopenWindowsACLDirectoryAsIdentity.
TargetID windowsFileIdentity
}
func applyWindowsACLPlan(plan WindowsACLPlan) (func() error, error) {
groups := groupWindowsACLPlanByPath(plan)
snapshots := make([]windowsACLSnapshot, 0, len(groups))
abort := func(err error) (func() error, error) {
if rollbackErr := rollbackWindowsACLSnapshots(snapshots); rollbackErr != nil {
return nil, fmt.Errorf("%w; rollback failed: %v", err, rollbackErr)
}
return nil, err
}
var deferred []windowsACLPathGroup
for _, group := range groups {
snapshot, applied, err := applyWindowsACLPathGroup(group)
if err != nil {
rollbackErr := rollbackWindowsACLSnapshots(snapshots)
if rollbackErr != nil {
return nil, fmt.Errorf("%w; rollback failed: %v", err, rollbackErr)
}
return nil, err
return abort(err)
}
if applied {
snapshots = append(snapshots, snapshot)
continue
}
deferred = append(deferred, group)
}
// A group that applied to nothing was skipped because its target did not
// exist and the group does not materialize one. A LATER group can still
// create it, so the skip has to be retried rather than treated as final.
//
// The .git rename guard is exactly this shape and was silently absent
// because of it. .git must NOT be materialized, since an empty one breaks
// `git init`, so its deny-delete group carries no Materialize. But .git does
// get created, as the parent chain of the .git\config carveout, and that
// group sorts AFTER it. So on every workspace that did not already have a
// .git, the guard was skipped, the directory appeared moments later, and
// nothing went back for it: the principal could then rename .git aside and
// shed the config and hooks carveouts, which is the escape the guard exists
// to stop. Groups that are genuinely absent simply skip again here.
for _, group := range deferred {
snapshot, applied, err := applyWindowsACLPathGroup(group)
if err != nil {
return abort(err)
}
if applied {
snapshots = append(snapshots, snapshot)
@@ -72,6 +174,7 @@ func groupWindowsACLPlanByPath(plan WindowsACLPlan) []windowsACLPathGroup {
}
group.Entries = append(group.Entries, entry)
group.Materialize = group.Materialize || entry.Materialize
group.MaterializeFile = group.MaterializeFile || entry.MaterializeFile
// One path is derived from at most one root, so the first anchor seen is
// the anchor. Taking it rather than overwriting keeps a later
// operator-named duplicate of the same path from clearing it.
@@ -101,8 +204,42 @@ func applyWindowsACLPathGroup(group windowsACLPathGroup) (windowsACLSnapshot, bo
// elevated setup a lower-privileged local user could swap the target for a
// symlink/junction between operations and redirect the ACL change onto a
// system object it never validated (issue #728, a TOCTOU privilege boundary).
materialized := false
handle, isDir, err := openWindowsACLTarget(path)
// Reject a malformed group BEFORE touching the filesystem. This validation
// used to run after materialization, so a bad SID or an unknown action
// created a directory chain and only then failed, leaving the error path to
// unwind work that never needed doing. Nothing here depends on isDir: that
// argument only selects the inheritance flag, while the errors come from the
// action lookup and the SID parse.
if _, _, err := prepareWindowsACLPathGroupEntries(group.Entries, false, nil); err != nil {
return windowsACLSnapshot{}, false, err
}
var created windowsACLMaterialization
var handle windows.Handle
// Every exit from here goes through one closure, because there are now two
// things to undo rather than one: the open handle, and whatever
// materialization created. Both are captured by reference and both start
// zero, so calling this before either is set is safe and does nothing.
//
// The unwind is handle-relative. It must never fall back to a pathname
// delete: the failure being cleaned up here can BE the path swap, and
// os.RemoveAll on a swapped ancestor is precisely the recursive elevated
// delete outside the workspace that this cleanup is supposed to prevent.
fail := func(err error) (windowsACLSnapshot, bool, error) {
if handle != 0 {
_ = windows.CloseHandle(handle)
}
// The apply itself is failing, so nothing has been left with a DACL to
// restore; only the removal outcome matters here.
if _, unwindErr := rollbackWindowsACLMaterialization(created); unwindErr != nil {
return windowsACLSnapshot{}, false, fmt.Errorf("%w; cleanup failed: %v", err, unwindErr)
}
return windowsACLSnapshot{}, false, err
}
var isDir bool
var err error
handle, isDir, err = openWindowsACLTargetFinalComponent(path)
if err != nil {
if !errors.Is(err, os.ErrNotExist) {
return windowsACLSnapshot{}, false, err
@@ -118,26 +255,20 @@ func applyWindowsACLPathGroup(group windowsACLPathGroup) (windowsACLSnapshot, bo
// elevated setup create the directory outside the write root and only the
// containment check below would notice, after the fact.
if err := verifyWindowsACLPathUnderAnchor(group.Anchor, path); err != nil {
return windowsACLSnapshot{}, false, err
return fail(err)
}
if err := os.MkdirAll(path, 0o700); err != nil {
return windowsACLSnapshot{}, false, fmt.Errorf("materialize windows ACL target %s: %w", path, err)
}
materialized = true
handle, isDir, err = openWindowsACLTarget(path)
// created is assigned even on failure: materialization reports what it
// managed to make before it stopped, and fail() unwinds exactly that.
created, err = materializeWindowsACLTarget(path, group.MaterializeFile)
if err != nil {
_ = os.RemoveAll(path)
return windowsACLSnapshot{}, false, fmt.Errorf("open materialized windows ACL target %s: %w", path, err)
return fail(fmt.Errorf("materialize windows ACL target %s: %w", path, err))
}
}
// From here the handle is open; every early return must close it first (and
// remove a freshly materialized target) so a failure leaks neither.
fail := func(err error) (windowsACLSnapshot, bool, error) {
_ = windows.CloseHandle(handle)
if materialized {
_ = os.RemoveAll(path)
handle, isDir, err = openWindowsACLTargetFinalComponent(path)
if err != nil {
// This is the branch that fires when the post-create verify catches a
// swap, so it is the single most important cleanup in the file.
return fail(fmt.Errorf("open materialized windows ACL target %s: %w", path, err))
}
return windowsACLSnapshot{}, false, err
}
// THE OBJECT HAS TO BE WHERE THE PLAN SAID IT WOULD BE. The open above
// refuses a reparse point at the final component and resolves every one
@@ -176,8 +307,14 @@ func applyWindowsACLPathGroup(group windowsACLPathGroup) (windowsACLSnapshot, bo
// The handle has served its purpose (read+write bound to one object) and is
// closed now — rollback re-opens no-follow rather than holding a handle for
// the whole sandbox lifetime, since one caller discards the rollback closure.
// Captured BEFORE the handle closes, because that handle is the only thing
// that names the object rather than the path.
targetID, err := windowsIdentityOfHandle(handle)
if err != nil {
return fail(fmt.Errorf("read windows ACL target identity for %s: %w", path, err))
}
_ = windows.CloseHandle(handle)
return windowsACLSnapshot{Path: path, Descriptor: descriptor, Materialized: materialized}, true, nil
return windowsACLSnapshot{Path: path, Descriptor: descriptor, Created: created, TargetID: targetID}, true, nil
}
// openWindowsACLTarget opens path for reading and rewriting its DACL without
@@ -189,6 +326,30 @@ func applyWindowsACLPathGroup(group windowsACLPathGroup) (windowsACLSnapshot, bo
// is exactly the redirection this guard exists to prevent. A missing target is
// surfaced as os.ErrNotExist so the caller's materialize path still fires.
func openWindowsACLTarget(path string) (windows.Handle, bool, error) {
handle, isDir, err := openWindowsACLTargetFinalComponent(path)
if err != nil {
return 0, false, err
}
// Ancestors are resolved by CreateFile even with FILE_FLAG_OPEN_REPARSE_POINT,
// so the final-component check is not enough on its own here: this opener
// serves the rollback re-open and the runtime ACE, which know no anchor and
// must not be redirected by anything on the way down.
if err := verifyWindowsACLTargetNotRedirected(handle, path); err != nil {
_ = windows.CloseHandle(handle)
return 0, false, err
}
return handle, isDir, nil
}
// openWindowsACLTargetFinalComponent is the open without the ancestor check.
// The plan apply uses it: a reparse point ABOVE a target is the operator's
// business (a workspace on a junction or a dev drive is a configuration that
// works), and a reparse point on a tail this package derived from a write root
// is caught by verifyWindowsACLHandleUnderAnchor, which knows the anchor and
// tolerates exactly the aliases above it. That is main's rule from #1040 and
// the two containment tests pin it; the blanket refusal above is kept for the
// callers that have no anchor to reason with.
func openWindowsACLTargetFinalComponent(path string) (windows.Handle, bool, error) {
utf16Path, err := windows.UTF16PtrFromString(path)
if err != nil {
return 0, false, fmt.Errorf("encode windows ACL target %s: %w", path, err)
@@ -270,13 +431,27 @@ func prepareWindowsACLPathGroupEntries(entries []WindowsACLEntry, isDir bool, ol
return nil, nil, err
}
inheritance := uint32(0)
if isDir && !entry.NoInherit {
// DenyDelete governs the object it names and nothing beneath it. Inherited
// onto .git's children it would deny DELETE on every file inside, so git
// could not remove a lock file, a ref, or anything else it rewrites, and
// the guard would read as a broken repository rather than as a blocked
// rename. Decided here, not in the planner, so no plan can make it inherit.
if isDir && !entry.NoInherit && entry.Action != WindowsACLDenyDelete {
inheritance = windows.SUB_CONTAINERS_AND_OBJECTS_INHERIT
}
entryInheritance := inheritance
// DenyDelete governs the object it names and nothing beneath it. Inherited
// onto .git's children it would deny DELETE on every file inside, so git
// could not remove a lock file, a ref, or anything else it rewrites, and
// the guard would read as a broken repository rather than as a blocked
// rename.
if entry.Action == WindowsACLDenyDelete {
entryInheritance = windows.NO_INHERITANCE
}
out = append(out, windows.EXPLICIT_ACCESS{
AccessPermissions: permissions,
AccessMode: accessMode,
Inheritance: inheritance,
Inheritance: entryInheritance,
Trustee: windows.TRUSTEE{
TrusteeForm: windows.TRUSTEE_IS_SID,
TrusteeType: windows.TRUSTEE_IS_GROUP,
@@ -585,13 +760,61 @@ func windowsAceSID(ace *windows.ACCESS_ALLOWED_ACE) (sid *windows.SID, ok bool)
func windowsACLAccess(action WindowsACLAction) (windows.ACCESS_MODE, windows.ACCESS_MASK, error) {
switch action {
case WindowsACLAllowWrite:
return windows.GRANT_ACCESS, windows.FILE_GENERIC_READ | windows.FILE_GENERIC_WRITE | windows.FILE_GENERIC_EXECUTE, nil
// DELETE is part of the grant, not an extra. FILE_GENERIC_WRITE covers
// creating and modifying but not removing or renaming, and a rename needs
// delete access on the source. Under the old same-user token that gap was
// invisible, because the caller already held inherited rights on its own
// tree; a sandbox principal is a separate account with no such
// inheritance, so without DELETE it can write a file it can never delete.
// Ordinary editing and most git operations rewrite files by replacing
// them, so the omission fails normal work rather than an edge case.
//
// FILE_DELETE_CHILD is deliberately NOT granted, for the same reason
// WRITE_DAC and WRITE_OWNER are not. On a parent it authorises deleting a
// child whatever the child's own DACL says, so granting it on a write root
// hands back the write-denied carve-outs underneath it: a principal could
// delete .git/config and recreate it, and the replacement inherits this
// grant with no deny of its own — restoring exactly the credential.helper
// and core.hooksPath control the carve-out exists to prevent.
//
// It was granted here originally to keep the mask symmetric with
// WindowsACLDenyWrite, which does treat FILE_DELETE_CHILD as part of
// write. Symmetry is the wrong goal: denying a capability is not a reason
// to grant it. DELETE alone covers removing and renaming files the
// principal owns inside its roots, which is what the grant is for.
return windows.GRANT_ACCESS, windows.FILE_GENERIC_READ | windows.FILE_GENERIC_WRITE | windows.FILE_GENERIC_EXECUTE | windows.DELETE, nil
case WindowsACLAllowRead:
// Read and traverse without write. A sandbox principal is a separate
// account with no inherent access to the caller's tree, so a read-only
// root has to be granted rather than assumed. Deliberately omits
// FILE_GENERIC_WRITE, DELETE and WRITE_DAC.
return windows.GRANT_ACCESS, windows.FILE_GENERIC_READ | windows.FILE_GENERIC_EXECUTE, nil
case windowsACLRevoke:
// REVOKE_ACCESS drops every ACE naming the trustee regardless of the mask,
// so the mask is ignored here. Used to retire a principal without having
// to remember which access each path was granted.
return windows.REVOKE_ACCESS, 0, nil
case WindowsACLDenyRead:
return windows.DENY_ACCESS, windows.FILE_GENERIC_READ | windows.FILE_GENERIC_EXECUTE, nil
case WindowsACLDenyWrite:
return windows.DENY_ACCESS, (windows.FILE_GENERIC_WRITE | windows.DELETE | windowsFileDeleteChild | windows.WRITE_DAC | windows.WRITE_OWNER) &^ windows.SYNCHRONIZE, nil
case WindowsACLDenyDelete:
// Deny removing or RENAMING the object itself, nothing more. Renaming a
// directory needs DELETE on that directory, so denying DELETE is what
// stops .git being moved aside and recreated without its carveouts.
//
// WRITE_DAC and WRITE_OWNER come along because a guard the principal can
// rewrite, or take ownership of and then rewrite, is not a guard.
//
// FILE_GENERIC_WRITE is deliberately absent: git writes index, objects and
// refs constantly, and denying it would break every commit rather than the
// rename. FILE_DELETE_CHILD is absent for the same reason one level down,
// since git deletes its own lock files and refs. Neither is needed here:
// this ACE does not inherit (see prepareWindowsACLPathGroupEntries), so it
// governs the .git directory object alone.
return windows.DENY_ACCESS, windows.DELETE | windows.WRITE_DAC | windows.WRITE_OWNER, nil
case WindowsACLRevokeCapability:
// Handled specially in windowsExplicitAccessEntries (preserve DenyRead).
// Handled specially in prepareWindowsACLPathGroupEntries (preserve DenyRead).
return windows.SET_ACCESS, 0, nil
default:
return 0, 0, fmt.Errorf("unsupported windows ACL action %q", action)
@@ -600,29 +823,87 @@ func windowsACLAccess(action WindowsACLAction) (windows.ACCESS_MODE, windows.ACC
func rollbackWindowsACLSnapshots(snapshots []windowsACLSnapshot) error {
var errs []error
// Reverse order is load-bearing twice over. Sorted ascending by path key, an
// ancestor key is always a proper prefix of its descendants, so walking
// backwards unwinds descendant before ancestor: a materialized directory is
// therefore empty by the time its own removal is attempted. Restoring ACLs in
// the same order is independently right, because SetSecurityInfo propagates
// inheritable ACEs down, so the ancestor must go last.
// TestRollbackUnwindsDescendantsBeforeAncestors pins it.
//
// SORTED HERE, NOT ASSUMED. The groups are sorted, but the snapshots are in
// APPLY order, and applyWindowsACLPlan's deferred pass appends a group whose
// target only appeared during the first pass, which is typically an ancestor
// of first-pass groups (.git after .git\config). Walking that list backwards
// restored the ancestor first. Reported by CodeRabbit;
// TestRollbackUnwindsADeferredAncestorAfterItsDescendants pins it.
snapshots = slices.Clone(snapshots)
sort.SliceStable(snapshots, func(i, j int) bool {
return windowsCapabilityPathKey(snapshots[i].Path) < windowsCapabilityPathKey(snapshots[j].Path)
})
for index := len(snapshots) - 1; index >= 0; index-- {
snapshot := snapshots[index]
if snapshot.Materialized {
if err := os.RemoveAll(snapshot.Path); err != nil {
errs = append(errs, fmt.Errorf("remove materialized windows ACL target %s: %w", snapshot.Path, err))
if snapshot.Created.createdAnything() {
removed, err := rollbackWindowsACLMaterialization(snapshot.Created)
if err != nil {
errs = append(errs, err)
}
// Only skip the restore when the object carrying the DACL is actually
// gone. A racer can win the leaf while this run made its parent, and
// then the aggregate says "ours" about a file that is not: the parent
// cannot be removed because it is non-empty, and skipping here left a
// pre-existing file wearing an aborted setup's ACL. Falling through
// reaches the same no-follow, TargetID-guarded restore as any other
// snapshot, which refuses on a mismatch rather than forcing.
if removed {
continue
}
continue
}
dacl, _, err := snapshot.Descriptor.DACL()
if err != nil {
errs = append(errs, fmt.Errorf("read rollback windows DACL for %s: %w", snapshot.Path, err))
continue
}
// Re-open no-follow rather than restoring by pathname: the restore must
// land on the real object, not a reparse point swapped in since apply. The
// residual window is small because the target is ACL-restricted by now, but
// a handle keeps the restore honest. On a materialized-target rollback we
// remove it above, so only the restore-existing path opens here.
handle, _, err := openWindowsACLTarget(snapshot.Path)
// Re-open no-follow AND prove it is the same object. The no-follow open
// alone only rules out a reparse point swapped in since apply; a target
// renamed aside and replaced by an ordinary directory of the same name
// passes it, and the old DACL would land on the decoy while the real
// object kept the aborted setup's ACEs. See windowsACLSnapshot.TargetID.
handle, _, err := openWindowsACLTargetFinalComponent(snapshot.Path)
if err != nil {
errs = append(errs, fmt.Errorf("re-open windows ACL target %s for rollback: %w", snapshot.Path, err))
continue
}
// An identity to compare against makes the pathname route irrelevant: the
// object either is the one the DACL was read from or it is not. Without
// one, the route is all there is, so keep the blanket redirection check.
if snapshot.TargetID.empty() {
if err := verifyWindowsACLTargetNotRedirected(handle, snapshot.Path); err != nil {
_ = windows.CloseHandle(handle)
errs = append(errs, fmt.Errorf("re-open windows ACL target %s for rollback: %w", snapshot.Path, err))
continue
}
}
if !snapshot.TargetID.empty() {
got, identityErr := windowsIdentityOfHandle(handle)
if identityErr != nil {
_ = windows.CloseHandle(handle)
errs = append(errs, fmt.Errorf("read rollback identity for %s: %w", snapshot.Path, identityErr))
continue
}
if got != snapshot.TargetID {
// REFUSED, not forced through. Leaving the real object with the
// aborted setup's ACEs is the safe direction: the caller is failing
// anyway, and writing a stale DACL onto an object setup never
// touched is the one outcome rollback must not produce.
_ = windows.CloseHandle(handle)
errs = append(errs, fmt.Errorf("refusing to restore windows ACL for %s: it is no longer the object setup applied to", snapshot.Path))
continue
}
}
if windowsACLRestoreHook != nil {
windowsACLRestoreHook(snapshot.Path)
}
if err := windows.SetSecurityInfo(handle, windows.SE_FILE_OBJECT, windows.DACL_SECURITY_INFORMATION, nil, nil, dacl, nil); err != nil {
errs = append(errs, fmt.Errorf("rollback windows ACL for %s: %w", snapshot.Path, err))
}
@@ -630,3 +911,280 @@ func rollbackWindowsACLSnapshots(snapshots []windowsACLSnapshot) error {
}
return errors.Join(errs...)
}
// materializeWindowsACLTarget creates a missing ACL target with the shape the
// owning tool expects. A directory target is created whole; a file target gets
// its parent chain created and then an empty file, because creating it as a
// directory would break the tool that owns it rather than just mis-ACL it.
// The returned record is meaningful even when the error is non-nil: a chain that
// got three levels deep and then failed still has three levels to unwind.
func materializeWindowsACLTarget(path string, asFile bool) (windowsACLMaterialization, error) {
directory := path
leaf := ""
if asFile {
directory = filepath.Dir(path)
leaf = filepath.Base(path)
}
created, parent, err := makeWindowsACLDirChainNoFollow(directory)
if err != nil {
return created, err
}
defer func() { _ = windows.CloseHandle(parent) }()
if !asFile {
return created, nil
}
// windowsACLRacedLeafHook fires at the ONE instant a racer can win the leaf
// while this run already owns the chain above it: the directories exist and
// the file does not yet. That mixed ownership is what made the old rollback
// skip its restore, and it is unreachable from the anchor-stage hook, which
// fires before the chain exists at all. Always nil in production.
if windowsACLRacedLeafHook != nil {
windowsACLRacedLeafHook(path)
}
// A racing creator winning is still fine: the target exists, which is all
// materialization needed. createWindowsACLChildFile reports that as
// created=false, so rollback will not delete a file the sandbox did not make.
created.File = leaf
madeFile, fileID, err := createWindowsACLChildFile(parent, leaf)
created.FileMade = madeFile
if madeFile {
created.FileID = fileID
}
return created, err
}
// rollbackWindowsACLMaterialization removes exactly what materialization
// created, deepest first, without resolving any pathname below the anchor.
//
// This is the other half of the pathname problem. The old cleanup called
// os.RemoveAll on the target pathname, which re-resolves every ancestor at the
// moment it runs, so an ancestor swapped to a junction after the object was
// created sent a recursive elevated delete into an unrelated tree. It also only
// ever removed the final component, leaving every intermediate directory the
// chain had created behind.
//
// The anchor is the one pathname that has to be resolved again, and it is
// checked by file identity rather than by name: replacing a directory with
// another REAL directory of the same name needs no reparse point at all and
// would otherwise pass every no-follow check there is.
//
// Residue is preferable to over-deletion throughout. When something cannot be
// removed safely this reports it and leaves it, and never falls back to a
// pathname delete.
// rollbackWindowsACLMaterialization removes what this run created and reports
// whether the ACL-BEARING TARGET is among what it removed.
//
// AGGREGATE OWNERSHIP IS NOT THE TARGET'S DISPOSITION. The caller used to treat
// createdAnything() as "this run owns the object it applied a DACL to", which is
// an OR across the whole materialization record. When this run creates the
// parent chain and a racer wins the leaf, that is true while the ACL-bearing
// file belongs to somebody else. The caller then skipped the identity-validated
// restore and left a pre-existing file carrying an aborted setup's ACL.
//
// The target is the file leaf when FileMade is set, and the deepest chain entry
// otherwise. Anything this cannot prove it removed reports false, which routes
// the caller to a restore that is already no-follow and TargetID-guarded, so the
// conservative direction is the default.
func rollbackWindowsACLMaterialization(materialization windowsACLMaterialization) (targetRemoved bool, err error) {
if !materialization.createdAnything() {
return false, nil
}
anchor, anchorErr := reopenWindowsACLDirectoryAsIdentity(materialization.AnchorPath, materialization.AnchorID)
if anchorErr != nil {
if errors.Is(anchorErr, os.ErrNotExist) {
// The anchor is gone, so everything created beneath it is gone too,
// the target included. Nothing to undo, and no way to undo it.
return true, nil
}
return false, fmt.Errorf("unwind windows ACL materialization under %s: %w", materialization.AnchorPath, anchorErr)
}
// One handle per level: handles[i] is the parent of Chain[i], which is what
// deleting Chain[i] relative to a pinned parent requires.
handles := []windows.Handle{anchor}
defer func() {
for _, handle := range handles {
if handle != 0 {
_ = windows.CloseHandle(handle)
}
}
}()
// Descend only as far as is actually required. Removing a directory needs its
// PARENT's handle, not its own, so the deepest component is opened only when
// a file leaf lives inside it. This is not just economy: the deepest
// component is usually the ACL target itself, so it may already carry the
// deny-read ACE this rollback is undoing, and opening it would be refused by
// the very ACL being unwound.
needed := len(materialization.Chain)
if !materialization.FileMade && needed > 0 {
needed--
}
depth := 0
for ; depth < needed; depth++ {
child, openErr := openWindowsACLChildDirectory(handles[depth], materialization.Chain[depth].Name)
if openErr != nil {
// Already removed by something else. Stop descending; whatever is
// below it is gone with it.
if isWindowsNotExist(openErr) {
break
}
return false, fmt.Errorf("unwind windows ACL materialization under %s: %w", materialization.AnchorPath, openErr)
}
// A component this run created has to still be the object it created
// before anything beneath it is touched: an ordinary directory renamed
// into its place beneath the unchanged anchor is not ours to descend
// into, let alone delete.
if step := materialization.Chain[depth]; step.Made {
got, identityErr := windowsIdentityOfHandle(child)
if identityErr != nil {
_ = windows.CloseHandle(child)
return false, fmt.Errorf("unwind windows ACL materialization under %s: identify %s: %w", materialization.AnchorPath, step.Name, identityErr)
}
if got != step.ID {
_ = windows.CloseHandle(child)
return false, fmt.Errorf("refusing to unwind windows ACL materialization under %s: %s is no longer the directory setup created", materialization.AnchorPath, step.Name)
}
}
handles = append(handles, child)
}
var errs []error
// An ancestor vanished mid-descent, so the target went with it.
targetRemoved = depth < needed
// The file leaf lives inside the deepest chain directory, so it goes first
// and only if the descent actually reached that far.
if materialization.FileMade && depth == needed {
if err := deleteWindowsACLChildFileAs(handles[len(handles)-1], materialization.File, materialization.FileID); err != nil {
errs = append(errs, fmt.Errorf("remove materialized windows ACL file %s: %w", materialization.File, err))
} else {
targetRemoved = true
}
}
// Chain[i] is removed through handles[i], so the deepest one that can be
// removed is bounded by how far the descent actually got.
deepest := len(handles) - 1
if last := len(materialization.Chain) - 1; deepest > last {
deepest = last
}
for index := deepest; index >= 0; index-- {
// Close the child's own handle, if the descent opened one, before asking
// its parent to remove it. A directory with a live handle open still
// counts as present, so the parent's delete would come back as non-empty.
if index+1 < len(handles) && handles[index+1] != 0 {
_ = windows.CloseHandle(handles[index+1])
handles[index+1] = 0
}
if !materialization.Chain[index].Made {
continue
}
if err := deleteWindowsACLChildDirectoryAs(handles[index], materialization.Chain[index].Name, materialization.Chain[index].ID); err != nil {
errs = append(errs, fmt.Errorf("remove materialized windows ACL directory %s: %w", materialization.Chain[index].Name, err))
continue
}
// The deepest chain entry IS the ACL target for a directory
// materialization, and it is the leaf's parent when a racer made the leaf,
// so removing it means the target is gone either way.
if !materialization.FileMade && index == len(materialization.Chain)-1 {
targetRemoved = true
}
}
return targetRemoved, errors.Join(errs...)
}
// windowsACLMaterializeSwapHook is a test seam and nothing else. It fires inside
// makeWindowsACLDirChainNoFollow at the exact instant the race used to be
// exploitable: the anchor is verified and pinned, and nothing has been created
// yet. A race reproducible only by luck is not a regression test, so the instant
// is made addressable rather than hoped for. Always nil in production.
var windowsACLMaterializeSwapHook func(anchor string)
// windowsACLRacedLeafHook fires after the directory chain is created and before
// the file leaf is. See materializeWindowsACLTarget. Always nil in production.
var windowsACLRacedLeafHook func(path string)
// makeWindowsACLDirChainNoFollow is an os.MkdirAll that never resolves a
// pathname below its anchor.
//
// It walks UP to the deepest ancestor that already exists and opens it
// no-follow. Because GetFinalPathNameByHandle answers for the whole resolved
// path, that single check clears every ancestor above it too. Then it walks back
// DOWN, creating one component at a time relative to the HANDLE of the level
// above, so the tree it descends is pinned to objects rather than named by
// strings.
//
// That is the difference that matters. This used to verify a component by
// pathname, close the handle, and then hand the same string to os.Mkdir: two
// independent kernel resolutions with a gap between them. A workspace owner who
// swapped the verified ancestor for a junction inside that gap got the component
// created outside the approved tree, as Administrator, and verifying again
// afterwards cannot un-create it. Junctions need no privilege, so this was
// reachable by exactly the unprivileged user the sandbox exists to contain.
//
// It deliberately does NOT re-verify each created component by pathname. A child
// created relative to a pinned parent is in the right place by construction, so
// comparing pathnames afterwards would add nothing and would reject correct
// creates whenever the tree was legitimately renamed mid-setup.
//
// Returns what it created, plus an open handle to the deepest directory which
// the caller must close.
func makeWindowsACLDirChainNoFollow(dir string) (windowsACLMaterialization, windows.Handle, error) {
cleaned := filepath.Clean(strings.TrimSpace(dir))
if cleaned == "" || cleaned == "." {
return windowsACLMaterialization{}, 0, fmt.Errorf("materialize windows ACL target: empty directory path %q", dir)
}
// Walk up to the deepest ancestor that exists, collecting the component
// NAMES that are missing. Names, not paths: everything below the anchor is
// addressed relative to a handle from here on.
var missing []string
current := cleaned
var anchor windows.Handle
var anchorID windowsFileIdentity
for {
handle, identity, err := openWindowsACLDirectoryNoFollowWithIdentity(current)
if err == nil {
anchor, anchorID = handle, identity
break
}
if !errors.Is(err, os.ErrNotExist) {
return windowsACLMaterialization{}, 0, err
}
parent := filepath.Dir(current)
if parent == current {
return windowsACLMaterialization{}, 0, fmt.Errorf("materialize windows ACL target %s: no existing ancestor to anchor on", dir)
}
missing = append(missing, filepath.Base(current))
current = parent
}
created := windowsACLMaterialization{AnchorPath: current, AnchorID: anchorID}
if hook := windowsACLMaterializeSwapHook; hook != nil {
hook(current)
}
// Walk back down, one component per handle. The anchor handle is released as
// soon as its child is open, so at most two levels are held at once.
parent := anchor
for index := len(missing) - 1; index >= 0; index-- {
name := missing[index]
child, madeNow, err := createWindowsACLChildDirectory(parent, name)
if err != nil {
_ = windows.CloseHandle(parent)
return created, 0, err
}
step := windowsACLChainStep{Name: name, Made: madeNow}
if madeNow {
if step.ID, err = windowsIdentityOfHandle(child); err != nil {
_ = windows.CloseHandle(parent)
_ = windows.CloseHandle(child)
return created, 0, fmt.Errorf("identify materialized windows ACL directory %s: %w", name, err)
}
}
created.Chain = append(created.Chain, step)
_ = windows.CloseHandle(parent)
parent = child
}
return created, parent, nil
}
@@ -37,8 +37,15 @@ func TestApplyWindowsACLPathGroupHandleBasedRoundTrip(t *testing.T) {
if !applied {
t.Fatal("applied = false, want true for an existing directory target")
}
if snapshot.Path != dir || snapshot.Materialized {
t.Fatalf("snapshot = %#v, want Path=%q Materialized=false", snapshot, dir)
if snapshot.Path != dir {
t.Fatalf("snapshot.Path = %q, want %q", snapshot.Path, dir)
}
// The target already existed, so nothing was created and rollback must have
// nothing to remove. Asserting the chain rather than a bool matters: a
// rewiring that recorded the walked components instead of only the created
// ones would make rollback delete a directory the sandbox never made.
if snapshot.Created.createdAnything() {
t.Fatalf("snapshot recorded %#v as created for a target that already existed", snapshot.Created)
}
if snapshot.Descriptor == nil {
t.Fatal("snapshot has no captured descriptor to roll back to")
@@ -110,8 +117,21 @@ func TestApplyWindowsACLPathGroupMaterializes(t *testing.T) {
if err != nil {
t.Fatalf("applyWindowsACLPathGroup: %v", err)
}
if !applied || !snapshot.Materialized {
t.Fatalf("applied=%v materialized=%v, want both true", applied, snapshot.Materialized)
if !applied {
t.Fatal("applied = false, want true for a materialized target")
}
// Exactly one component was missing, so exactly one must be recorded as
// created, and it must be the leaf's own name rather than a path, carrying
// the identity of the directory it made so rollback can prove it is still
// deleting that object.
if len(snapshot.Created.Chain) != 1 || snapshot.Created.Chain[0].Name != "created" || !snapshot.Created.Chain[0].Made {
t.Fatalf("created chain = %#v, want one step {created true}", snapshot.Created.Chain)
}
if snapshot.Created.Chain[0].ID.empty() {
t.Fatalf("created chain step carries no identity: %#v", snapshot.Created.Chain[0])
}
if snapshot.Created.AnchorPath != filepath.Dir(target) {
t.Fatalf("anchor = %q, want the existing parent %q", snapshot.Created.AnchorPath, filepath.Dir(target))
}
if _, err := os.Stat(target); err != nil {
t.Fatalf("materialized target not created: %v", err)
@@ -0,0 +1,122 @@
//go:build windows
package sandbox
import (
"os"
"path/filepath"
"testing"
"unsafe"
"golang.org/x/sys/windows"
)
// gitGuardDenyDeleteApplied reports whether the applied DACL on path carries a
// DENY ace granting DELETE to sid. Read back from the object rather than from
// the plan, because the plan is what was already wrong.
func gitGuardDenyDeleteApplied(t *testing.T, path string, sid string) bool {
t.Helper()
handle, _, err := openWindowsACLTarget(path)
if err != nil {
t.Fatalf("open %s: %v", path, err)
}
defer func() { _ = windows.CloseHandle(handle) }()
descriptor, err := windows.GetSecurityInfo(handle, windows.SE_FILE_OBJECT, windows.DACL_SECURITY_INFORMATION)
if err != nil {
t.Fatalf("read the DACL of %s: %v", path, err)
}
dacl, _, err := descriptor.DACL()
if err != nil || dacl == nil {
t.Fatalf("read the DACL of %s: %v", path, err)
}
wanted, err := windows.StringToSid(sid)
if err != nil {
t.Fatalf("parse the capability SID %q: %v", sid, err)
}
// GetAce hands back a generic header that is reinterpreted here. Sound only
// for the fixed-layout ACE types: an object ACE carries Flags and two GUIDs
// ahead of the trustee, so SidStart would land mid-structure. Allowed and
// denied ACEs share that fixed layout, and nothing under test builds an
// object ACE, so a type this does not recognise is skipped rather than
// decoded into a nonsense SID.
for index := uint32(0); index < uint32(dacl.AceCount); index++ {
var ace *windows.ACCESS_ALLOWED_ACE
if err := windows.GetAce(dacl, index, &ace); err != nil {
continue
}
if ace.Header.AceType != windows.ACCESS_DENIED_ACE_TYPE {
continue
}
aceSID := (*windows.SID)(unsafe.Pointer(&ace.SidStart))
if !aceSID.Equals(wanted) {
continue
}
if ace.Mask&windows.DELETE != 0 {
return true
}
}
return false
}
// THE GUARD BELONGS TO THE GRANT, NOT TO ONE PLANNER.
//
// The allow-write mask both backends share includes DELETE, and it inherits from
// the write root onto .git. What protects git is attached to .git/config and
// .git/hooks as OBJECTS, so renaming .git aside and recreating it discards those
// carveouts: the fresh config and hooks inherit the workspace allow with no deny
// of their own, which hands back credential.helper and core.hooksPath.
//
// The principal planner denied DELETE on .git; the capability planner did not,
// and the capability backend is the default. So on the reachable path the
// caller's own token and the capability restricting SID could both authorise the
// rename.
//
// Read back from the applied object, not asserted on the plan, because the plan
// is exactly what was wrong. DACL edits on a user-owned directory need no
// Administrator rights, so this runs unelevated.
func TestCapabilityPlanDeniesDeleteOnGit(t *testing.T) {
workspace := t.TempDir()
gitDir := filepath.Join(workspace, ".git")
if err := os.MkdirAll(gitDir, 0o700); err != nil {
t.Fatal(err)
}
config := WindowsSandboxCommandConfig{
SandboxHome: t.TempDir(),
CommandCWD: workspace,
WorkspaceRoots: []string{workspace},
PermissionProfile: PermissionProfile{
FileSystem: FileSystemPolicy{
Kind: FileSystemRestricted,
WriteRoots: []WritableRoot{{Root: workspace}},
},
},
}
plan, err := BuildWindowsACLPlan(config)
if err != nil {
t.Fatalf("BuildWindowsACLPlan: %v", err)
}
sid, err := windowsCapabilitySIDForWriteRoot(config, workspace)
if err != nil {
t.Fatalf("resolve the workspace capability SID: %v", err)
}
// SETUP: the plan must actually grant this root, or the guard below would be
// vacuously satisfied by a plan that grants nothing.
granted := false
for _, entry := range plan.Entries {
if entry.Action == WindowsACLAllowWrite && entry.Path == workspace {
granted = true
}
}
if !granted {
t.Fatalf("SETUP INVALID: the capability plan does not grant write on %s", workspace)
}
if _, err := applyWindowsACLPlan(plan); err != nil {
t.Skipf("cannot apply an ACL plan here: %v", err)
}
if !gitGuardDenyDeleteApplied(t, gitDir, sid) {
t.Fatalf(".git carries no deny-DELETE ace for the capability SID %s, so the sandboxed token can rename it and recreate it without the config and hooks carveouts", sid)
}
}
@@ -0,0 +1,94 @@
//go:build windows
package sandbox
import (
"os"
"os/exec"
"path/filepath"
"strings"
"testing"
)
// makeJunction points link at target, skipping the test when the environment
// refuses to create one. A junction needs no privilege, which is exactly why
// this attack is reachable by an ordinary workspace owner.
func makeJunction(t *testing.T, link, target string) {
t.Helper()
if out, err := exec.Command("cmd", "/c", "mklink", "/J", link, target).CombinedOutput(); err != nil {
t.Skipf("cannot create a junction here: %v: %s", err, out)
}
// Assert it actually redirects. A junction that silently did nothing would
// green this test while proving nothing.
probe := filepath.Join(link, "redirect-probe")
if err := os.WriteFile(probe, []byte("x"), 0o600); err != nil {
t.Fatalf("write through junction: %v", err)
}
if _, err := os.Stat(filepath.Join(target, "redirect-probe")); err != nil {
t.Fatalf("junction does not redirect, so this test would prove nothing: %v", err)
}
if err := os.Remove(probe); err != nil {
t.Fatalf("clean probe: %v", err)
}
}
// Elevated setup must not create anything through a reparse-point ancestor.
//
// FILE_FLAG_OPEN_REPARSE_POINT only stops the FINAL component being followed.
// materializeWindowsACLTarget used os.MkdirAll/os.OpenFile on the pathname, both
// of which resolve ancestors, so a workspace owner who turned .git into a
// junction before setup ran got objects created at a location of their choosing
// — as Administrator — and the no-follow check only rejected it afterwards, far
// too late to un-create them.
func TestMaterializeRefusesAncestorJunctionBeforeCreating(t *testing.T) {
for name, asFile := range map[string]bool{"file target": true, "directory target": false} {
t.Run(name, func(t *testing.T) {
external := t.TempDir()
workspace := t.TempDir()
gitDir := filepath.Join(workspace, ".git")
makeJunction(t, gitDir, external)
target := filepath.Join(gitDir, "hooks", "config")
_, err := materializeWindowsACLTarget(target, asFile)
if err == nil {
t.Fatalf("materialized %s through a junction ancestor instead of refusing", target)
}
if !strings.Contains(err.Error(), "reparse") {
t.Fatalf("refused for the wrong reason: %v", err)
}
// Nothing may survive on the other side of the junction. The old code
// left every intermediate directory MkdirAll had created.
leaked, lerr := os.ReadDir(external)
if lerr != nil {
t.Fatalf("read external dir: %v", lerr)
}
if len(leaked) != 0 {
names := make([]string, 0, len(leaked))
for _, entry := range leaked {
names = append(names, entry.Name())
}
t.Fatalf("created %v outside the workspace through the junction", names)
}
})
}
}
// The ordinary path still works: no reparse point anywhere, target gets made.
func TestMaterializeStillCreatesOrdinaryTargets(t *testing.T) {
root := t.TempDir()
for name, asFile := range map[string]bool{"file target": true, "directory target": false} {
t.Run(name, func(t *testing.T) {
target := filepath.Join(root, name, "nested", "deeper", "target")
if _, err := materializeWindowsACLTarget(target, asFile); err != nil {
t.Fatalf("materializeWindowsACLTarget: %v", err)
}
info, err := os.Stat(target)
if err != nil {
t.Fatalf("target was not created: %v", err)
}
if info.IsDir() == asFile {
t.Fatalf("target isDir=%v, wanted file=%v", info.IsDir(), asFile)
}
})
}
}
@@ -0,0 +1,453 @@
//go:build windows
package sandbox
import (
"errors"
"os"
"path/filepath"
"strings"
"testing"
"golang.org/x/sys/windows"
)
// swapAncestorAside moves approved out of the way and leaves a junction wearing
// its name, pointing at elsewhere. This is the whole attack in three lines, and
// it needs no privilege: junctions are creatable by any user, which is exactly
// why an unprivileged workspace owner can aim elevated setup wherever they like.
//
// Returns the path the real directory now lives at.
func swapAncestorAside(t *testing.T, approved, elsewhere string) string {
t.Helper()
moved := approved + "-moved"
if err := os.Rename(approved, moved); err != nil {
t.Skipf("cannot rename a directory with an open handle on this filesystem: %v", err)
}
makeJunction(t, approved, elsewhere)
return moved
}
// requireNothingEscaped fails when anything at all was created on the far side
// of the junction.
func requireNothingEscaped(t *testing.T, elsewhere string) {
t.Helper()
leaked, err := os.ReadDir(elsewhere)
if err != nil {
t.Fatalf("read the decoy directory: %v", err)
}
if len(leaked) == 0 {
return
}
names := make([]string, 0, len(leaked))
for _, entry := range leaked {
names = append(names, entry.Name())
}
t.Fatalf("ESCAPED: created %v outside the approved tree, as Administrator", names)
}
// THE MATERIALIZATION RACE, ON THE PRODUCTION CALL PATH.
//
// The existing junction test plants its junction before the walk even starts, so
// the very first check sees it and refuses. That proves the easy half. The half
// the reviewer filed is the swap that happens AFTER a component has been
// verified and BEFORE it is used, and no test reached it: a race nobody can
// trigger on demand is not a regression test, so makeWindowsACLDirChainNoFollow
// carries a seam that fires at exactly that instant.
//
// The control arm matters as much as the fixed one. It performs the identical
// swap and then does what this code used to do, creating by pathname, and
// asserts that the object DOES escape. Without it, the fixed arm passing proves
// only that some code ran, not that the hole it closes was ever open.
func TestMaterializeSurvivesAnAncestorSwappedMidWalk(t *testing.T) {
t.Run("control: creating by pathname escapes", func(t *testing.T) {
root := t.TempDir()
approved := filepath.Join(root, "ws")
elsewhere := filepath.Join(root, "OUTSIDE")
for _, dir := range []string{approved, elsewhere} {
if err := os.Mkdir(dir, 0o700); err != nil {
t.Fatalf("seed %s: %v", dir, err)
}
}
// Verified, exactly as the walk verifies its anchor.
if err := verifyWindowsACLPathComponentNotRedirected(approved); err != nil {
t.Fatalf("anchor did not verify before the swap: %v", err)
}
moved := swapAncestorAside(t, approved, elsewhere)
// The old create: a pathname, re-resolved by the kernel right now.
if err := os.MkdirAll(filepath.Join(approved, "a", "b"), 0o700); err != nil {
t.Fatalf("pathname create: %v", err)
}
if _, err := os.Stat(filepath.Join(elsewhere, "a", "b")); err != nil {
t.Fatalf("the control arm did not reproduce the escape, so the fixed arm below proves nothing: %v", err)
}
if _, err := os.Stat(filepath.Join(moved, "a", "b")); err == nil {
t.Error("the control arm created inside the verified directory, which is not the behaviour being contrasted")
}
})
t.Run("fixed: creating through the pinned handle stays put", func(t *testing.T) {
root := t.TempDir()
approved := filepath.Join(root, "ws")
elsewhere := filepath.Join(root, "OUTSIDE")
for _, dir := range []string{approved, elsewhere} {
if err := os.Mkdir(dir, 0o700); err != nil {
t.Fatalf("seed %s: %v", dir, err)
}
}
var moved string
swapped := false
windowsACLMaterializeSwapHook = func(anchor string) {
if swapped {
return
}
swapped = true
if anchor != approved {
t.Errorf("anchored on %q, want the deepest existing ancestor %q", anchor, approved)
}
moved = swapAncestorAside(t, approved, elsewhere)
}
t.Cleanup(func() { windowsACLMaterializeSwapHook = nil })
created, err := materializeWindowsACLTarget(filepath.Join(approved, "a", "b"), false)
if err != nil {
t.Fatalf("materializeWindowsACLTarget: %v", err)
}
if !swapped {
t.Fatal("the seam never fired, so the swap never happened and this test proved nothing")
}
requireNothingEscaped(t, elsewhere)
if _, err := os.Stat(filepath.Join(moved, "a", "b")); err != nil {
t.Errorf("the target did not land in the directory that was verified: %v", err)
}
// And the record must describe what to unwind, in components rather than
// paths, shallowest first.
if len(created.Chain) != 2 || created.Chain[0].Name != "a" || created.Chain[1].Name != "b" {
t.Fatalf("created chain = %#v, want [a b] shallow to deep", created.Chain)
}
for _, step := range created.Chain {
if !step.Made {
t.Errorf("component %q was not recorded as created, so rollback would leave it behind", step.Name)
}
}
})
}
// The FILE target has the same race, and it is the one that matters most:
// .git/config is materialized as a file on every stock setup, and it is the file
// whose credential.helper is worth stealing.
func TestMaterializeFileSurvivesAnAncestorSwappedMidWalk(t *testing.T) {
root := t.TempDir()
approved := filepath.Join(root, "ws")
elsewhere := filepath.Join(root, "OUTSIDE")
for _, dir := range []string{approved, elsewhere} {
if err := os.Mkdir(dir, 0o700); err != nil {
t.Fatalf("seed %s: %v", dir, err)
}
}
var moved string
swapped := false
windowsACLMaterializeSwapHook = func(string) {
if swapped {
return
}
swapped = true
moved = swapAncestorAside(t, approved, elsewhere)
}
t.Cleanup(func() { windowsACLMaterializeSwapHook = nil })
created, err := materializeWindowsACLTarget(filepath.Join(approved, ".git", "config"), true)
if err != nil {
t.Fatalf("materializeWindowsACLTarget: %v", err)
}
if !swapped {
t.Fatal("the seam never fired, so this test proved nothing")
}
requireNothingEscaped(t, elsewhere)
landed := filepath.Join(moved, ".git", "config")
info, err := os.Stat(landed)
if err != nil {
t.Fatalf("the file did not land in the directory that was verified: %v", err)
}
if info.IsDir() {
t.Error("materialized .git/config as a directory, which breaks git init")
}
if !created.FileMade || created.File != "config" {
t.Errorf("file record = %q made=%v, want config/true", created.File, created.FileMade)
}
}
// THE ROLLBACK RACE. The ancestor is swapped AFTER the target was created, which
// is the window the teardown path lives in: minutes or hours, not microseconds.
//
// The bystander is the point. If the unwind resolves by pathname it walks into
// the decoy and deletes what it finds there, recursively and elevated. Its
// survival is the only thing that proves the unwind did not.
func TestRollbackDoesNotFollowAnAncestorSwappedAfterCreation(t *testing.T) {
root := t.TempDir()
approved := filepath.Join(root, "ws")
elsewhere := filepath.Join(root, "OUTSIDE")
for _, dir := range []string{approved, elsewhere} {
if err := os.Mkdir(dir, 0o700); err != nil {
t.Fatalf("seed %s: %v", dir, err)
}
}
created, err := materializeWindowsACLTarget(filepath.Join(approved, "a", "b"), false)
if err != nil {
t.Fatalf("materializeWindowsACLTarget: %v", err)
}
// A bystander tree under the decoy, shaped exactly like what we created, so a
// pathname unwind would find something to destroy at every level.
bystander := filepath.Join(elsewhere, "a", "b")
if err := os.MkdirAll(bystander, 0o700); err != nil {
t.Fatalf("seed bystander: %v", err)
}
witness := filepath.Join(bystander, "irreplaceable.txt")
if err := os.WriteFile(witness, []byte("not yours to delete"), 0o600); err != nil {
t.Fatalf("seed witness: %v", err)
}
moved := swapAncestorAside(t, approved, elsewhere)
// The anchor pathname now names the decoy, and the decoy is a junction, so
// the unwind must refuse rather than proceed. Either way it must not delete.
_, err = rollbackWindowsACLMaterialization(created)
if _, statErr := os.Stat(witness); statErr != nil {
t.Fatalf("DESTRUCTIVE: rollback followed the junction and deleted a tree outside the approved directory: %v", statErr)
}
if _, statErr := os.Stat(bystander); statErr != nil {
t.Fatalf("DESTRUCTIVE: rollback removed the bystander directory outside the approved directory: %v", statErr)
}
if err == nil {
t.Error("rollback reported success while unwinding through a swapped ancestor; it must say it could not")
}
// Residue inside the real tree is the accepted price: leaving it is strictly
// better than a recursive delete through a path someone else controls.
if _, statErr := os.Stat(filepath.Join(moved, "a", "b")); statErr != nil {
t.Logf("note: the real tree was also unwound (%v); leaving it would be acceptable too", statErr)
}
}
// A real directory wearing the anchor's name is a swap with NO reparse point
// anywhere, so every no-follow check in this package passes it. Only the file
// identity notices.
func TestRollbackRefusesAnAnchorReplacedByARealDirectory(t *testing.T) {
root := t.TempDir()
approved := filepath.Join(root, "ws")
if err := os.Mkdir(approved, 0o700); err != nil {
t.Fatalf("seed: %v", err)
}
created, err := materializeWindowsACLTarget(filepath.Join(approved, "a"), false)
if err != nil {
t.Fatalf("materializeWindowsACLTarget: %v", err)
}
if err := os.Rename(approved, approved+"-moved"); err != nil {
t.Skipf("cannot rename here: %v", err)
}
// An ordinary directory. Nothing is a link; nothing is a reparse point.
if err := os.Mkdir(approved, 0o700); err != nil {
t.Fatalf("plant the replacement: %v", err)
}
decoy := filepath.Join(approved, "a")
if err := os.Mkdir(decoy, 0o700); err != nil {
t.Fatalf("plant the decoy child: %v", err)
}
_, err = rollbackWindowsACLMaterialization(created)
if err == nil {
t.Error("rollback accepted a different directory wearing the anchor's name")
} else if !strings.Contains(err.Error(), "no longer the directory") {
t.Errorf("refused for the wrong reason: %v", err)
}
if _, statErr := os.Stat(decoy); statErr != nil {
t.Errorf("rollback deleted a directory it never created: %v", statErr)
}
}
// Rollback removes ONLY what this run created. A pre-existing ancestor is walked
// through and left alone.
func TestRollbackLeavesDirectoriesItDidNotCreate(t *testing.T) {
root := t.TempDir()
existing := filepath.Join(root, "ws", "already-here")
if err := os.MkdirAll(existing, 0o700); err != nil {
t.Fatalf("seed: %v", err)
}
target := filepath.Join(existing, "made", "deeper")
created, err := materializeWindowsACLTarget(target, false)
if err != nil {
t.Fatalf("materializeWindowsACLTarget: %v", err)
}
if created.AnchorPath != existing {
t.Fatalf("anchor = %q, want the deepest pre-existing directory %q", created.AnchorPath, existing)
}
if _, err := rollbackWindowsACLMaterialization(created); err != nil {
t.Fatalf("rollbackWindowsACLMaterialization: %v", err)
}
if _, err := os.Stat(filepath.Join(existing, "made")); !errors.Is(err, os.ErrNotExist) {
t.Errorf("created directory survived rollback: stat err = %v", err)
}
if _, err := os.Stat(existing); err != nil {
t.Errorf("rollback removed a directory that already existed: %v", err)
}
}
// The whole apply path, through the closure callers actually hold, rather than
// through rollbackWindowsACLSnapshots directly. Every other rollback test in
// this package calls the unwind by hand, which cannot catch applyWindowsACLPlan
// failing to carry the created record into the snapshots it hands over.
func TestApplyWindowsACLPlanClosureRemovesWhatItMaterialized(t *testing.T) {
root := t.TempDir()
directoryTarget := filepath.Join(root, "ws", "hooks")
fileTarget := filepath.Join(root, "ws", "config")
plan := WindowsACLPlan{Entries: []WindowsACLEntry{
{Action: WindowsACLDenyWrite, Path: directoryTarget, Capability: "S-1-1-0", Materialize: true},
{Action: WindowsACLDenyWrite, Path: fileTarget, Capability: "S-1-1-0", Materialize: true, MaterializeFile: true},
}}
rollback, err := applyWindowsACLPlan(plan)
if err != nil {
t.Fatalf("applyWindowsACLPlan: %v", err)
}
for _, path := range []string{directoryTarget, fileTarget} {
if _, err := os.Stat(path); err != nil {
t.Fatalf("%s was not materialized: %v", path, err)
}
}
if err := rollback(); err != nil {
t.Fatalf("rollback closure: %v", err)
}
for _, path := range []string{directoryTarget, fileTarget} {
if _, err := os.Stat(path); !errors.Is(err, os.ErrNotExist) {
t.Errorf("%s survived the rollback closure: stat err = %v", path, err)
}
}
// The shared prefix both targets needed must go too, and it is created by
// whichever group runs first rather than being owned by both.
if _, err := os.Stat(filepath.Join(root, "ws")); !errors.Is(err, os.ErrNotExist) {
t.Errorf("the shared parent survived: stat err = %v", err)
}
}
// A rollback that cannot remove something must SAY so. This is the regression
// guard for the trap a naive handle-relative port walks straight into:
// FILE_DELETE_ON_CLOSE reports success on a non-empty directory and leaves it
// there, which turns a loud failure into a silent lie. The directory being
// populated is not adversarial; .git/hooks fills up the moment git runs.
func TestRollbackReportsWhatItCouldNotRemove(t *testing.T) {
root := t.TempDir()
target := filepath.Join(root, "ws", "hooks")
created, err := materializeWindowsACLTarget(target, false)
if err != nil {
t.Fatalf("materializeWindowsACLTarget: %v", err)
}
if err := os.WriteFile(filepath.Join(target, "pre-commit"), []byte("#!/bin/sh\n"), 0o600); err != nil {
t.Fatalf("populate: %v", err)
}
_, err = rollbackWindowsACLMaterialization(created)
if err == nil {
t.Fatal("rollback reported success on a directory it could not empty, so callers cannot tell teardown failed")
}
if !strings.Contains(strings.ToLower(err.Error()), "hooks") {
t.Errorf("the error does not name what was left behind: %v", err)
}
// Left in place deliberately. Removing it would mean recursing, and recursion
// through a path the workspace owner controls is the thing being avoided.
if _, statErr := os.Stat(target); statErr != nil {
t.Errorf("rollback recursed into a populated directory instead of reporting it: %v", statErr)
}
}
// The primitives take a single component and the walk relies on that. A joined
// name is resolved the ordinary way by the kernel, so an intermediate junction
// inside it is followed and the object lands outside the anchor: the pinned
// parent buys nothing if the name itself walks.
func TestChildOperationsRefuseNamesThatAreNotSingleComponents(t *testing.T) {
root := t.TempDir()
parent, err := openWindowsACLDirectoryNoFollow(root)
if err != nil {
t.Fatalf("open root: %v", err)
}
defer func() { _ = windows.CloseHandle(parent) }()
for _, name := range []string{`sub\child`, "sub/child", "..", ".", "", `C:\absolute`, "stream:name"} {
t.Run("create dir "+name, func(t *testing.T) {
handle, _, err := createWindowsACLChildDirectory(parent, name)
if err == nil {
_ = windows.CloseHandle(handle)
t.Fatalf("accepted %q, which the kernel would resolve through intermediate directories", name)
}
})
t.Run("delete dir "+name, func(t *testing.T) {
if err := deleteWindowsACLChildDirectory(parent, name); err == nil {
t.Fatalf("accepted %q for deletion", name)
}
})
t.Run("create file "+name, func(t *testing.T) {
if _, _, err := createWindowsACLChildFile(parent, name); err == nil {
t.Fatalf("accepted %q for file creation", name)
}
})
}
}
// A junction sitting where a chain component should be must be refused when it
// is OPENED, not merely when it is created. FILE_OPEN_REPARSE_POINT hands back a
// handle to the junction itself, and using that as the next parent puts every
// deeper create on the far side of it.
func TestChildOperationsRefuseAnExistingJunction(t *testing.T) {
root := t.TempDir()
elsewhere := t.TempDir()
makeJunction(t, filepath.Join(root, "hop"), elsewhere)
parent, err := openWindowsACLDirectoryNoFollow(root)
if err != nil {
t.Fatalf("open root: %v", err)
}
defer func() { _ = windows.CloseHandle(parent) }()
handle, _, err := createWindowsACLChildDirectory(parent, "hop")
if err == nil {
_ = windows.CloseHandle(handle)
t.Error("createWindowsACLChildDirectory returned a junction as the next parent in the walk")
}
opened, err := openWindowsACLChildDirectory(parent, "hop")
if err == nil {
_ = windows.CloseHandle(opened)
t.Error("openWindowsACLChildDirectory returned a junction to descend through")
}
}
// Rollback descends; it must never create. If a component was removed by
// something else in the meantime, re-making it and then deleting it would remove
// a directory the sandbox never made.
func TestRollbackDescentNeverCreatesAMissingComponent(t *testing.T) {
root := t.TempDir()
parent, err := openWindowsACLDirectoryNoFollow(root)
if err != nil {
t.Fatalf("open root: %v", err)
}
defer func() { _ = windows.CloseHandle(parent) }()
handle, err := openWindowsACLChildDirectory(parent, "never-existed")
if err == nil {
_ = windows.CloseHandle(handle)
t.Fatal("the descent open created a directory that did not exist")
}
if !isWindowsNotExist(err) {
t.Errorf("a missing component reported %v, which rollback cannot distinguish from a real failure", err)
}
if _, statErr := os.Stat(filepath.Join(root, "never-existed")); statErr == nil {
t.Error("a directory appeared on disk from an open that should never create")
}
}
@@ -0,0 +1,128 @@
//go:build windows
package sandbox
import (
"os"
"path/filepath"
"strings"
"testing"
"unsafe"
"golang.org/x/sys/windows"
)
// racedLeafDenyMask reads the DENY mask a path carries for sid.
func racedLeafDenyMask(t *testing.T, path string, sid string) uint32 {
t.Helper()
handle, _, err := openWindowsACLTarget(path)
if err != nil {
t.Fatalf("open %s: %v", path, err)
}
defer func() { _ = windows.CloseHandle(handle) }()
descriptor, err := windows.GetSecurityInfo(handle, windows.SE_FILE_OBJECT, windows.DACL_SECURITY_INFORMATION)
if err != nil {
t.Fatalf("read the DACL of %s: %v", path, err)
}
dacl, _, err := descriptor.DACL()
if err != nil || dacl == nil {
t.Fatalf("read the DACL of %s: %v", path, err)
}
wanted, err := windows.StringToSid(sid)
if err != nil {
t.Fatalf("parse %q: %v", sid, err)
}
var mask uint32
for index := uint32(0); index < uint32(dacl.AceCount); index++ {
var ace *windows.ACCESS_ALLOWED_ACE
if windows.GetAce(dacl, index, &ace) != nil {
continue
}
if ace.Header.AceType != windows.ACCESS_DENIED_ACE_TYPE {
continue
}
if !(*windows.SID)(unsafe.Pointer(&ace.SidStart)).Equals(wanted) {
continue
}
mask |= uint32(ace.Mask)
}
return mask
}
// OWNING THE PARENT IS NOT OWNING THE TARGET.
//
// rollbackWindowsACLSnapshots branched on createdAnything(), an OR across the
// whole materialization record. When this run creates the parent chain and a
// racer wins the leaf, that is true while the ACL-bearing file belongs to
// somebody else: Chain carries Made:true and FileMade is false.
//
// The rollback then could not remove the parent, because it is not empty, and
// the unconditional skip meant the existing no-follow, identity-validated
// restore never ran either. A file that existed before setup started was left
// wearing an aborted setup's DACL.
//
// Driven through applyWindowsACLPlan with the leaf created inside the swap hook,
// which fires after the anchor is pinned and before anything is made, so the
// race is deterministic rather than hoped for.
func TestAbortRestoresALeafARacerCreated(t *testing.T) {
workspace := t.TempDir()
parent := filepath.Join(workspace, "materialized")
leaf := filepath.Join(parent, "config")
previous := windowsACLRacedLeafHook
t.Cleanup(func() { windowsACLRacedLeafHook = previous })
raced := false
windowsACLRacedLeafHook = func(string) {
// The chain above already belongs to this run; the racer wins only the
// file. That mixed ownership is the whole case.
if raced {
return
}
raced = true
_ = os.WriteFile(leaf, []byte("pre-existing content"), 0o600)
}
sid := testPrincipalSID
plan := WindowsACLPlan{Entries: []WindowsACLEntry{{
Action: WindowsACLDenyWrite,
Path: leaf,
Capability: sid,
Materialize: true,
MaterializeFile: true,
}}}
rollback, err := applyWindowsACLPlan(plan)
if err != nil {
t.Skipf("cannot apply an ACL plan here: %v", err)
}
if !raced {
t.Fatal("SETUP INVALID: the leaf hook never fired, so the mixed-ownership case was not reproduced")
}
// SETUP: the racer really won, and the apply really landed on its file.
if _, statErr := os.Stat(leaf); statErr != nil {
t.Skipf("SETUP: the racer's leaf is not present, so this is not the mixed-ownership case: %v", statErr)
}
applied := racedLeafDenyMask(t, leaf, sid)
if applied == 0 {
t.Skipf("SETUP: the apply did not put a deny ACE on the raced leaf, so there is nothing to restore")
}
// The setup aborts.
if rollback != nil {
_ = rollback()
}
// The racer's file must not be left wearing this run's ACL.
if got := racedLeafDenyMask(t, leaf, sid); got != 0 {
t.Fatalf("a file the racer created still carries the aborted setup's deny ACE (mask=%#x); rollback skipped its restore because an ancestor happened to be ours", got)
}
// And it must still exist: a raced leaf is never ours to delete.
body, readErr := os.ReadFile(leaf)
if readErr != nil {
t.Fatalf("rollback removed a file it did not create: %v", readErr)
}
if !strings.Contains(string(body), "pre-existing") {
t.Fatalf("the raced leaf's contents changed: %q", body)
}
}
@@ -0,0 +1,496 @@
//go:build windows
package sandbox
import (
"errors"
"fmt"
"os"
"unsafe"
"golang.org/x/sys/windows"
)
// Handle-relative directory operations.
//
// WHY THESE EXIST. Every pathname-based call re-resolves the whole path inside
// the kernel at the moment it runs. So verifying a component and then creating
// through it are two separate resolutions of the same string, and a workspace
// owner can swap an ancestor for a junction in the gap between them: setup
// verifies, the attacker swaps, setup creates, and the object lands outside the
// approved tree. Checking again afterwards is too late, because the thing has
// already been created somewhere it should not be.
//
// A HANDLE pins the object rather than the name. Once a directory is open, that
// handle keeps referring to the same directory however the path is later
// rearranged, so creating a child relative to it cannot be redirected. os.Mkdir,
// os.OpenFile and os.RemoveAll are pathname-based by construction with no
// relative form on Windows, which is why this drops to NtCreateFile with
// OBJECT_ATTRIBUTES.RootDirectory.
// IO_STATUS_BLOCK.Information values for a create/open, named because "2 means
// it was created" is not something a reader should have to look up.
const (
windowsFileOpened uintptr = 1
windowsFileCreated uintptr = 2
)
// windowsACLDirectoryShare is the share mode every open here uses. A sandbox
// tree is live, so refusing to share would fail on any directory something else
// happens to have open: a denial of service on ourselves rather than a security
// property.
const windowsACLDirectoryShare = windows.FILE_SHARE_READ | windows.FILE_SHARE_WRITE | windows.FILE_SHARE_DELETE
// windowsFileIdentity is the kernel's own answer to "is this the same object",
// independent of what it is currently called.
//
// It exists because rollback cannot hold the anchor handle open for the whole
// sandbox lifetime (see rollbackWindowsACLSnapshots), so it has to re-open the
// anchor by pathname, and a pathname can be made to name a different object.
// Crucially that substitution needs NO reparse point: rename the real directory
// aside and create an ordinary directory wearing its name, and every no-follow
// check still passes because nothing anywhere is a link. Comparing the volume
// and file index catches it, because those identify the object the kernel
// actually opened.
type windowsFileIdentity struct {
Volume uint32
IndexHigh uint32
IndexLow uint32
}
func (identity windowsFileIdentity) empty() bool {
return identity == windowsFileIdentity{}
}
// windowsIdentityOfHandle reads the identity of an already-open object.
func windowsIdentityOfHandle(handle windows.Handle) (windowsFileIdentity, error) {
var info windows.ByHandleFileInformation
if err := windows.GetFileInformationByHandle(handle, &info); err != nil {
return windowsFileIdentity{}, fmt.Errorf("read windows file identity: %w", err)
}
return windowsFileIdentity{
Volume: info.VolumeSerialNumber,
IndexHigh: info.FileIndexHigh,
IndexLow: info.FileIndexLow,
}, nil
}
// openWindowsACLDirectoryNoFollow opens an existing directory by pathname,
// refusing to traverse or land on a reparse point.
//
// This is the ANCHOR for a handle-relative walk: the one pathname resolution
// that has to happen, with everything below it relative to the handle it
// returns. FILE_FLAG_OPEN_REPARSE_POINT stops the final component being
// followed, and verifyWindowsACLTargetNotRedirected then confirms no ancestor
// redirected either, because GetFinalPathNameByHandle answers for the whole
// resolved path.
func openWindowsACLDirectoryNoFollow(path string) (windows.Handle, error) {
utf16Path, err := windows.UTF16PtrFromString(path)
if err != nil {
return 0, fmt.Errorf("encode windows ACL directory %s: %w", path, err)
}
handle, err := windows.CreateFile(
utf16Path,
windows.FILE_LIST_DIRECTORY|windows.FILE_READ_ATTRIBUTES|windows.SYNCHRONIZE,
windowsACLDirectoryShare,
nil,
windows.OPEN_EXISTING,
windows.FILE_FLAG_BACKUP_SEMANTICS|windows.FILE_FLAG_OPEN_REPARSE_POINT,
0,
)
if err != nil {
// Errno.Is maps the not-found codes to os.ErrNotExist, so a caller
// walking up to find the deepest existing ancestor keeps working.
return 0, fmt.Errorf("open windows ACL directory %s: %w", path, err)
}
if err := verifyWindowsACLHandleIsCleanDirectory(handle, path); err != nil {
_ = windows.CloseHandle(handle)
return 0, err
}
return handle, nil
}
// openWindowsACLDirectoryNoFollowWithIdentity is the anchor open plus the
// identity a later rollback needs in order to prove it re-opened the same
// object.
func openWindowsACLDirectoryNoFollowWithIdentity(path string) (windows.Handle, windowsFileIdentity, error) {
handle, err := openWindowsACLDirectoryNoFollow(path)
if err != nil {
return 0, windowsFileIdentity{}, err
}
identity, err := windowsIdentityOfHandle(handle)
if err != nil {
_ = windows.CloseHandle(handle)
return 0, windowsFileIdentity{}, fmt.Errorf("identify windows ACL directory %s: %w", path, err)
}
return handle, identity, nil
}
// reopenWindowsACLDirectoryAsIdentity re-opens an anchor by pathname and refuses
// it unless the kernel says it is the object that was opened before.
//
// Used only by rollback. See windowsFileIdentity for why the pathname alone is
// not enough, and rollbackWindowsACLSnapshots for why a handle cannot simply be
// held instead.
func reopenWindowsACLDirectoryAsIdentity(path string, want windowsFileIdentity) (windows.Handle, error) {
handle, err := openWindowsACLDirectoryNoFollow(path)
if err != nil {
return 0, err
}
if want.empty() {
return handle, nil
}
got, err := windowsIdentityOfHandle(handle)
if err != nil {
_ = windows.CloseHandle(handle)
return 0, fmt.Errorf("identify windows ACL directory %s: %w", path, err)
}
if got != want {
_ = windows.CloseHandle(handle)
return 0, fmt.Errorf("refusing to unwind under %s: it is no longer the directory setup created into, so something replaced it since (possible path swap during elevated setup)", path)
}
return handle, nil
}
// createWindowsACLChildDirectory creates one directory directly beneath parent,
// or opens it when it already exists, and reports which happened.
//
// name must be a single component; see validateWindowsACLComponent for why that
// is enforced rather than assumed. The kernel resolves it relative to the parent
// HANDLE, so nothing above it is consulted and nothing above it can be swapped
// underneath us.
//
// created is true only when this call made the directory, which the rollback
// needs: removing one that already existed would delete a user's data over a
// failure that had nothing to do with it.
func createWindowsACLChildDirectory(parent windows.Handle, name string) (handle windows.Handle, created bool, err error) {
if err := validateWindowsACLComponent(name); err != nil {
return 0, false, err
}
objectName, err := windows.NewNTUnicodeString(name)
if err != nil {
return 0, false, fmt.Errorf("encode windows ACL directory component %s: %w", name, err)
}
attributes := windows.OBJECT_ATTRIBUTES{
RootDirectory: parent,
ObjectName: objectName,
Attributes: windows.OBJ_CASE_INSENSITIVE,
}
attributes.Length = uint32(unsafe.Sizeof(attributes))
var status windows.IO_STATUS_BLOCK
if err := windows.NtCreateFile(
&handle,
windows.FILE_LIST_DIRECTORY|windows.FILE_READ_ATTRIBUTES|windows.SYNCHRONIZE|windows.DELETE,
&attributes,
&status,
nil,
windows.FILE_ATTRIBUTE_DIRECTORY,
windowsACLDirectoryShare,
windows.FILE_OPEN_IF,
windows.FILE_DIRECTORY_FILE|windows.FILE_OPEN_REPARSE_POINT|windows.FILE_SYNCHRONOUS_IO_NONALERT,
0,
0,
); err != nil {
return 0, false, fmt.Errorf("create windows ACL directory component %s: %w", name, err)
}
// FILE_OPEN_IF means an EXISTING child is opened rather than created, and
// FILE_OPEN_REPARSE_POINT means a junction is opened AS the junction. Without
// this check that junction becomes the parent of the next level and every
// create beneath it lands wherever it points, which is the mid-walk swap this
// whole file exists to stop.
if err := rejectWindowsACLReparseHandle(handle, name); err != nil {
_ = windows.CloseHandle(handle)
return 0, false, err
}
return handle, status.Information == windowsFileCreated, nil
}
// openWindowsACLChildDirectory opens an EXISTING directory beneath parent and
// never creates one.
//
// Rollback walks back down the chain it created, and it must not conjure a
// component that has since been removed: FILE_OPEN_IF would recreate it, and
// then the unwind would delete a directory setup never made. FILE_OPEN is the
// whole difference from createWindowsACLChildDirectory.
func openWindowsACLChildDirectory(parent windows.Handle, name string) (handle windows.Handle, err error) {
if err := validateWindowsACLComponent(name); err != nil {
return 0, err
}
objectName, err := windows.NewNTUnicodeString(name)
if err != nil {
return 0, fmt.Errorf("encode windows ACL directory component %s: %w", name, err)
}
attributes := windows.OBJECT_ATTRIBUTES{
RootDirectory: parent,
ObjectName: objectName,
Attributes: windows.OBJ_CASE_INSENSITIVE,
}
attributes.Length = uint32(unsafe.Sizeof(attributes))
// Ask for the least that still allows passing through and checking the
// reparse attribute. This runs during rollback, on directories whose ACEs
// have already been applied, so every extra right is another way for the
// unwind to be refused by the very ACL it is unwinding. Notably absent:
// SYNCHRONIZE, and with it FILE_SYNCHRONOUS_IO_NONALERT, since nothing is
// read or written through this handle.
var status windows.IO_STATUS_BLOCK
if err := windows.NtCreateFile(
&handle,
windows.FILE_TRAVERSE|windows.FILE_READ_ATTRIBUTES,
&attributes,
&status,
nil,
windows.FILE_ATTRIBUTE_DIRECTORY,
windowsACLDirectoryShare,
windows.FILE_OPEN,
windows.FILE_DIRECTORY_FILE|windows.FILE_OPEN_REPARSE_POINT,
0,
0,
); err != nil {
return 0, fmt.Errorf("open windows ACL directory component %s: %w", name, err)
}
if err := rejectWindowsACLReparseHandle(handle, name); err != nil {
_ = windows.CloseHandle(handle)
return 0, err
}
return handle, nil
}
// createWindowsACLChildFile creates an empty file directly beneath parent, or
// opens it when it already exists, and reports which happened.
//
// The counterpart to createWindowsACLChildDirectory for the one materialized
// target that must be a FILE: .git/config, where creating a directory instead
// would break `git init` outright rather than merely mis-ACL it.
//
// FILE_OPEN_IF rather than FILE_CREATE deliberately. The pathname version this
// replaces used O_CREATE|O_EXCL and then tolerated os.ErrExist, so a racing
// creator winning was fine. FILE_CREATE's collision status is
// STATUS_OBJECT_NAME_COLLISION, which errors.Is(err, os.ErrExist) does NOT
// match, so porting it literally would have turned that tolerated race into a
// hard failure. FILE_OPEN_IF keeps the old behaviour and reports the truth in
// created, which rollback needs so it never deletes a file it did not make.
func createWindowsACLChildFile(parent windows.Handle, name string) (created bool, identity windowsFileIdentity, err error) {
if err := validateWindowsACLComponent(name); err != nil {
return false, windowsFileIdentity{}, err
}
objectName, err := windows.NewNTUnicodeString(name)
if err != nil {
return false, windowsFileIdentity{}, fmt.Errorf("encode windows ACL file component %s: %w", name, err)
}
attributes := windows.OBJECT_ATTRIBUTES{
RootDirectory: parent,
ObjectName: objectName,
Attributes: windows.OBJ_CASE_INSENSITIVE,
}
attributes.Length = uint32(unsafe.Sizeof(attributes))
var handle windows.Handle
var status windows.IO_STATUS_BLOCK
if err := windows.NtCreateFile(
&handle,
windows.FILE_READ_ATTRIBUTES|windows.SYNCHRONIZE,
&attributes,
&status,
nil,
windows.FILE_ATTRIBUTE_NORMAL,
windowsACLDirectoryShare,
windows.FILE_OPEN_IF,
windows.FILE_NON_DIRECTORY_FILE|windows.FILE_OPEN_REPARSE_POINT|windows.FILE_SYNCHRONOUS_IO_NONALERT,
0,
0,
); err != nil {
return false, windowsFileIdentity{}, fmt.Errorf("create windows ACL file component %s: %w", name, err)
}
if err := rejectWindowsACLReparseHandle(handle, name); err != nil {
_ = windows.CloseHandle(handle)
return false, windowsFileIdentity{}, err
}
createdNow := status.Information == windowsFileCreated
identity, err = windowsIdentityOfHandle(handle)
if err != nil {
_ = windows.CloseHandle(handle)
return createdNow, windowsFileIdentity{}, fmt.Errorf("identify windows ACL file component %s: %w", name, err)
}
if err := windows.CloseHandle(handle); err != nil {
return createdNow, identity, fmt.Errorf("close windows ACL file component %s: %w", name, err)
}
return createdNow, identity, nil
}
// deleteWindowsACLChildDirectory removes one directory directly beneath parent.
//
// The counterpart to the create above, and the reason rollback cannot use
// os.RemoveAll: that takes a pathname, so an ancestor swapped to a junction
// AFTER the object was created sends the recursive delete somewhere else and
// takes unrelated trees with it. Resolving relative to the parent handle makes
// that impossible.
//
// A missing child is not an error: rollback runs on failure paths where the
// object may never have been created.
func deleteWindowsACLChildDirectory(parent windows.Handle, name string) error {
return deleteWindowsACLChild(parent, name, true, windowsFileIdentity{})
}
// deleteWindowsACLChildDirectoryAs and deleteWindowsACLChildFileAs remove the
// child only if the object at name is still want. The identity is read from
// the very handle the delete disposition is set on, so a replacement renamed
// in between a check and the unlink cannot be the thing removed.
func deleteWindowsACLChildDirectoryAs(parent windows.Handle, name string, want windowsFileIdentity) error {
return deleteWindowsACLChild(parent, name, true, want)
}
func deleteWindowsACLChildFileAs(parent windows.Handle, name string, want windowsFileIdentity) error {
return deleteWindowsACLChild(parent, name, false, want)
}
// deleteWindowsACLChildFile removes one file directly beneath parent, for the
// materialized .git/config carveout. Rollback picks between this and the
// directory form from the shape recorded at materialization time rather than by
// stat-ing the pathname, because a stat is another pathname resolution and this
// whole file exists to avoid those.
func deleteWindowsACLChildFile(parent windows.Handle, name string) error {
return deleteWindowsACLChild(parent, name, false, windowsFileIdentity{})
}
// deleteWindowsACLChild opens one child relative to parent and deletes it by
// SETTING ITS DISPOSITION, not with FILE_DELETE_ON_CLOSE.
//
// That distinction is the whole point, and it was measured rather than assumed.
// FILE_DELETE_ON_CLOSE defers the removal to cleanup, where a non-empty
// directory makes it fail with nothing to report it to: NtCreateFile returns
// success, CloseHandle returns success, and the directory is still there. A
// rollback built on it would report success while leaving materialized state on
// disk, which is strictly worse than the os.RemoveAll it replaces, because
// os.RemoveAll at least removed it.
//
// NtSetInformationFile answers synchronously and to the caller, so a non-empty
// directory comes back as STATUS_DIRECTORY_NOT_EMPTY. Leaving residue is
// acceptable, since the alternative is a recursive delete through a pathname an
// attacker may control; lying about having removed it is not.
//
// FILE_DIRECTORY_FILE / FILE_NON_DIRECTORY_FILE also make the open refuse an
// object of the wrong shape rather than deleting it.
func deleteWindowsACLChild(parent windows.Handle, name string, directory bool, want windowsFileIdentity) error {
if err := validateWindowsACLComponent(name); err != nil {
return err
}
objectName, err := windows.NewNTUnicodeString(name)
if err != nil {
return fmt.Errorf("encode windows ACL component %s: %w", name, err)
}
attributes := windows.OBJECT_ATTRIBUTES{
RootDirectory: parent,
ObjectName: objectName,
Attributes: windows.OBJ_CASE_INSENSITIVE,
}
attributes.Length = uint32(unsafe.Sizeof(attributes))
shapeOption := uint32(windows.FILE_NON_DIRECTORY_FILE)
shapeAttribute := uint32(windows.FILE_ATTRIBUTE_NORMAL)
if directory {
shapeOption = windows.FILE_DIRECTORY_FILE
shapeAttribute = windows.FILE_ATTRIBUTE_DIRECTORY
}
// DELETE alone. Asking for SYNCHRONIZE as well would make this fail on any
// object already carrying a deny-read ACE, because FILE_GENERIC_READ and
// FILE_GENERIC_EXECUTE both include SYNCHRONIZE, and rollback exists
// precisely to undo objects that have just been ACL'd. Nothing is read or
// written through this handle, so synchronous IO is not needed either.
var handle windows.Handle
var status windows.IO_STATUS_BLOCK
if err := windows.NtCreateFile(
&handle,
windows.DELETE|windows.FILE_READ_ATTRIBUTES,
&attributes,
&status,
nil,
shapeAttribute,
windowsACLDirectoryShare,
windows.FILE_OPEN,
shapeOption|windows.FILE_OPEN_REPARSE_POINT,
0,
0,
); err != nil {
if isWindowsNotExist(err) {
return nil
}
return fmt.Errorf("open windows ACL component %s for delete: %w", name, err)
}
defer func() { _ = windows.CloseHandle(handle) }()
if !want.empty() {
got, err := windowsIdentityOfHandle(handle)
if err != nil {
return fmt.Errorf("identify windows ACL component %s before delete: %w", name, err)
}
if got != want {
return fmt.Errorf("refusing to remove %s: it is no longer the object setup created", name)
}
}
// One BOOLEAN: FILE_DISPOSITION_INFORMATION.DeleteFile = TRUE.
disposition := byte(1)
var setStatus windows.IO_STATUS_BLOCK
if err := windows.NtSetInformationFile(
handle,
&setStatus,
&disposition,
uint32(unsafe.Sizeof(disposition)),
windows.FileDispositionInformation,
); err != nil {
return fmt.Errorf("delete windows ACL component %s: %w", name, err)
}
return nil
}
// rejectWindowsACLReparseHandle refuses a handle that landed on a reparse point.
//
// Deliberately NOT verifyWindowsACLTargetNotRedirected: that one compares the
// handle's resolved path against an expected pathname, which is exactly the
// pathname dependency the handle-relative walk removes. A child opened relative
// to a pinned parent is in the right place by construction even when the
// pathname no longer leads there, so comparing paths would reject correct, safe
// creates whenever the tree was legitimately renamed. The attribute is the only
// thing worth checking here.
func rejectWindowsACLReparseHandle(handle windows.Handle, name string) error {
var info windows.ByHandleFileInformation
if err := windows.GetFileInformationByHandle(handle, &info); err != nil {
return fmt.Errorf("inspect windows ACL component %s: %w", name, err)
}
if info.FileAttributes&windows.FILE_ATTRIBUTE_REPARSE_POINT != 0 {
return fmt.Errorf("refusing to work through reparse-point component %s: possible path swap during elevated setup", name)
}
return nil
}
// verifyWindowsACLHandleIsCleanDirectory rejects a handle that landed on a
// reparse point, or on an object other than the path asked for.
func verifyWindowsACLHandleIsCleanDirectory(handle windows.Handle, path string) error {
var info windows.ByHandleFileInformation
if err := windows.GetFileInformationByHandle(handle, &info); err != nil {
return fmt.Errorf("inspect windows ACL directory %s: %w", path, err)
}
if info.FileAttributes&windows.FILE_ATTRIBUTE_REPARSE_POINT != 0 {
return fmt.Errorf("refusing to materialize under reparse-point path component %s: possible path swap during elevated setup", path)
}
return verifyWindowsACLTargetNotRedirected(handle, path)
}
// isWindowsNotExist reports a missing-object error from either side of the API.
// NtCreateFile returns NTSTATUS values, which do not map to os.ErrNotExist the
// way the Win32 error codes do.
func isWindowsNotExist(err error) bool {
if err == nil {
return false
}
if os.IsNotExist(err) {
return true
}
var status windows.NTStatus
if errors.As(err, &status) {
return status == windows.STATUS_OBJECT_NAME_NOT_FOUND || status == windows.STATUS_OBJECT_PATH_NOT_FOUND
}
return false
}
@@ -0,0 +1,230 @@
//go:build windows
package sandbox
import (
"os"
"path/filepath"
"testing"
"golang.org/x/sys/windows"
)
// THE SWAP THAT PATHNAMES CANNOT SURVIVE.
//
// This is the race behind the materialization P1. A pathname-based create
// resolves the whole path again at the moment it runs, so an ancestor replaced
// between the verification and the create sends the new directory somewhere else
// entirely. Verifying afterwards is too late: the object already exists in the
// wrong place.
//
// A handle pins the OBJECT, not the name. This test performs the swap for real,
// in the window that used to be exploitable, and asserts the child still lands
// in the directory that was verified.
//
// Worth noting for anyone extending this: the fix is what makes the race
// testable at all. Against the old code the swap had to be threaded into the
// middle of a function; here it is three ordinary lines between an open and a
// create, because the handle is held across them.
func TestChildCreationFollowsTheHandleNotThePath(t *testing.T) {
root := t.TempDir()
approved := filepath.Join(root, "approved")
elsewhere := filepath.Join(root, "elsewhere")
for _, dir := range []string{approved, elsewhere} {
if err := os.Mkdir(dir, 0o700); err != nil {
t.Fatalf("seed %s: %v", dir, err)
}
}
// Verified once, exactly as setup does before it materializes anything.
parent, err := openWindowsACLDirectoryNoFollow(approved)
if err != nil {
t.Fatalf("open approved directory: %v", err)
}
defer func() { _ = windows.CloseHandle(parent) }()
// THE SWAP, in the window that used to be exploitable: move the verified
// directory aside and leave a junction to somewhere else wearing its name.
moved := filepath.Join(root, "approved-moved")
if err := os.Rename(approved, moved); err != nil {
t.Skipf("cannot rename a directory with an open handle on this filesystem: %v", err)
}
makeJunction(t, approved, elsewhere)
// The create resolves against the handle, so it must ignore the junction now
// sitting at the original pathname.
child, created, err := createWindowsACLChildDirectory(parent, "materialized")
if err != nil {
t.Fatalf("create child relative to the pinned handle: %v", err)
}
defer func() { _ = windows.CloseHandle(child) }()
if !created {
t.Error("created = false for a directory that did not exist")
}
if _, err := os.Stat(filepath.Join(moved, "materialized")); err != nil {
t.Errorf("the child did not land in the verified directory: %v", err)
}
if _, err := os.Stat(filepath.Join(elsewhere, "materialized")); err == nil {
t.Fatal("ESCAPED: the child was created through the junction, outside the approved tree")
}
}
// Materialization runs on trees that may already be half-built, so creating an
// existing directory has to be a no-op rather than a failure. created must still
// report the truth, because rollback deletes only what this call made.
func TestCreatingAnExistingChildOpensItInstead(t *testing.T) {
root := t.TempDir()
if err := os.Mkdir(filepath.Join(root, "already"), 0o700); err != nil {
t.Fatalf("seed: %v", err)
}
parent, err := openWindowsACLDirectoryNoFollow(root)
if err != nil {
t.Fatalf("open root: %v", err)
}
defer func() { _ = windows.CloseHandle(parent) }()
handle, created, err := createWindowsACLChildDirectory(parent, "already")
if err != nil {
t.Fatalf("open existing child: %v", err)
}
_ = windows.CloseHandle(handle)
if created {
t.Error("created = true for a directory that already existed; rollback would delete a user's data")
}
}
// The rollback counterpart. os.RemoveAll on a pathname whose ancestor has since
// become a junction recurses outside the workspace and deletes unrelated trees,
// which is the second P1. Resolving relative to the parent handle cannot.
func TestDeleteFollowsTheHandleNotThePath(t *testing.T) {
root := t.TempDir()
approved := filepath.Join(root, "approved")
elsewhere := filepath.Join(root, "elsewhere")
for _, dir := range []string{approved, elsewhere} {
if err := os.Mkdir(dir, 0o700); err != nil {
t.Fatalf("seed %s: %v", dir, err)
}
}
// A bystander under the decoy: if the delete ever resolves by pathname it is
// reachable, and its survival is what proves the delete did not.
if err := os.Mkdir(filepath.Join(elsewhere, "victim"), 0o700); err != nil {
t.Fatalf("seed victim: %v", err)
}
if err := os.Mkdir(filepath.Join(approved, "victim"), 0o700); err != nil {
t.Fatalf("seed target: %v", err)
}
parent, err := openWindowsACLDirectoryNoFollow(approved)
if err != nil {
t.Fatalf("open approved directory: %v", err)
}
defer func() { _ = windows.CloseHandle(parent) }()
moved := filepath.Join(root, "approved-moved")
if err := os.Rename(approved, moved); err != nil {
t.Skipf("cannot rename a directory with an open handle on this filesystem: %v", err)
}
makeJunction(t, approved, elsewhere)
if err := deleteWindowsACLChildDirectory(parent, "victim"); err != nil {
t.Fatalf("delete relative to the pinned handle: %v", err)
}
if _, err := os.Stat(filepath.Join(elsewhere, "victim")); err != nil {
t.Fatal("DESTRUCTIVE: rollback followed the junction and deleted a directory outside the approved tree")
}
if _, err := os.Stat(filepath.Join(moved, "victim")); err == nil {
t.Error("the directory inside the approved tree was not removed")
}
}
// A delete that cannot happen must SAY so.
//
// This is the gap that let a silent bug ship in the first version of this file.
// It deleted with FILE_DELETE_ON_CLOSE, which defers the removal to cleanup,
// where a non-empty directory makes it fail with nowhere to report it: the open
// returned success, the close returned success, and the directory was still
// there. The only test covering deletion used an EMPTY directory, so it passed
// throughout. Rollback built on that would have reported success while leaving
// materialized state on disk, which is worse than the os.RemoveAll it replaced,
// because os.RemoveAll actually removed it.
func TestDeletingANonEmptyDirectoryIsReported(t *testing.T) {
root := t.TempDir()
populated := filepath.Join(root, "populated")
if err := os.Mkdir(populated, 0o700); err != nil {
t.Fatalf("seed: %v", err)
}
if err := os.WriteFile(filepath.Join(populated, "occupant"), []byte("x"), 0o600); err != nil {
t.Fatalf("seed occupant: %v", err)
}
parent, err := openWindowsACLDirectoryNoFollow(root)
if err != nil {
t.Fatalf("open root: %v", err)
}
defer func() { _ = windows.CloseHandle(parent) }()
err = deleteWindowsACLChildDirectory(parent, "populated")
if _, statErr := os.Stat(populated); statErr != nil {
t.Fatalf("the directory was removed with its contents, which this delete must never do: %v", statErr)
}
if err == nil {
t.Fatal("reported success while leaving the directory in place")
}
}
// The directory form must refuse a file rather than delete it, and the file form
// must handle the one materialized target that is a file.
func TestDeleteDistinguishesFilesFromDirectories(t *testing.T) {
root := t.TempDir()
if err := os.WriteFile(filepath.Join(root, "config"), []byte("x"), 0o600); err != nil {
t.Fatalf("seed: %v", err)
}
parent, err := openWindowsACLDirectoryNoFollow(root)
if err != nil {
t.Fatalf("open root: %v", err)
}
defer func() { _ = windows.CloseHandle(parent) }()
if err := deleteWindowsACLChildDirectory(parent, "config"); err == nil {
t.Error("the directory delete accepted a file")
}
if err := deleteWindowsACLChildFile(parent, "config"); err != nil {
t.Fatalf("deleteWindowsACLChildFile: %v", err)
}
if _, err := os.Stat(filepath.Join(root, "config")); err == nil {
t.Error("the file survived its delete")
}
}
// Rollback runs on failure paths where the object may never have been created,
// so a missing child is success rather than an error to report.
func TestDeletingAMissingChildIsNotAnError(t *testing.T) {
root := t.TempDir()
parent, err := openWindowsACLDirectoryNoFollow(root)
if err != nil {
t.Fatalf("open root: %v", err)
}
defer func() { _ = windows.CloseHandle(parent) }()
if err := deleteWindowsACLChildDirectory(parent, "never-existed"); err != nil {
t.Fatalf("deleting a missing child reported an error: %v", err)
}
}
// The anchor open is the one pathname resolution in the walk, so it has to
// refuse a junction itself rather than leaving it to a later check.
func TestOpeningAJunctionAnchorIsRefused(t *testing.T) {
root := t.TempDir()
real := filepath.Join(root, "real")
if err := os.Mkdir(real, 0o700); err != nil {
t.Fatalf("seed: %v", err)
}
link := filepath.Join(root, "link")
makeJunction(t, link, real)
handle, err := openWindowsACLDirectoryNoFollow(link)
if err == nil {
_ = windows.CloseHandle(handle)
t.Fatal("opened a junction as the materialization anchor; every create beneath it would land outside the approved tree")
}
}
@@ -0,0 +1,161 @@
//go:build windows
package sandbox
import (
"fmt"
"path/filepath"
"strings"
"golang.org/x/sys/windows"
)
// GetFinalPathNameByHandle flags. x/sys/windows does not export these.
const (
windowsFileNameNormalized uint32 = 0x0
windowsVolumeNameDOS uint32 = 0x0
)
// verifyWindowsACLTargetNotRedirected fails when an opened handle resolved
// somewhere other than the requested path, which means a component along the way
// is a reparse point.
//
// openWindowsACLTarget's FILE_FLAG_OPEN_REPARSE_POINT check covers the FINAL
// component only; CreateFile still resolves ANCESTORS. A user who controls the
// workspace can turn an ancestor — .git, say — into a junction before elevated
// setup runs, and setup would then apply its DACL change to an object outside
// the approved tree while the final-component check still passed. Junctions need
// no privilege to create, unlike symlinks, so this is reachable by exactly the
// unprivileged user the sandbox exists to contain.
//
// GetFinalPathNameByHandle answers where the handle actually landed, covering
// every component in one call rather than walking the path and re-checking each
// component (which would also race between the checks).
//
// The comparison basis must NEVER follow a reparse point, and getting that wrong
// is what made this guard mostly ornamental.
//
// It used to compare against canonicalSandboxWorkspaceRoot(path), which runs
// filepath.EvalSymlinks — the same resolution the kernel just performed. So for a
// directory SYMLINK the two sides agreed precisely BECAUSE the redirect happened:
// GetFinalPathNameByHandle followed the link to produce one side, EvalSymlinks
// followed the same link to produce the other, and elevated setup went on to
// rewrite the DACL of an object outside the workspace.
//
// Junctions were rejected, but by accident rather than by design. Go reports a
// junction as ModeIrregular rather than ModeSymlink, so EvalSymlinks refuses it,
// canonicalSandboxWorkspaceRoot falls back to the lexical path, and the mismatch
// surfaces. That is a property of the standard library's mode bits, not of this
// check: a Go release that resolved mount points would silently disarm the one
// case this was known to catch.
//
// So the expected side is now normalized WITHOUT resolving anything. Casing and
// 8.3 short names still have to compare equal, since a legitimate target can be
// spelled either way and still be the same object — EqualFold covers the first
// and GetLongPathName the second, and neither follows a link.
//
// This does mean a target deliberately spelled through a symlink is now refused.
// That is the intended direction: the whole question here is whether the object
// the handle landed on is the object that was named, and a caller that wants a
// link's target should name the target.
func verifyWindowsACLTargetNotRedirected(handle windows.Handle, path string) error {
buffer := make([]uint16, windows.MAX_LONG_PATH)
n, err := windows.GetFinalPathNameByHandle(handle, &buffer[0], uint32(len(buffer)), windowsFileNameNormalized|windowsVolumeNameDOS)
if err != nil {
return fmt.Errorf("resolve windows ACL target %s: %w", path, err)
}
if int(n) < len(buffer) {
buffer = buffer[:n]
}
actual := trimWindowsExtendedPathPrefix(windows.UTF16ToString(buffer))
expected := trimWindowsExtendedPathPrefix(windowsACLComparablePath(path))
if !strings.EqualFold(filepath.Clean(actual), filepath.Clean(expected)) {
return fmt.Errorf("refusing to apply ACL to %s: it resolves to %s, so a parent directory is a reparse point (possible path swap during elevated setup)", path, actual)
}
return nil
}
// windowsACLComparablePath normalizes a path for comparison against where a
// handle actually landed, WITHOUT resolving any reparse point.
//
// The two things that must still compare equal are casing and 8.3 short names,
// because either can spell the same object. GetLongPathName expands the short
// form by reading directory entries; it does not follow a symlink or a junction
// to its target, which is the entire reason it is used here instead of
// EvalSymlinks. Casing is left to the caller's EqualFold.
//
// Every failure degrades to the lexically cleaned path rather than to a resolved
// one. A path this cannot expand is compared as written, which can only produce
// a spurious MISMATCH — a refusal — and never a spurious match. That is the
// direction a redirect check has to fail in.
func windowsACLComparablePath(path string) string {
cleaned := filepath.Clean(strings.TrimSpace(path))
if cleaned == "" || cleaned == "." {
return cleaned
}
if absolute, err := filepath.Abs(cleaned); err == nil {
cleaned = absolute
}
wide, err := windows.UTF16PtrFromString(cleaned)
if err != nil {
return cleaned
}
buffer := make([]uint16, windows.MAX_LONG_PATH)
n, err := windows.GetLongPathName(wide, &buffer[0], uint32(len(buffer)))
if err != nil || n == 0 || int(n) >= len(buffer) {
return cleaned
}
return filepath.Clean(windows.UTF16ToString(buffer[:n]))
}
// trimWindowsExtendedPathPrefix strips the \?\ form GetFinalPathNameByHandle
// returns so it can be compared with an ordinary path.
func trimWindowsExtendedPathPrefix(path string) string {
// Built from filepath.Separator rather than written as literals so the
// backslashes cannot be miscounted by whatever writes this file.
sep := string(filepath.Separator)
devicePrefix := sep + sep + "?" + sep
uncPrefix := devicePrefix + "UNC" + sep
if strings.HasPrefix(path, uncPrefix) {
return sep + sep + strings.TrimPrefix(path, uncPrefix)
}
return strings.TrimPrefix(path, devicePrefix)
}
// verifyWindowsACLPathComponentNotRedirected opens one path component no-follow
// and refuses it if it is a reparse point or resolves anywhere other than its own
// pathname. Because GetFinalPathNameByHandle answers for the WHOLE resolved path,
// verifying a single existing component also clears every ancestor above it.
//
// A missing component surfaces as os.ErrNotExist so the caller can walk further
// up. Only FILE_READ_ATTRIBUTES is requested: this inspects, it never writes, and
// asking for more would fail on ancestors the setup process has no rights on.
func verifyWindowsACLPathComponentNotRedirected(path string) error {
utf16Path, err := windows.UTF16PtrFromString(path)
if err != nil {
return fmt.Errorf("encode windows ACL path component %s: %w", path, err)
}
handle, err := windows.CreateFile(
utf16Path,
windows.FILE_READ_ATTRIBUTES,
windows.FILE_SHARE_READ|windows.FILE_SHARE_WRITE|windows.FILE_SHARE_DELETE,
nil,
windows.OPEN_EXISTING,
windows.FILE_FLAG_BACKUP_SEMANTICS|windows.FILE_FLAG_OPEN_REPARSE_POINT,
0,
)
if err != nil {
// syscall.Errno.Is maps ERROR_FILE_NOT_FOUND/ERROR_PATH_NOT_FOUND to
// os.ErrNotExist, so the caller's errors.Is check keeps working.
return fmt.Errorf("open windows ACL path component %s: %w", path, err)
}
defer func() { _ = windows.CloseHandle(handle) }()
var info windows.ByHandleFileInformation
if err := windows.GetFileInformationByHandle(handle, &info); err != nil {
return fmt.Errorf("inspect windows ACL path component %s: %w", path, err)
}
if info.FileAttributes&windows.FILE_ATTRIBUTE_REPARSE_POINT != 0 {
return fmt.Errorf("refusing to materialize under reparse-point path component %s: possible path swap during elevated setup", path)
}
return verifyWindowsACLTargetNotRedirected(handle, path)
}
@@ -0,0 +1,79 @@
//go:build windows
package sandbox
import (
"os"
"os/exec"
"path/filepath"
"strings"
"testing"
"golang.org/x/sys/windows"
)
// An unprivileged user who controls the workspace can turn an ancestor of a
// configured ACL target into a junction before elevated setup runs. CreateFile
// resolves ancestors even with FILE_FLAG_OPEN_REPARSE_POINT, so the
// final-component check passes and setup would rewrite the DACL of an object
// outside the approved tree.
//
// Junctions, unlike symlinks, need no privilege — which is what makes this
// reachable by exactly the user the sandbox is containing.
func TestOpenWindowsACLTargetRefusesAJunctionAncestor(t *testing.T) {
base := t.TempDir()
workspace := filepath.Join(base, "workspace")
outside := filepath.Join(base, "OUTSIDE")
for _, dir := range []string{workspace, outside} {
if err := os.MkdirAll(dir, 0o700); err != nil {
t.Fatalf("mkdir %s: %v", dir, err)
}
}
// The object the attacker wants setup to touch.
victim := filepath.Join(outside, "hooks")
if err := os.MkdirAll(victim, 0o700); err != nil {
t.Fatalf("mkdir victim: %v", err)
}
// .git is the ancestor, and it is a junction to OUTSIDE.
gitDir := filepath.Join(workspace, ".git")
if out, err := exec.Command("cmd", "/c", "mklink", "/J", gitDir, outside).CombinedOutput(); err != nil {
t.Skipf("cannot create a junction here: %v %s", err, out)
}
// This is the path setup would be configured with.
target := filepath.Join(gitDir, "hooks")
if _, err := os.Stat(target); err != nil {
t.Fatalf("precondition: the junction should make %s reachable: %v", target, err)
}
handle, _, err := openWindowsACLTarget(target)
if err == nil {
_ = windows.CloseHandle(handle)
t.Fatal("opened an ACL target through a junction ancestor; setup would have rewritten a DACL outside the workspace")
}
if !strings.Contains(err.Error(), "reparse point") {
t.Errorf("error = %v, want it to name the reparse point", err)
}
t.Logf("refused as expected: %v", err)
}
// The guard must not reject ordinary targets, including ones spelled
// non-canonically — a differently-cased path is the same object, not a redirect.
func TestOpenWindowsACLTargetAcceptsAnOrdinaryTarget(t *testing.T) {
dir := t.TempDir()
nested := filepath.Join(dir, "Nested")
if err := os.MkdirAll(nested, 0o700); err != nil {
t.Fatalf("mkdir: %v", err)
}
for _, spelling := range []string{nested, strings.ToLower(nested)} {
handle, isDir, err := openWindowsACLTarget(spelling)
if err != nil {
t.Fatalf("openWindowsACLTarget(%q): %v", spelling, err)
}
if !isDir {
t.Errorf("%q reported as not a directory", spelling)
}
_ = windows.CloseHandle(handle)
}
}
@@ -0,0 +1,200 @@
//go:build windows
package sandbox
import (
"os"
"path/filepath"
"strings"
"testing"
"golang.org/x/sys/windows"
)
// THE RESTORE MUST LAND ON THE OBJECT THE DACL CAME FROM.
//
// Creation and the materialization unwind were both bound to handles, and the
// restore branch was left re-resolving the target by pathname. Its comment
// justified that with a no-follow re-open, which rules out a REPARSE POINT
// swapped in since apply and nothing else. The other substitution passes it
// untouched: rename the target aside and put an ordinary directory of the same
// name in its place. Nothing in that decoy is a link, so the no-follow open
// succeeds, the pre-apply DACL is written onto the attacker's object, and the
// real one keeps the ACEs from the setup that just aborted.
func TestRollbackRefusesToRestoreOntoAReplacedTarget(t *testing.T) {
root := t.TempDir()
approved := filepath.Join(root, "ws")
target := filepath.Join(approved, "target")
if err := os.MkdirAll(target, 0o700); err != nil {
t.Fatalf("seed the approved tree: %v", err)
}
handle, _, err := openWindowsACLTarget(target)
if err != nil {
t.Fatalf("open the target: %v", err)
}
descriptor, err := windows.GetSecurityInfo(handle, windows.SE_FILE_OBJECT, windows.DACL_SECURITY_INFORMATION)
if err != nil {
_ = windows.CloseHandle(handle)
t.Fatalf("read the target DACL: %v", err)
}
identity, err := windowsIdentityOfHandle(handle)
if err != nil {
_ = windows.CloseHandle(handle)
t.Fatalf("read the target identity: %v", err)
}
_ = windows.CloseHandle(handle)
// The swap, exactly as it would happen between apply and rollback. Ordinary
// directories throughout: no links, no reparse points.
if err := os.Rename(target, target+"-moved"); err != nil {
t.Skipf("cannot rename here: %v", err)
}
if err := os.Mkdir(target, 0o700); err != nil {
t.Fatalf("plant the replacement: %v", err)
}
snapshot := windowsACLSnapshot{Path: target, Descriptor: descriptor, TargetID: identity}
err = rollbackWindowsACLSnapshots([]windowsACLSnapshot{snapshot})
if err == nil {
t.Fatal("rollback wrote the pre-apply DACL onto a different object wearing the target's name")
}
if !strings.Contains(err.Error(), "no longer the object") {
t.Errorf("refused for the wrong reason: %v", err)
}
}
// And an untouched target still restores, or the guard above would be satisfied
// by a rollback that refuses everything.
func TestRollbackRestoresAnUnchangedTarget(t *testing.T) {
target := filepath.Join(t.TempDir(), "target")
if err := os.Mkdir(target, 0o700); err != nil {
t.Fatalf("seed the target: %v", err)
}
handle, _, err := openWindowsACLTarget(target)
if err != nil {
t.Fatalf("open the target: %v", err)
}
descriptor, err := windows.GetSecurityInfo(handle, windows.SE_FILE_OBJECT, windows.DACL_SECURITY_INFORMATION)
if err != nil {
_ = windows.CloseHandle(handle)
t.Fatalf("read the target DACL: %v", err)
}
identity, err := windowsIdentityOfHandle(handle)
if err != nil {
_ = windows.CloseHandle(handle)
t.Fatalf("read the target identity: %v", err)
}
_ = windows.CloseHandle(handle)
snapshot := windowsACLSnapshot{Path: target, Descriptor: descriptor, TargetID: identity}
if err := rollbackWindowsACLSnapshots([]windowsACLSnapshot{snapshot}); err != nil {
t.Fatalf("an unchanged target was refused: %v", err)
}
}
// THE COMMENT AT rollbackWindowsACLSnapshots CLAIMED A TEST THAT DID NOT EXIST.
//
// It said "TestRollbackUnwindsDescendantsBeforeAncestors pins it" about the
// reverse iteration order, and grepping the repo found only that sentence. The
// ordering is load-bearing twice over: a materialized directory must be empty
// before its own removal is attempted, and SetSecurityInfo propagates
// inheritable ACEs downward so the ancestor has to be restored last. Neither
// was pinned by anything.
func TestRollbackUnwindsDescendantsBeforeAncestors(t *testing.T) {
root := t.TempDir()
ancestor := filepath.Join(root, "ws")
descendant := filepath.Join(ancestor, "child")
if err := os.MkdirAll(descendant, 0o700); err != nil {
t.Fatalf("seed the tree: %v", err)
}
snapshotFor := func(path string) windowsACLSnapshot {
t.Helper()
handle, _, err := openWindowsACLTarget(path)
if err != nil {
t.Fatalf("open %s: %v", path, err)
}
defer windows.CloseHandle(handle)
descriptor, err := windows.GetSecurityInfo(handle, windows.SE_FILE_OBJECT, windows.DACL_SECURITY_INFORMATION)
if err != nil {
t.Fatalf("read the DACL for %s: %v", path, err)
}
identity, err := windowsIdentityOfHandle(handle)
if err != nil {
t.Fatalf("read the identity for %s: %v", path, err)
}
return windowsACLSnapshot{Path: path, Descriptor: descriptor, TargetID: identity}
}
// Ascending by path key, the order applyWindowsACLPlan produces.
snapshots := []windowsACLSnapshot{snapshotFor(ancestor), snapshotFor(descendant)}
var order []string
restore := windowsACLRestoreHook
windowsACLRestoreHook = func(path string) { order = append(order, path) }
t.Cleanup(func() { windowsACLRestoreHook = restore })
if err := rollbackWindowsACLSnapshots(snapshots); err != nil {
t.Fatalf("rollbackWindowsACLSnapshots: %v", err)
}
if len(order) != 2 {
t.Fatalf("restored %d targets, want 2: %v", len(order), order)
}
if order[0] != descendant || order[1] != ancestor {
t.Errorf("restore order was %v; the descendant must be restored before its ancestor, because SetSecurityInfo propagates inheritable ACEs downward", order)
}
}
// The snapshots arrive in APPLY order, not path order. applyWindowsACLPlan's
// deferred pass appends a group whose target only appeared during the first
// pass, typically an ancestor (.git after .git\config), so the ancestor is LAST
// in the list. Rollback must still unwind the descendant first.
func TestRollbackUnwindsADeferredAncestorAfterItsDescendants(t *testing.T) {
root := t.TempDir()
ancestor := filepath.Join(root, ".git")
descendant := filepath.Join(ancestor, "config")
if err := os.MkdirAll(descendant, 0o700); err != nil {
t.Fatalf("seed the tree: %v", err)
}
snapshotFor := func(path string) windowsACLSnapshot {
t.Helper()
handle, _, err := openWindowsACLTarget(path)
if err != nil {
t.Fatalf("open %s: %v", path, err)
}
defer windows.CloseHandle(handle)
descriptor, err := windows.GetSecurityInfo(handle, windows.SE_FILE_OBJECT, windows.DACL_SECURITY_INFORMATION)
if err != nil {
t.Fatalf("read the DACL for %s: %v", path, err)
}
identity, err := windowsIdentityOfHandle(handle)
if err != nil {
t.Fatalf("read the identity for %s: %v", path, err)
}
return windowsACLSnapshot{Path: path, Descriptor: descriptor, TargetID: identity}
}
// First pass applied the descendant; the deferred pass applied the ancestor.
snapshots := []windowsACLSnapshot{snapshotFor(descendant), snapshotFor(ancestor)}
var order []string
restore := windowsACLRestoreHook
windowsACLRestoreHook = func(path string) { order = append(order, path) }
t.Cleanup(func() { windowsACLRestoreHook = restore })
if err := rollbackWindowsACLSnapshots(snapshots); err != nil {
t.Fatalf("rollbackWindowsACLSnapshots: %v", err)
}
if len(order) != 2 {
t.Fatalf("restored %d targets, want 2: %v", len(order), order)
}
if order[0] != descendant || order[1] != ancestor {
t.Errorf("restore order was %v; a deferred ancestor must still be restored after its descendant", order)
}
if snapshots[0].Path != descendant || snapshots[1].Path != ancestor {
t.Errorf("rollback reordered the caller's slice: %v, %v", snapshots[0].Path, snapshots[1].Path)
}
}
@@ -0,0 +1,102 @@
//go:build windows
package sandbox
import (
"os"
"path/filepath"
"testing"
)
// ROLLBACK DELETES THE OBJECT IT CREATED, NOT WHATEVER NOW WEARS ITS NAME.
//
// The anchor's identity was verified, but the created children were recorded
// by name only, so after setup materialized .git/config another process could
// move it aside and put an ordinary file at that name beneath the unchanged
// anchor, and a later setup failure deleted the replacement. Each created
// component now carries the identity read from the handle that created it,
// and the delete disposition is set on a handle whose identity was checked.
func TestRollbackRefusesAReplacedMaterializedChild(t *testing.T) {
for name, asFile := range map[string]bool{"file target": true, "directory target": false} {
t.Run(name, func(t *testing.T) {
workspace := t.TempDir()
target := filepath.Join(workspace, ".git", "hooks")
if asFile {
target = filepath.Join(workspace, ".git", "config")
}
created, err := materializeWindowsACLTarget(target, asFile)
if err != nil {
t.Fatalf("materialize: %v", err)
}
if !created.createdAnything() {
t.Fatal("SETUP INVALID: nothing was materialized")
}
// Another process moves the created object aside and puts an
// ordinary one of the same shape at its name. The anchor above is
// untouched, so the anchor identity check cannot see this.
aside := target + ".aside"
if err := os.Rename(target, aside); err != nil {
t.Fatalf("rename aside: %v", err)
}
if asFile {
if err := os.WriteFile(target, []byte("theirs"), 0o600); err != nil {
t.Fatal(err)
}
} else {
if err := os.Mkdir(target, 0o700); err != nil {
t.Fatal(err)
}
if err := os.WriteFile(filepath.Join(target, "keep"), []byte("theirs"), 0o600); err != nil {
t.Fatal(err)
}
}
removed, err := rollbackWindowsACLMaterialization(created)
// The replacement is the whole point: it has to survive, whatever the
// rollback reported about itself.
if _, statErr := os.Lstat(target); statErr != nil {
t.Fatalf("rollback deleted the replacement at %s, which it never created: %v", target, statErr)
}
if !asFile {
if _, statErr := os.Lstat(filepath.Join(target, "keep")); statErr != nil {
t.Fatalf("the replacement directory's contents are gone: %v", statErr)
}
}
if err == nil {
t.Fatal("rollback left a replacement it never created without saying why")
}
if removed {
t.Fatal("rollback reported the target removed after refusing the replacement")
}
})
}
}
// CONTROL: the unreplaced case still unwinds completely, so the identity check
// cannot pass by refusing everything.
func TestRollbackRemovesTheChildrenItActuallyCreated(t *testing.T) {
for name, asFile := range map[string]bool{"file target": true, "directory target": false} {
t.Run(name, func(t *testing.T) {
workspace := t.TempDir()
target := filepath.Join(workspace, ".git", "hooks")
if asFile {
target = filepath.Join(workspace, ".git", "config")
}
created, err := materializeWindowsACLTarget(target, asFile)
if err != nil {
t.Fatalf("materialize: %v", err)
}
removed, err := rollbackWindowsACLMaterialization(created)
if err != nil {
t.Fatalf("rollback: %v", err)
}
if !removed {
t.Fatal("rollback did not report the target removed")
}
if _, statErr := os.Lstat(filepath.Join(workspace, ".git")); !os.IsNotExist(statErr) {
t.Fatalf(".git survived a rollback of what created it: %v", statErr)
}
})
}
}
@@ -0,0 +1,113 @@
//go:build windows
package sandbox
import (
"os"
"os/exec"
"path/filepath"
"strings"
"testing"
"golang.org/x/sys/windows"
)
// THE COMPARISON BASIS MUST NOT FOLLOW WHAT IT IS CHECKING FOR.
//
// verifyWindowsACLTargetNotRedirected asks GetFinalPathNameByHandle where the
// handle landed and compares that against the requested path. It used to build
// the second side with filepath.EvalSymlinks, which is the same resolution the
// kernel had just performed, so for a directory symlink the two sides agreed
// BECAUSE the redirect happened, and elevated setup rewrote the DACL of an
// object outside the workspace.
//
// Junctions were caught, but only because Go reports one as ModeIrregular and
// EvalSymlinks declines it, leaving the lexical path to disagree. That is a
// standard-library detail, not a property of the guard.
// The property, testable with no privilege at all: the normalizer must not
// resolve a reparse point.
//
// HONEST LIMIT, because it would be easy to read more into this than it proves.
// A junction is used because creating one needs no privilege, and EvalSymlinks
// does not resolve a junction either — so this test passes against BOTH the old
// basis and the new one, and reverting the fix does not fail it. It is an
// invariant test, not a regression for this change: it pins that normalization
// leaves a reparse point alone, which is what would break first if a future Go
// started resolving mount points and silently disarmed the junction case.
//
// The case that actually separates the two bases is the directory symlink below,
// and that one skips without privilege. On this machine it skipped.
func TestACLComparablePathDoesNotResolveAReparsePoint(t *testing.T) {
base := t.TempDir()
outside := filepath.Join(base, "outside")
if err := os.MkdirAll(filepath.Join(outside, "hooks"), 0o700); err != nil {
t.Fatalf("mkdir outside: %v", err)
}
link := filepath.Join(base, "link")
if out, err := exec.Command("cmd", "/c", "mklink", "/J", link, outside).CombinedOutput(); err != nil {
t.Skipf("cannot create a junction here: %v (%s)", err, out)
}
through := filepath.Join(link, "hooks")
comparable := windowsACLComparablePath(through)
// Compared against the normalizer's OWN answer for each path, never against
// the raw input. GetLongPathName legitimately rewrites the string: on a CI
// runner the temp directory is an 8.3 short name, so expanding RUNNER~1 to
// runneradmin makes the result differ from what was passed in while naming
// exactly the same object. An earlier version of this test asserted equality
// with the input and failed on Windows CI for that reason, which was the test
// being wrong rather than the code.
target := windowsACLComparablePath(filepath.Join(outside, "hooks"))
// The whole property: normalizing a path THROUGH the reparse point must not
// produce the target's normalization. If it did, the guard would be comparing
// a redirected handle against a redirected expectation and matching itself.
if strings.EqualFold(filepath.Clean(comparable), filepath.Clean(target)) {
t.Errorf("windowsACLComparablePath resolved through the reparse point:\n through %s\n target %s", comparable, target)
}
// And it still has to name the link component, or it resolved to something
// else entirely rather than leaving the path alone.
if !strings.Contains(strings.ToLower(comparable), "link") {
t.Errorf("windowsACLComparablePath lost the link component: %s", comparable)
}
// The old basis is checked alongside for contrast: where it resolves, it
// could not have been the comparison basis.
if resolved := canonicalSandboxWorkspaceRoot(through); strings.EqualFold(filepath.Clean(resolved), filepath.Clean(filepath.Join(outside, "hooks"))) {
t.Logf("confirmed: canonicalSandboxWorkspaceRoot resolves %s to %s, which is why it cannot be the basis", through, resolved)
}
}
// The end-to-end symlink case the finding names. Directory symlinks need either
// Developer Mode or SeCreateSymbolicLinkPrivilege, so this skips where it cannot
// build the fixture rather than passing vacuously.
func TestOpenWindowsACLTargetRefusesASymlinkAncestor(t *testing.T) {
base := t.TempDir()
outside := filepath.Join(base, "outside")
if err := os.MkdirAll(filepath.Join(outside, "hooks"), 0o700); err != nil {
t.Fatalf("mkdir outside: %v", err)
}
workspace := filepath.Join(base, "workspace")
if err := os.MkdirAll(workspace, 0o700); err != nil {
t.Fatalf("mkdir workspace: %v", err)
}
// A DIRECTORY symlink, not a junction: os.Symlink maps to CreateSymbolicLinkW
// and the directory flag is inferred from the existing target.
link := filepath.Join(workspace, ".git")
if err := os.Symlink(outside, link); err != nil {
t.Skipf("cannot create a directory symlink here (needs Developer Mode or SeCreateSymbolicLinkPrivilege): %v", err)
}
target := filepath.Join(link, "hooks")
handle, _, err := openWindowsACLTarget(target)
if err == nil {
_ = windows.CloseHandle(handle)
t.Fatal("elevated setup opened a target through a symlinked ancestor; its DACL change would land outside the workspace")
}
if !strings.Contains(err.Error(), "reparse point") {
t.Errorf("refusal does not name the cause: %v", err)
}
}
+42 -3
View File
@@ -46,9 +46,14 @@ func TestBuildWindowsACLPlanForWorkspaceWriteProfile(t *testing.T) {
assertWindowsACLEntry(t, plan, WindowsACLAllowWrite, `C:\workspace`, workspaceSID, false)
assertWindowsACLEntry(t, plan, WindowsACLAllowWrite, `D:\cache`, cacheSID, false)
assertWindowsACLEntry(t, plan, WindowsACLDenyWrite, `C:\workspace\vendor`, workspaceSID, false)
assertWindowsACLEntry(t, plan, WindowsACLDenyWrite, `C:\workspace\.git`, workspaceSID, false)
assertWindowsACLEntry(t, plan, WindowsACLDenyWrite, `C:\workspace\.zero`, workspaceSID, false)
// Materialized, matching the principal plan. A guard attached to an object
// that does not exist yet is never applied: on a workspace with no .git at
// setup time both passes skipped these while setup still recorded success.
// Creating them is also what lets the deferred pass reach the deny-delete on
// .git, since config and hooks create .git as their parent.
assertWindowsACLEntry(t, plan, WindowsACLDenyWrite, `C:\workspace\vendor`, workspaceSID, true)
assertWindowsACLEntry(t, plan, WindowsACLDenyWrite, `C:\workspace\.git`, workspaceSID, true)
assertWindowsACLEntry(t, plan, WindowsACLDenyWrite, `C:\workspace\.zero`, workspaceSID, true)
assertWindowsACLEntry(t, plan, WindowsACLDenyWrite, `C:\workspace\secret-write`, workspaceSID, false)
assertWindowsACLEntry(t, plan, WindowsACLDenyWrite, `C:\workspace\secret-write`, cacheSID, false)
assertWindowsACLEntry(t, plan, WindowsACLDenyRead, `C:\workspace\secret-read`, workspaceSID, true)
@@ -354,3 +359,37 @@ func TestBuildWindowsACLPlanLeavesAnOutOfRootSubpathUnanchored(t *testing.T) {
t.Errorf("out-of-root subpath carries anchor %q, want none: the apply would refuse a config that works today", outsideAnchor)
}
}
func TestBuildWindowsACLPlanUsesReadOnlySIDWithoutWriteRoots(t *testing.T) {
home := t.TempDir()
caps, err := LoadOrCreateWindowsCapabilitySIDs(home)
if err != nil {
t.Fatalf("LoadOrCreateWindowsCapabilitySIDs: %v", err)
}
plan, err := BuildWindowsACLPlan(WindowsSandboxCommandConfig{
SandboxHome: home,
PermissionProfile: PermissionProfile{
FileSystem: FileSystemPolicy{
Kind: FileSystemRestricted,
DenyRead: []string{`C:\workspace\secret-read`},
},
Network: NetworkPolicy{Mode: NetworkDeny},
},
})
if err != nil {
t.Fatalf("BuildWindowsACLPlan: %v", err)
}
// Two deny entries, one per SID the token can carry here. ReadOnly is the
// only capability a profile with no write roots gets, and ReadAllow is the
// read grant a DenyRead profile's strict token carries: denying just one of
// them leaves the carveout readable through the other.
if len(plan.Entries) != 2 {
t.Fatalf("ACL entries = %#v, want a deny-read entry per capability SID", plan.Entries)
}
assertWindowsACLEntry(t, plan, WindowsACLDenyRead, `C:\workspace\secret-read`, caps.ReadOnly, true)
readSID, err := WindowsReadAllowSID(home)
if err != nil {
t.Fatalf("WindowsReadAllowSID: %v", err)
}
assertWindowsACLEntry(t, plan, WindowsACLDenyRead, `C:\workspace\secret-read`, readSID, true)
}
@@ -0,0 +1,87 @@
//go:build windows
package sandbox
import (
"os"
"os/exec"
"path/filepath"
"strings"
"testing"
)
// ELEVATED SETUP MUST NOT CREATE THROUGH A JUNCTION THE CALLER PLANTED.
//
// ensureWindowsSandboxRuntimeCandidates runs as Administrator, and os.MkdirAll
// follows links. Both candidate ancestries are prepared by the invoking user, so
// a junction at a not-yet-created component below the cache directory — or at the
// fallback anchor — made elevated setup build the runtime tree beneath a
// redirected, Administrator-writable target. The ACL applier's no-follow check
// runs later and spots the redirection, but the privileged create has already
// happened by then, outside its rollback boundary.
//
// A junction needs no privilege on Windows, so this reproduces the caller's half
// of the race on an ordinary unelevated box.
func TestRuntimeCandidateCreationRefusesAJunctionedComponent(t *testing.T) {
cacheRoot := t.TempDir()
target := t.TempDir()
previous := sandboxUserCacheDir
t.Cleanup(func() { sandboxUserCacheDir = previous })
sandboxUserCacheDir = func() (string, error) { return cacheRoot, nil }
workspace := t.TempDir()
candidate, ok := deterministicSandboxRuntimeRoot(canonicalSandboxWorkspaceRoot(workspace), canonicalSandboxWorkspaceRoot(cacheRoot))
if !ok {
t.Fatalf("SETUP INVALID: no deterministic candidate for %s under %s", workspace, cacheRoot)
}
// The component the caller controls: the first one Zero owns, below the
// operator's cache directory.
owned := filepath.Join(canonicalSandboxWorkspaceRoot(cacheRoot), "zero")
if !strings.HasPrefix(strings.ToLower(candidate), strings.ToLower(owned)) {
t.Fatalf("SETUP INVALID: candidate %s does not sit under the owned component %s", candidate, owned)
}
if out, err := exec.Command("cmd", "/c", "mklink", "/J", owned, target).CombinedOutput(); err != nil {
t.Fatalf("SETUP INVALID: mklink /J: %v\n%s", err, out)
}
err := ensureRuntimeCandidateDir(candidate)
if err == nil {
t.Fatal("elevated setup created the runtime tree through a junction the caller planted")
}
// The whole point: nothing may appear beneath the redirected target.
entries, readErr := os.ReadDir(target)
if readErr != nil {
t.Fatal(readErr)
}
if len(entries) != 0 {
names := make([]string, 0, len(entries))
for _, entry := range entries {
names = append(names, entry.Name())
}
t.Fatalf("setup created %v beneath the redirected target", names)
}
}
// And an ordinary cache directory still gets its candidate, or the refusal above
// would be satisfied by a creator that refuses everything.
func TestRuntimeCandidateCreationStillCreatesAnOrdinaryTree(t *testing.T) {
cacheRoot := t.TempDir()
previous := sandboxUserCacheDir
t.Cleanup(func() { sandboxUserCacheDir = previous })
sandboxUserCacheDir = func() (string, error) { return cacheRoot, nil }
workspace := t.TempDir()
candidate, ok := deterministicSandboxRuntimeRoot(canonicalSandboxWorkspaceRoot(workspace), canonicalSandboxWorkspaceRoot(cacheRoot))
if !ok {
t.Fatalf("SETUP INVALID: no deterministic candidate for %s", workspace)
}
if err := ensureRuntimeCandidateDir(candidate); err != nil {
t.Fatalf("an ordinary cache tree was refused: %v", err)
}
info, err := os.Stat(candidate)
if err != nil || !info.IsDir() {
t.Fatalf("the candidate was not created: err=%v", err)
}
}
@@ -3,8 +3,11 @@
package sandbox
import (
"errors"
"fmt"
"io"
"os"
"strings"
)
func runWindowsSandboxCommand(config WindowsSandboxCommandConfig, stderr io.Writer) int {
@@ -23,6 +26,15 @@ func runWindowsSandboxCommand(config WindowsSandboxCommandConfig, stderr io.Writ
fmt.Fprintln(stderr, WindowsSandboxCommandRunnerName+": "+err.Error())
return 1
}
// The marker attests to a PLAN. This attests to the OBJECT that plan was
// applied to, which cleanup can reclaim and an ordinary run then recreates
// without the capability ACE. Checked before the token is minted, so the
// operator is told to rerun setup instead of watching every sandboxed write
// fail with a bare access-denied.
if err := verifyWindowsRuntimeRootCapability(config); err != nil {
fmt.Fprintln(stderr, WindowsSandboxCommandRunnerName+": "+err.Error())
return 1
}
case WindowsSandboxLevelUnelevated:
if err := ensureWindowsUnelevatedSetup(config); err != nil {
fmt.Fprintln(stderr, WindowsSandboxCommandRunnerName+": "+err.Error())
@@ -84,6 +96,115 @@ func runWindowsSandboxCommand(config WindowsSandboxCommandConfig, stderr io.Writ
// DenyRead is rejected above for both runner levels rather than launching a
// fully restricted narrow-SID token that cannot execute normal tools.
writeRestricted := len(config.PermissionProfile.FileSystem.DenyRead) == 0
// A provisioned sandbox principal replaces the restricted token entirely: it
// is a separate account, so reads outside its granted roots are denied by the
// filesystem rather than left open the way a same-user restricted token has
// to leave them (#662). Absent, unprovisioned or opted-out, ok is false and
// the restricted-token backend below runs exactly as before.
principalToken, ok, err := windowsSandboxPrincipalToken(config)
if err != nil {
// The one path here that does not fall back, because a provisioned but
// unusable principal means the sandbox is broken rather than absent. Say
// how to get out of it, since the whole backend is opt-in.
fmt.Fprintf(stderr, "%s: sandbox principal is provisioned but unusable: %v. Re-run `zero sandbox setup` from an elevated terminal, or unset %s to fall back to the restricted-token sandbox.\n",
WindowsSandboxCommandRunnerName, err, windowsSandboxIdentityEnv)
return 1
}
if ok {
defer principalToken.Close()
// The principal gets its own identity AND the write jail, not one or the
// other. Its ACEs confine reads; without the restricted token it would
// still hold every write its ambient memberships grant, so a profile
// permitting writes only to the workspace could still write anywhere
// BATCH or BUILTIN\Users may — C:\Users\Public\Documents, for one.
//
// The principal's own SID is deliberately NOT a restricting SID, and that
// is the whole of the write jail on this path.
//
// WRITE_RESTRICTED allows a write only when BOTH the normal token and the
// restricting-SID list allow it. The account SID is already enabled in the
// normal token, so listing it as a restricting SID makes the second check
// a formality for anything granted to that account: every path carrying a
// direct principal ACE passes both halves and is writable wherever it
// sits. The principal's own profile directory, which Windows creates on
// first logon with exactly such an ACE, is outside every configured write
// root and was writable for that reason.
//
// Same defect as the World SID in the restricted list (#865), with the
// account SID in place of Everyone: a SID already carried by the normal
// token cannot also serve as the restriction on it.
//
// Confining to the capability SIDs alone restores the intersection the
// jail is supposed to be. A configured write root carries BOTH a principal
// ACE, from the principal plan, satisfying the normal token, AND a
// capability ACE, from BuildWindowsACLPlan which setup applies on every
// path, satisfying the restriction. So the principal keeps the tree it
// owns, while anything holding only a principal ACE now fails the
// restricted check.
principalUser, err := principalToken.GetTokenUser()
if err != nil {
fmt.Fprintln(stderr, WindowsSandboxCommandRunnerName+": read sandbox principal SID: "+err.Error())
return 1
}
jailSIDs := windowsPrincipalJailSIDs(tokenSIDs, principalUser.User.Sid.String())
// A strict token restricts READS too, and the account SID that carries the
// read roots was just removed above. Without the read capability the jail
// stops being a write jail and becomes a total one: no read root, no
// executable, nothing. BuildWindowsACLPlan grants this same SID on every
// read root and denies it on every DenyRead path, so the allow-list and the
// restriction stay one decision.
if !writeRestricted {
readSID, err := WindowsReadAllowSID(config.SandboxHome)
if err != nil {
fmt.Fprintln(stderr, WindowsSandboxCommandRunnerName+": resolve sandbox read capability: "+err.Error())
return 1
}
jailSIDs = append(jailSIDs, readSID)
}
jailedToken, err := restrictWindowsTokenForCapabilitySIDs(principalToken, jailSIDs, writeRestricted)
if err != nil {
fmt.Fprintln(stderr, WindowsSandboxCommandRunnerName+": "+err.Error())
return 1
}
defer jailedToken.Close()
// CreateProcessAsUser below is about to be handed a token for a DIFFERENT
// account, which forfeits the own-token exemption the ordinary restricted
// path relies on. Enable what that needs, and refuse with a specific reason
// when this process cannot, rather than letting an unelevated run surface a
// bare "Access is denied" that reads as the command being rejected.
//
// Refusing rather than falling back: an operator who set the opt-in to
// confine reads must not be handed the same-user restricted token while
// believing otherwise.
if err := enableWindowsPrincipalLaunchPrivileges(); err != nil {
fmt.Fprintln(stderr, WindowsSandboxCommandRunnerName+": "+err.Error())
return 1
}
// Stop the child describing the CALLER. Everything identifying the account
// survived from the invoking user's environment, so a principal command
// resolved its per-user state through paths inside a profile it cannot
// open. Applied here, on the principal path only, because this is the first
// point that knows which account the command is about to run as.
// The role has to be the one the token above was minted for, or the child
// is told it is the other account and resolves its per-user state under a
// profile it cannot open.
config.Env = windowsPrincipalIdentityEnvironment(
config.Env,
windowsSandboxUserName(
windowsSandboxPrincipalKey(config),
windowsSandboxRoleForNetwork(config.PermissionProfile.Network.Mode),
),
config.PermissionProfile.Runtime,
)
exitCode, err := runWindowsCommandAsUser(jailedToken, config)
if err != nil {
fmt.Fprintln(stderr, WindowsSandboxCommandRunnerName+": "+err.Error())
return 1
}
return exitCode
}
token, err := createWindowsRestrictedTokenForCapabilitySIDs(tokenSIDs, writeRestricted)
if err != nil {
fmt.Fprintln(stderr, WindowsSandboxCommandRunnerName+": "+err.Error())
@@ -117,12 +238,127 @@ func ensureWindowsUnelevatedSetup(config WindowsSandboxCommandConfig) error {
if err != nil {
return err
}
if marker.contains(applied) {
// THE MARKER ATTESTS TO A PLAN. THE COMMAND CONSUMES AN OBJECT.
//
// The marker fingerprints pathnames and actions, and cleanup is allowed to
// reclaim the deterministic runtime directory that plan was realized on. An
// ordinary later run recreates the same pathname with the caller-private DACL
// and no capability ACE, and the serialized plan is unchanged, so this fast
// path returned before anything looked at the directory. The restricted child
// still carried the capability SID; the new object simply did not grant it, and
// every temp, package-cache and build-cache write failed after launch with a
// bare ACCESS_DENIED and nothing pointing at setup.
//
// This tier owns its plan and needs no elevation, so the answer here is to
// reapply rather than to refuse. Refusing would print advice to run elevated
// setup, which is unnecessary on this tier and unfollowable for a user with no
// Administrator account. The restricted-token tier keeps its refusal, because
// an ordinary user cannot restore principal provisioning.
if marker.contains(applied) && verifyWindowsRuntimeRootCapability(config) == nil {
return nil
}
// THE TIER BOUNDARY, STATED BEFORE ANY MUTATION IS ATTEMPTED.
//
// One plan is consumed by two tiers with different authority. A profile that
// carries DenyRead runs on a strict token, and the strict token applies the
// restricted-SID check to READS, so the read capability has to be granted
// wherever the command reads from -- including the volume root that
// permissionProfileReadRoots seeds. Elevated setup can write that DACL. An
// ordinary user cannot, and the common opener asks for WRITE_DAC on every
// entry, so this tier fails on that one root every time.
//
// Dropping the root ACE instead is not an option: the strict token would then
// fail its own read check for the executable and every ambient read. So the
// tier is refused explicitly, naming the root and the reason, rather than
// discovered as an ACCESS_DENIED after the fact. The real smoke test misses
// this because it substitutes a user-owned temporary directory for the
// production read root.
if refusal := WindowsACLPlanReadGrantRefusal(plan); refusal != "" {
return errors.New("unelevated sandbox setup cannot apply this plan: " + refusal)
}
if _, err := applyWindowsACLPlan(plan); err != nil {
// Refusing to run is right: without these ACEs the write jail does not
// exist, so continuing would run the command believing it is sandboxed
// when it is not. What was wrong was the diagnosis. Every failure got the
// same "the workspace may be on a filesystem you do not own" guess, and
// the suggested remedy was elevated setup, which does not help at all
// when the real problem is one root in the plan that nobody can ACL.
//
// Being precise matters because this failure repeats: the success marker
// is only recorded on success, so the same plan fails identically on
// every later command until the offending root leaves it. A reader who
// cannot tell which root is at fault has no way out of that.
// Every remedy named below is one the reader can actually carry out.
// Both messages used to offer `--sandbox forbid`, which is not an option
// at all: SandboxPreferenceForbid is an internal engine state with no flag
// behind it, so acting on it produced an unknown option and left the reader
// stuck on the failure they had just been told how to clear. Advice that
// does not work costs more than none, since finding that out takes time.
if denied := windowsACLPlanDeniedPath(err); denied != "" {
return fmt.Errorf("apply unelevated workspace ACLs: %w; %s cannot have its permissions changed by this user, "+
"so the sandbox cannot enforce a write boundary there and will not run the command. "+
"That path is one of this workspace's sandbox roots, usually a system directory that arrived via TEMP or TMP. "+
"Check those, or turn the sandbox off in your user config with "+
`"sandbox": {"enabled": false}. `+
"Running `zero sandbox setup` elevated will NOT fix this", err, denied)
}
return fmt.Errorf("apply unelevated workspace ACLs: %w — the workspace may be on a filesystem the current user does not own; "+
"run `zero sandbox setup` from an elevated (Administrator) terminal, or re-run with `--sandbox forbid` to skip OS sandboxing", err)
"run `zero sandbox setup` from an elevated (Administrator) terminal, "+
`or turn the sandbox off in your user config with "sandbox": {"enabled": false}`, err)
}
return recordWindowsUnelevatedAppliedPlan(config.SandboxHome, applied)
}
// windowsACLPlanDeniedPath pulls the target path out of an apply failure that
// was an access denial, and returns "" for anything else.
//
// applyWindowsACLPathGroup already wraps the path into its error, so this reads
// the message rather than threading a typed error through four layers for one
// diagnostic. The string it matches is produced in the same package by
// openWindowsACLTarget, and a test pins the pairing so the two cannot drift
// apart silently.
func windowsACLPlanDeniedPath(err error) string {
if err == nil || !errors.Is(err, os.ErrPermission) {
return ""
}
const marker = "open windows ACL target "
message := err.Error()
start := strings.Index(message, marker)
if start < 0 {
return ""
}
// Colon-SPACE, not colon. The wrapper is "...target %s: %w", and on Windows
// the path itself starts with a drive colon, so splitting on the first colon
// returns "C". A drive colon is always followed by a separator, never a
// space, which makes ": " the only unambiguous boundary here.
rest := message[start+len(marker):]
end := strings.Index(rest, ": ")
if end <= 0 {
return ""
}
return strings.TrimSpace(rest[:end])
}
// windowsPrincipalJailSIDs returns the restricting SIDs for a principal command.
//
// A named function with its own test rather than an inline slice literal,
// because the defect it encodes was invisible: the production composition added
// the account's own SID while the only jail test granted a GROUP, so the
// configuration that shipped was never the configuration under test.
//
// accountSID is taken and DELIBERATELY EXCLUDED rather than simply not passed.
// Naming it here makes the exclusion the function's stated contract instead of an
// omission a later edit could undo without noticing, and it also removes the SID
// should it ever arrive through capabilitySIDs, which is the same route the World
// SID took in #865.
func windowsPrincipalJailSIDs(capabilitySIDs []string, accountSID string) []string {
account := strings.TrimSpace(accountSID)
jail := make([]string, 0, len(capabilitySIDs))
for _, sid := range capabilitySIDs {
if account != "" && strings.EqualFold(strings.TrimSpace(sid), account) {
continue
}
jail = append(jail, sid)
}
return jail
}
@@ -0,0 +1,236 @@
//go:build windows
package sandbox
import (
"errors"
"os"
"path/filepath"
"testing"
"time"
"golang.org/x/sys/windows"
)
// The outer rollback must only delete principals this run created.
//
// Dual-role setup provisions offline then online. If the offline role adopts an
// account that already existed and anything afterwards fails, the outer rollback
// used to delete it anyway, turning a partial re-setup failure into the loss of
// a principal that was working before the run started. Two roles make that the
// common case rather than an unlucky one: the first role usually succeeds, so
// there is nearly always something for a later failure to destroy.
func TestDualRoleSetupRollbackSparesAdoptedPrincipals(t *testing.T) {
for name, testCase := range map[string]struct {
createdByRole map[windowsSandboxRole]bool
wantRemoved []windowsSandboxRole
}{
"offline adopted, online created": {
createdByRole: map[windowsSandboxRole]bool{
windowsSandboxRoleOffline: false,
windowsSandboxRoleOnline: true,
},
// Only the one this run made. Deleting the adopted offline principal
// is the data loss this guards against.
wantRemoved: []windowsSandboxRole{windowsSandboxRoleOnline},
},
"both adopted": {
createdByRole: map[windowsSandboxRole]bool{
windowsSandboxRoleOffline: false,
windowsSandboxRoleOnline: false,
},
wantRemoved: nil,
},
"both created": {
createdByRole: map[windowsSandboxRole]bool{
windowsSandboxRoleOffline: true,
windowsSandboxRoleOnline: true,
},
wantRemoved: []windowsSandboxRole{windowsSandboxRoleOffline, windowsSandboxRoleOnline},
},
} {
t.Run(name, func(t *testing.T) {
var removed []windowsSandboxRole
restoreDualRoleSeams(t, testCase.createdByRole, &removed)
// Fail on the SECOND role, not the first. ACL application happens per
// role inside the loop, so failing the first aborts before the second
// is provisioned at all and the rollback never has more than one
// principal to consider. The case worth testing is the one review
// described: the first role succeeds, the second fails, and the
// question is whether the first gets destroyed on the way out.
// Count GRANT plans, not ACL calls. applyWindowsPrincipalACLs revokes
// this trustee's existing ACEs before applying the new plan, so there
// are two calls per role now. The contract under test is "the second
// ROLE fails"; counting raw calls would fail the first role's grant
// instead and prove something else entirely.
grants := 0
applyWindowsACLPlanFn = func(plan WindowsACLPlan) (func() error, error) {
if len(plan.Entries) > 0 && plan.Entries[0].Action == windowsACLRevoke {
return func() error { return nil }, nil
}
grants++
if grants < 2 {
return func() error { return nil }, nil
}
return nil, errors.New("ACL apply refused")
}
if _, err := setupWindowsSandboxPrincipal(windowsSandboxTestConfig(t)); err == nil {
t.Fatal("setup reported success despite an injected ACL failure")
}
assertRolesEqual(t, removed, testCase.wantRemoved)
})
}
}
// The same contract on the success path: the rollback handed back to the caller
// for a LATER setup step to invoke must be just as reluctant.
func TestDualRoleSetupReturnedRollbackSparesAdoptedPrincipals(t *testing.T) {
var removed []windowsSandboxRole
restoreDualRoleSeams(t, map[windowsSandboxRole]bool{
windowsSandboxRoleOffline: false,
windowsSandboxRoleOnline: true,
}, &removed)
rollback, err := setupWindowsSandboxPrincipal(windowsSandboxTestConfig(t))
if err != nil {
t.Fatalf("setup: %v", err)
}
if len(removed) != 0 {
t.Fatalf("setup removed principals before anything failed: %v", removed)
}
if err := rollback(); err != nil {
t.Fatalf("rollback: %v", err)
}
assertRolesEqual(t, removed, []windowsSandboxRole{windowsSandboxRoleOnline})
}
func restoreDualRoleSeams(t *testing.T, createdByRole map[windowsSandboxRole]bool, removed *[]windowsSandboxRole) {
t.Helper()
prevProvision := provisionWindowsSandboxPrincipalForSetupFn
prevApply := applyWindowsACLPlanFn
prevRemove := removeWindowsSandboxPrincipalForSetupFn
t.Cleanup(func() {
provisionWindowsSandboxPrincipalForSetupFn = prevProvision
applyWindowsACLPlanFn = prevApply
removeWindowsSandboxPrincipalForSetupFn = prevRemove
})
provisionWindowsSandboxPrincipalForSetupFn = func(_ WindowsSandboxCommandConfig, role windowsSandboxRole) (windowsSandboxIdentity, bool, error) {
sid, err := windows.CreateWellKnownSid(windows.WinLocalSystemSid)
if err != nil {
return windowsSandboxIdentity{}, false, err
}
return windowsSandboxIdentity{Username: "zero-sbx-test", SID: sid}, createdByRole[role], nil
}
applyWindowsACLPlanFn = func(WindowsACLPlan) (func() error, error) {
return func() error { return nil }, nil
}
removeWindowsSandboxPrincipalForSetupFn = func(_ WindowsSandboxCommandConfig, role windowsSandboxRole) error {
*removed = append(*removed, role)
return nil
}
}
// windowsSandboxTestConfig hands the production setup path test-owned roots and
// nothing else. The principal and ACL seams intercept the identity work, not the
// filesystem work: setupWindowsSandboxPrincipal materializes runtime candidates
// under the user cache and TEMP, and applyWindowsPrincipalACLs writes ledgers
// below the sandbox home, so the fixed C:\sandboxhome and C:\ws these tests used
// to name meant an ordinary run wrote to the live cache, failed on drive-root
// permissions, or collided with host state. Everything setup touches is
// redirected to t.TempDir, and windowsSandboxTestRootsUntouched proves the
// redirect took. Reported by @gnanam1990.
func windowsSandboxTestConfig(t *testing.T) WindowsSandboxCommandConfig {
t.Helper()
home := filepath.Join(t.TempDir(), "sandboxhome")
workspace := filepath.Join(t.TempDir(), "ws")
if err := os.MkdirAll(workspace, 0o700); err != nil {
t.Fatal(err)
}
cache := t.TempDir()
prevCache := sandboxUserCacheDir
sandboxUserCacheDir = func() (string, error) { return cache, nil }
t.Cleanup(func() { sandboxUserCacheDir = prevCache })
temp := t.TempDir()
t.Setenv("TMP", temp)
t.Setenv("TEMP", temp)
before := windowsFixedTestRootsState()
t.Cleanup(func() { windowsSandboxTestRootsUntouched(t, cache, before) })
return WindowsSandboxCommandConfig{
SandboxHome: home,
CommandCWD: workspace,
WorkspaceRoots: []string{workspace},
PermissionProfile: PermissionProfile{
FileSystem: FileSystemPolicy{
Kind: FileSystemRestricted,
WriteRoots: []WritableRoot{{Root: workspace}},
},
},
}
}
// windowsFixedRootState is what a run may not change about a path outside the
// test-owned roots: whether it exists, and if it does, when its entries last
// changed. A directory's modification time moves whenever something is created
// or removed inside it, which is exactly what setup would do to a home it was
// still writing ledgers into.
type windowsFixedRootState struct {
exists bool
modTime time.Time
}
var windowsFixedTestRoots = []string{`C:\sandboxhome`, `C:\ws`}
func windowsFixedTestRootsState() map[string]windowsFixedRootState {
states := make(map[string]windowsFixedRootState, len(windowsFixedTestRoots))
for _, fixed := range windowsFixedTestRoots {
info, err := os.Stat(fixed)
if err != nil {
states[fixed] = windowsFixedRootState{}
continue
}
states[fixed] = windowsFixedRootState{exists: true, modTime: info.ModTime()}
}
return states
}
// windowsSandboxTestRootsUntouched asserts the production setup path stayed
// inside the test-owned roots. Not "the fixed paths are absent": a box that ran
// the old form of these tests still has C:\sandboxhome from them, which is the
// host state the finding was about, so the assertion is that THIS run neither
// created nor changed them. And the cache the run was redirected to must not be
// the live one, or the redirect proved nothing.
func windowsSandboxTestRootsUntouched(t *testing.T, cache string, before map[string]windowsFixedRootState) {
t.Helper()
after := windowsFixedTestRootsState()
for _, fixed := range windowsFixedTestRoots {
was, now := before[fixed], after[fixed]
switch {
case !was.exists && now.exists:
t.Errorf("setup under test created %s, a path outside the test-owned roots", fixed)
case was.exists && now.exists && !now.modTime.Equal(was.modTime):
t.Errorf("setup under test wrote into %s, a path outside the test-owned roots", fixed)
}
}
if live, err := os.UserCacheDir(); err == nil && live == cache {
t.Fatalf("SETUP INVALID: the redirected cache %s is the live one", cache)
}
}
func assertRolesEqual(t *testing.T, got []windowsSandboxRole, want []windowsSandboxRole) {
t.Helper()
if len(got) != len(want) {
t.Fatalf("removed %v, want %v", got, want)
}
seen := map[windowsSandboxRole]bool{}
for _, role := range got {
seen[role] = true
}
for _, role := range want {
if !seen[role] {
t.Fatalf("removed %v, want %v", got, want)
}
}
}
@@ -0,0 +1,172 @@
//go:build windows
package sandbox
import (
"os"
"os/exec"
"path/filepath"
"testing"
"unsafe"
"golang.org/x/sys/windows"
)
// appliedDenyMask returns the DENY mask an applied DACL carries for sid, read
// back off the object rather than asserted on the plan, because the plan is what
// was wrong.
func appliedDenyMask(t *testing.T, path string, sid string) uint32 {
t.Helper()
handle, _, err := openWindowsACLTarget(path)
if err != nil {
t.Fatalf("open %s: %v", path, err)
}
defer func() { _ = windows.CloseHandle(handle) }()
descriptor, err := windows.GetSecurityInfo(handle, windows.SE_FILE_OBJECT, windows.DACL_SECURITY_INFORMATION)
if err != nil {
t.Fatalf("read the DACL of %s: %v", path, err)
}
dacl, _, err := descriptor.DACL()
if err != nil || dacl == nil {
t.Fatalf("read the DACL of %s: %v", path, err)
}
wanted, err := windows.StringToSid(sid)
if err != nil {
t.Fatalf("parse %q: %v", sid, err)
}
var mask uint32
// Fixed-layout ACE types only; an object ACE puts GUIDs ahead of the trustee
// so SidStart would land mid-structure. Nothing here builds one, and an
// unrecognised type is skipped rather than decoded into a nonsense SID.
for index := uint32(0); index < uint32(dacl.AceCount); index++ {
var ace *windows.ACCESS_ALLOWED_ACE
if err := windows.GetAce(dacl, index, &ace); err != nil {
continue
}
if ace.Header.AceType != windows.ACCESS_DENIED_ACE_TYPE {
continue
}
if !(*windows.SID)(unsafe.Pointer(&ace.SidStart)).Equals(wanted) {
continue
}
mask |= uint32(ace.Mask)
}
return mask
}
// A GUARD ON AN OBJECT THAT DOES NOT EXIST YET IS NOT A GUARD.
//
// The capability planner emitted the deny-delete on .git and the deny-writes on
// .git\config and .git\hooks without Materialize. On a workspace that had no
// .git when setup ran, the first apply pass skipped all three as missing and the
// deferred pass skipped them again, because nothing else in the capability plan
// created them. Setup recorded success anyway.
//
// A later git init then created .git, config and hooks beneath the
// already-granted workspace. They inherit the workspace allow, which carries
// DELETE, with no object-specific deny of their own, so the sandboxed command
// could rename .git aside, recreate it, and get credential.helper and
// core.hooksPath back.
//
// This is the DEFAULT backend, so the weaker of the two planners' rules was the
// one almost every Windows user got. The principal plan was never affected: its
// carveouts are materialized, which both applies them and creates .git as their
// parent so the deferred retry lands the deny-delete.
//
// Read back off the applied object, and driven through the same
// BuildWindowsACLPlan + applyWindowsACLPlan pair both setup tiers use. DACL edits
// on a user-owned directory need no Administrator rights.
func TestCapabilityGitGuardReachesAWorkspaceThatGetsGitLater(t *testing.T) {
workspace := t.TempDir()
gitDir := filepath.Join(workspace, ".git")
// SETUP: no .git at setup time. That is the entire case.
if _, err := os.Stat(gitDir); err == nil {
t.Fatal("SETUP INVALID: .git already exists, so this is the covered case, not the uncovered one")
}
config := WindowsSandboxCommandConfig{
SandboxHome: t.TempDir(),
CommandCWD: workspace,
WorkspaceRoots: []string{workspace},
PermissionProfile: PermissionProfile{
FileSystem: FileSystemPolicy{
Kind: FileSystemRestricted,
WriteRoots: []WritableRoot{{
Root: workspace,
ReadOnlySubpaths: gitMetadataWriteCarveouts(workspace),
ProtectedMetadataNames: sandboxFullyProtectedMetadataNames,
}},
},
},
}
plan, err := BuildWindowsACLPlan(config)
if err != nil {
t.Fatalf("BuildWindowsACLPlan: %v", err)
}
sid, err := windowsCapabilitySIDForWriteRoot(config, workspace)
if err != nil {
t.Fatalf("resolve the workspace capability SID: %v", err)
}
if _, err := applyWindowsACLPlan(plan); err != nil {
t.Skipf("cannot apply an ACL plan here: %v", err)
}
// The workspace grant really landed, so a missing deny below is a missing
// deny and not an apply that did nothing.
if appliedAllowMask(t, workspace, sid) == 0 {
t.Fatal("SETUP INVALID: the workspace carries no allow ACE for the capability SID, so the plan did not apply")
}
// Now git arrives, the way it does for a scaffold or a clone after setup.
if out, err := exec.Command("git", "init", workspace).CombinedOutput(); err != nil {
t.Skipf("git init unavailable here: %v\n%s", err, out)
}
if mask := appliedDenyMask(t, gitDir, sid); mask&uint32(windows.DELETE) == 0 {
t.Fatalf(".git carries no deny-DELETE for the capability SID after git init (mask=%#x); the sandboxed token can rename it aside and recreate it without the config and hooks carveouts", mask)
}
hooks := filepath.Join(gitDir, "hooks")
if _, err := os.Stat(hooks); err == nil {
if mask := appliedDenyMask(t, hooks, sid); mask == 0 {
t.Error(".git\\hooks carries no deny for the capability SID, so core.hooksPath is writable from inside the sandbox")
}
}
}
// appliedAllowMask is the allow-side companion, used only as a setup guard.
func appliedAllowMask(t *testing.T, path string, sid string) uint32 {
t.Helper()
handle, _, err := openWindowsACLTarget(path)
if err != nil {
t.Fatalf("open %s: %v", path, err)
}
defer func() { _ = windows.CloseHandle(handle) }()
descriptor, err := windows.GetSecurityInfo(handle, windows.SE_FILE_OBJECT, windows.DACL_SECURITY_INFORMATION)
if err != nil {
t.Fatalf("read the DACL of %s: %v", path, err)
}
dacl, _, err := descriptor.DACL()
if err != nil || dacl == nil {
t.Fatalf("read the DACL of %s: %v", path, err)
}
wanted, err := windows.StringToSid(sid)
if err != nil {
t.Fatalf("parse %q: %v", sid, err)
}
var mask uint32
for index := uint32(0); index < uint32(dacl.AceCount); index++ {
var ace *windows.ACCESS_ALLOWED_ACE
if err := windows.GetAce(dacl, index, &ace); err != nil {
continue
}
if ace.Header.AceType != windows.ACCESS_ALLOWED_ACE_TYPE {
continue
}
if !(*windows.SID)(unsafe.Pointer(&ace.SidStart)).Equals(wanted) {
continue
}
mask |= uint32(ace.Mask)
}
return mask
}
@@ -0,0 +1,66 @@
//go:build windows
package sandbox
import (
"os"
"os/exec"
"path/filepath"
"testing"
)
// The git control-plane carveouts are two different shapes: .git/hooks is a
// directory, .git/config is a FILE. Materialization has to respect that.
//
// On a fresh workspace neither exists yet, which is precisely the case
// Materialize was added for — so this is the common path, not a corner. Creating
// .git/config as a directory does not just mis-ACL it: it makes the workspace
// permanently unusable, because git refuses to initialise over a directory
// where its config file belongs.
func TestPrincipalACLPlanMaterializesGitConfigAsFile(t *testing.T) {
workspace := t.TempDir()
plan, err := buildWindowsPrincipalACLPlan(windowsPrincipalACLInput{
// Guests, deliberately: the deny-write ACE must land on the sandbox
// principal, not on whoever runs the test. With Everyone (S-1-1-0) the
// ACE denies the test process too and `git init` fails with "Permission
// denied" for a reason that has nothing to do with the shape bug.
PrincipalSID: "S-1-5-32-546",
WriteRoots: []WritableRoot{{
Root: workspace,
ReadOnlySubpaths: gitMetadataWriteCarveouts(workspace),
}},
})
if err != nil {
t.Fatalf("buildWindowsPrincipalACLPlan: %v", err)
}
rollback, err := applyWindowsACLPlan(plan)
if err != nil {
t.Fatalf("applyWindowsACLPlan: %v", err)
}
t.Cleanup(func() {
if rollback != nil {
_ = rollback()
}
})
configPath := filepath.Join(workspace, ".git", "config")
if info, err := os.Stat(configPath); err == nil && info.IsDir() {
t.Errorf(".git/config was materialized as a directory; git requires a file")
}
hooksPath := filepath.Join(workspace, ".git", "hooks")
if info, err := os.Stat(hooksPath); err == nil && !info.IsDir() {
t.Errorf(".git/hooks was materialized as a file; git requires a directory")
}
// The failure users would actually hit.
if _, err := exec.LookPath("git"); err != nil {
t.Skip("git not on PATH; shape assertions above still ran")
}
cmd := exec.Command("git", "init")
cmd.Dir = workspace
if out, err := cmd.CombinedOutput(); err != nil {
t.Errorf("git init failed on a workspace after sandbox setup: %v\n%s", err, out)
}
}
@@ -0,0 +1,145 @@
//go:build windows
package sandbox
import (
"os"
"path/filepath"
"strconv"
"strings"
"testing"
"golang.org/x/sys/windows"
)
// windowsPathDeniesDelete reports whether the object's real DACL carries a deny
// ACE covering DELETE for the given SID.
//
// The plan-shape tests assert what the planner emits. This reads what actually
// landed on disk, which is the gap that let the guard go missing: the plan was
// right the whole time and the apply silently dropped it.
func windowsPathDeniesDelete(t *testing.T, path, sid string) bool {
t.Helper()
handle, _, err := openWindowsACLTarget(path)
if err != nil {
t.Fatalf("open %s: %v", path, err)
}
defer func() { _ = windows.CloseHandle(handle) }()
descriptor, err := windows.GetSecurityInfo(handle, windows.SE_FILE_OBJECT, windows.DACL_SECURITY_INFORMATION)
if err != nil {
t.Fatalf("read DACL for %s: %v", path, err)
}
// SDDL rather than walking the ACE buffer by hand: this x/sys does not export
// an ACE enumerator, and unsafe pointer arithmetic in a test that exists to
// catch a security regression is its own hazard.
//
// An ACE renders as (type;flags;rights;guid;inherit_guid;sid), so the deny
// entries are the ones whose type field is D. Rights come back as SDDL
// abbreviations when they fit and as a hex mask when they do not, so both are
// accepted; SD is the abbreviation for DELETE.
for _, ace := range strings.Split(descriptor.String(), "(") {
fields := strings.Split(strings.TrimSuffix(strings.TrimSpace(ace), ")"), ";")
if len(fields) != 6 || fields[0] != "D" || !strings.EqualFold(fields[5], sid) {
continue
}
rights := fields[2]
if strings.Contains(rights, "SD") {
return true
}
if mask, err := strconv.ParseUint(strings.TrimPrefix(strings.ToLower(rights), "0x"), 16, 32); err == nil {
if uint32(mask)&uint32(windows.DELETE) != 0 {
return true
}
}
}
return false
}
// THE GUARD MUST REACH DISK ON A WORKSPACE THAT HAD NO .git.
//
// This is the case the whole plan is built around and it was the one case where
// the guard was absent. .git deliberately carries no Materialize, because an
// empty .git breaks `git init`. Groups are applied in ascending path order, so
// the .git group ran while .git did not yet exist, was skipped as a
// non-materializing missing target, and nothing revisited it once the
// .git\config carveout created .git as its parent chain moments later.
//
// Four tests already covered the deny-delete mask and the plan emitting it.
// None of them applied the plan and looked at the object, which is exactly why
// a green suite said nothing.
func TestGitRenameGuardReachesDiskOnAWorkspaceWithoutGit(t *testing.T) {
const principal = testPrincipalSID // Unaliased, so it renders literally in SDDL.
workspace := t.TempDir()
gitDir := filepath.Join(workspace, ".git")
if _, err := os.Stat(gitDir); err == nil {
t.Fatal("the workspace already has .git, so this proves nothing")
}
plan, err := buildWindowsPrincipalACLPlan(windowsPrincipalACLInput{
PrincipalSID: principal,
WriteRoots: []WritableRoot{{
Root: workspace,
ProtectedMetadataNames: sandboxFullyProtectedMetadataNames,
ReadOnlySubpaths: gitMetadataWriteCarveouts(workspace),
}},
})
if err != nil {
t.Fatalf("buildWindowsPrincipalACLPlan: %v", err)
}
rollback, err := applyWindowsACLPlan(plan)
if err != nil {
t.Fatalf("applyWindowsACLPlan: %v", err)
}
t.Cleanup(func() {
if rollback != nil {
_ = rollback()
}
})
// The carveouts create .git on the way to .git\config.
if _, err := os.Stat(gitDir); err != nil {
t.Fatalf(".git was never created by the carveout materialization: %v", err)
}
if !windowsPathDeniesDelete(t, gitDir, principal) {
t.Fatal("no deny-delete ACE on .git after applying the plan: the principal can rename it aside and recreate it without the config and hooks carveouts")
}
}
// The same guard on a workspace that already had .git must keep working. This
// case was already correct, and it is kept so a fix aimed at the fresh
// workspace cannot quietly trade one for the other.
func TestGitRenameGuardStillReachesDiskWhenGitAlreadyExists(t *testing.T) {
const principal = testPrincipalSID
workspace := t.TempDir()
gitDir := filepath.Join(workspace, ".git")
if err := os.Mkdir(gitDir, 0o700); err != nil {
t.Fatalf("seed .git: %v", err)
}
plan, err := buildWindowsPrincipalACLPlan(windowsPrincipalACLInput{
PrincipalSID: principal,
WriteRoots: []WritableRoot{{
Root: workspace,
ProtectedMetadataNames: sandboxFullyProtectedMetadataNames,
ReadOnlySubpaths: gitMetadataWriteCarveouts(workspace),
}},
})
if err != nil {
t.Fatalf("buildWindowsPrincipalACLPlan: %v", err)
}
rollback, err := applyWindowsACLPlan(plan)
if err != nil {
t.Fatalf("applyWindowsACLPlan: %v", err)
}
t.Cleanup(func() {
if rollback != nil {
_ = rollback()
}
})
if !windowsPathDeniesDelete(t, gitDir, principal) {
t.Fatal("no deny-delete ACE on a .git that already existed")
}
}
@@ -0,0 +1,98 @@
package sandbox
import (
"path/filepath"
"testing"
)
// A sandbox principal must not be able to REPLACE .git.
//
// The write-denied carveouts are attached to .git/config and .git/hooks as
// objects. Rename .git aside, recreate it, and those objects are gone: the fresh
// config and hooks inherit the workspace allow with no deny of their own, which
// hands back credential.helper and core.hooksPath, and with them arbitrary code
// execution on the next git command.
//
// .git cannot join sandboxFullyProtectedMetadataNames to fix this, because that
// list emits DenyWrite, whose mask includes FILE_GENERIC_WRITE. Git has to write
// index, objects and refs. So the directory needs DELETE denied on itself while
// staying writable underneath.
func TestThePrincipalCannotRenameTheGitDirectory(t *testing.T) {
root := filepath.FromSlash("/ws/repo")
plan, err := buildWindowsPrincipalACLPlan(windowsPrincipalACLInput{
PrincipalSID: "S-1-5-21-1-2-3-1001",
WriteRoots: []WritableRoot{{
Root: root,
ProtectedMetadataNames: sandboxFullyProtectedMetadataNames,
ReadOnlySubpaths: gitMetadataWriteCarveouts(root),
}},
})
if err != nil {
t.Fatalf("buildWindowsPrincipalACLPlan: %v", err)
}
// The plan normalizes every write root before it names an ACE, so the
// expected path has to be normalized too or this compares two spellings of
// the same directory. Hardcoding a drive letter instead would pass on
// Windows and fail everywhere else, since the builder is portable code.
gitDir := filepath.Join(normalizeProfilePath(root), ".git")
var denyDelete *WindowsACLEntry
for index := range plan.Entries {
if plan.Entries[index].Action == WindowsACLDenyDelete && plan.Entries[index].Path == gitDir {
denyDelete = &plan.Entries[index]
break
}
}
if denyDelete == nil {
t.Fatalf("no deny-delete entry for %s, so the principal can rename .git and recreate it without the carveouts:\n%#v", gitDir, plan.Entries)
}
if denyDelete.Capability != "S-1-5-21-1-2-3-1001" {
t.Errorf("deny-delete names %q, want the principal SID", denyDelete.Capability)
}
}
// The guard must not become a write ban. Git writes constantly inside .git, so a
// deny that reached the children would break every commit rather than just the
// rename. It also must not be materialized into existence: .git is git's to
// create, and an empty .git directory made by setup breaks `git init`.
func TestTheGitRenameGuardDoesNotBlockGitsOwnWrites(t *testing.T) {
root := filepath.FromSlash("/ws/repo")
plan, err := buildWindowsPrincipalACLPlan(windowsPrincipalACLInput{
PrincipalSID: "S-1-5-21-1-2-3-1001",
WriteRoots: []WritableRoot{{
Root: root,
ProtectedMetadataNames: sandboxFullyProtectedMetadataNames,
ReadOnlySubpaths: gitMetadataWriteCarveouts(root),
}},
})
if err != nil {
t.Fatalf("buildWindowsPrincipalACLPlan: %v", err)
}
gitDir := filepath.Join(normalizeProfilePath(root), ".git")
for _, entry := range plan.Entries {
if entry.Path != gitDir {
continue
}
if entry.Action == WindowsACLDenyWrite {
t.Errorf("deny-write on %s would stop git writing index/objects/refs", gitDir)
}
if entry.Action == WindowsACLDenyDelete && entry.Materialize {
t.Errorf("the rename guard materializes %s; git must create it, an empty .git breaks git init", gitDir)
}
}
// The existing carveouts must survive unchanged.
for _, want := range []string{filepath.Join(gitDir, "config"), filepath.Join(gitDir, "hooks")} {
found := false
for _, entry := range plan.Entries {
if entry.Action == WindowsACLDenyWrite && entry.Path == want {
found = true
break
}
}
if !found {
t.Errorf("the write-deny carveout for %s disappeared", want)
}
}
}
@@ -0,0 +1,81 @@
//go:build windows
package sandbox
import (
"testing"
"golang.org/x/sys/windows"
)
// The mask is the whole point of the action, so it is asserted bit by bit.
//
// Renaming a directory needs DELETE on the directory itself, so denying DELETE
// is what stops .git being replaced. Everything else in the mask is there to
// stop the principal removing the guard: WRITE_DAC would let it rewrite the
// DACL, WRITE_OWNER would let it take ownership and then rewrite the DACL.
//
// What must NOT be in it matters just as much. FILE_GENERIC_WRITE would stop git
// writing index, objects and refs. FILE_DELETE_CHILD would stop git deleting its
// own lock files and refs. Either one turns a rename guard into a broken repo.
func TestDenyDeleteMaskStopsRenameWithoutStoppingGit(t *testing.T) {
mode, mask, err := windowsACLAccess(WindowsACLDenyDelete)
if err != nil {
t.Fatalf("windowsACLAccess(deny-delete): %v", err)
}
if mode != windows.DENY_ACCESS {
t.Fatalf("access mode = %v, want DENY_ACCESS", mode)
}
for _, required := range []struct {
name string
bit windows.ACCESS_MASK
}{
{"DELETE", windows.DELETE},
{"WRITE_DAC", windows.WRITE_DAC},
{"WRITE_OWNER", windows.WRITE_OWNER},
} {
if mask&required.bit == 0 {
t.Errorf("mask %#x is missing %s, so the guard can be removed or bypassed", mask, required.name)
}
}
for _, forbidden := range []struct {
name string
bit windows.ACCESS_MASK
breaks string
}{
{"FILE_GENERIC_WRITE", windows.FILE_GENERIC_WRITE, "git writing index/objects/refs"},
{"FILE_DELETE_CHILD", windowsFileDeleteChild, "git deleting its own lock files and refs"},
} {
if mask&forbidden.bit != 0 {
t.Errorf("mask %#x includes %s, which breaks %s", mask, forbidden.name, forbidden.breaks)
}
}
}
// Inheritance is the other half. An inherited deny would reach every file inside
// .git and stop git deleting anything at all, so this ACE has to apply to the
// directory object alone while the other actions keep inheriting as before.
func TestDenyDeleteDoesNotInheritWhileOtherActionsStillDo(t *testing.T) {
entries := []WindowsACLEntry{
{Action: WindowsACLDenyDelete, Path: `C:\work\repo\.git`, Capability: "S-1-5-32-9999"},
{Action: WindowsACLDenyWrite, Path: `C:\work\repo\.zero`, Capability: "S-1-5-32-9999"},
{Action: WindowsACLAllowWrite, Path: `C:\work\repo`, Capability: "S-1-5-32-9999"},
}
_, access, err := prepareWindowsACLPathGroupEntries(entries, true, nil)
if err != nil {
t.Fatalf("prepareWindowsACLPathGroupEntries: %v", err)
}
if len(access) != len(entries) {
t.Fatalf("got %d access entries, want %d", len(access), len(entries))
}
if access[0].Inheritance != windows.NO_INHERITANCE {
t.Errorf("deny-delete inheritance = %#x, want NO_INHERITANCE; an inherited deny would stop git deleting inside .git", access[0].Inheritance)
}
for index, entry := range entries[1:] {
if got := access[index+1].Inheritance; got != windows.SUB_CONTAINERS_AND_OBJECTS_INHERIT {
t.Errorf("%s inheritance = %#x, want the directory default to be unchanged", entry.Action, got)
}
}
}
@@ -0,0 +1,86 @@
//go:build windows
package sandbox
import (
"errors"
"strings"
"testing"
)
// A NAME IS NOT PROOF OF PROVENANCE, for the USERS group specifically.
//
// ensureWindowsLocalGroup covers both managed groups, and the sibling test in
// windows_offline_group_ownership_windows_test.go pins the offline one. This
// pins ZeroSandboxUsers, which is the group anandh8x reported: it holds every
// sandbox principal, so adopting a same-named group created by an installer or
// by policy would hand the principal whatever that group already grants.
//
// Driven through the seams so it needs no Administrator and leaves no real local
// group on the machine running the suite.
func TestAdoptingAForeignUsersGroupIsRefused(t *testing.T) {
for _, status := range []uintptr{nerrGroupExists, errorAliasExists} {
prevAdd, prevOwned := addWindowsLocalGroupFn, windowsLocalGroupOwnedByZeroFn
t.Cleanup(func() { addWindowsLocalGroupFn, windowsLocalGroupOwnedByZeroFn = prevAdd, prevOwned })
addWindowsLocalGroupFn = func(string, string) (uintptr, error) { return status, nil }
windowsLocalGroupOwnedByZeroFn = func(string, string) (bool, error) { return false, nil }
err := ensureWindowsSandboxGroup()
if err == nil {
t.Fatalf("status %d adopted a group Zero did not create, so the principal inherits whatever it already grants", status)
}
if !strings.Contains(err.Error(), windowsSandboxGroupName) {
t.Errorf("the refusal must name the group in the way, got %q", err)
}
}
}
// Our own group is still adopted, or re-running setup would fail on the group it
// created a moment ago and provisioning would never converge.
func TestAdoptingOurOwnUsersGroupSucceeds(t *testing.T) {
prevAdd, prevOwned := addWindowsLocalGroupFn, windowsLocalGroupOwnedByZeroFn
t.Cleanup(func() { addWindowsLocalGroupFn, windowsLocalGroupOwnedByZeroFn = prevAdd, prevOwned })
addWindowsLocalGroupFn = func(string, string) (uintptr, error) { return nerrGroupExists, nil }
windowsLocalGroupOwnedByZeroFn = func(name, comment string) (bool, error) {
if name != windowsSandboxGroupName || comment != windowsSandboxGroupComment {
t.Errorf("ownership probed for %q/%q, want the users group", name, comment)
}
return true, nil
}
if err := ensureWindowsSandboxGroup(); err != nil {
t.Errorf("refused a group carrying Zero's own comment: %v", err)
}
}
// A freshly created group is ours by construction, so no ownership probe runs.
func TestCreatingTheUsersGroupDoesNotProbeOwnership(t *testing.T) {
prevAdd, prevOwned := addWindowsLocalGroupFn, windowsLocalGroupOwnedByZeroFn
t.Cleanup(func() { addWindowsLocalGroupFn, windowsLocalGroupOwnedByZeroFn = prevAdd, prevOwned })
probed := false
addWindowsLocalGroupFn = func(string, string) (uintptr, error) { return nerrSuccess, nil }
windowsLocalGroupOwnedByZeroFn = func(string, string) (bool, error) { probed = true; return false, nil }
if err := ensureWindowsSandboxGroup(); err != nil {
t.Fatalf("a successful create was rejected: %v", err)
}
if probed {
t.Error("ownership was probed for a group we had just created ourselves")
}
}
// A failed ownership probe is not read as "ours" and not as "not ours" either.
func TestAnUnreadableUsersGroupIsNotGuessedEitherWay(t *testing.T) {
prevAdd, prevOwned := addWindowsLocalGroupFn, windowsLocalGroupOwnedByZeroFn
t.Cleanup(func() { addWindowsLocalGroupFn, windowsLocalGroupOwnedByZeroFn = prevAdd, prevOwned })
sentinel := errors.New("NetLocalGroupGetInfo: status 5")
addWindowsLocalGroupFn = func(string, string) (uintptr, error) { return nerrGroupExists, nil }
windowsLocalGroupOwnedByZeroFn = func(string, string) (bool, error) { return false, sentinel }
if err := ensureWindowsSandboxGroup(); !errors.Is(err, sentinel) {
t.Fatalf("a failed ownership probe was swallowed, got %v", err)
}
}
+231
View File
@@ -0,0 +1,231 @@
package sandbox
// ACLs for a sandbox principal.
//
// The capability-SID model this sits beside starts from "the caller can already
// read everything" and narrows writes, because the sandboxed child runs as the
// caller. A principal inverts that: a separate local account has no access to
// the caller's profile at all, so the interesting direction is what to GRANT.
//
// That inversion is the point. Credential stores under the user's profile are
// unreachable because the principal is a different account, not because a deny
// rule enumerated them, which is what makes this able to close #662 and #675 on
// Windows where a deny-read ACE against the caller's own SID never could. Deny
// rules stay useful only for objects that are readable by everyone.
//
// Grants are explicit and narrow: the workspace and any extra write roots get
// read+write, declared read-only roots get read, and the protected metadata
// carve-outs the profile already defines stay denied so .git internals and
// .zero/.agents cannot be rewritten from inside the sandbox.
import (
"errors"
"fmt"
"path/filepath"
)
// WindowsACLAllowRead grants read and execute without write. It exists for the
// principal model, where a read root must be granted rather than assumed.
const WindowsACLAllowRead WindowsACLAction = "allow-read"
// windowsPrincipalACLInput is everything needed to describe a principal's
// access. It is deliberately a plain struct rather than the full command config
// so the plan can be built and tested without a live sandbox.
type windowsPrincipalACLInput struct {
// PrincipalSID is the string SID of the sandbox account every ACE names.
PrincipalSID string
// WriteRoots receive read+write+execute. The workspace lives here.
WriteRoots []WritableRoot
// ReadRoots receive read+execute only.
ReadRoots []string
// DenyRead covers objects a principal could otherwise reach because they are
// world-readable; per-user secrets need no entry.
DenyRead []string
// DenyWrite carries the policy's own deny-write paths. The capability plan
// has always emitted these; the principal plan denied write only on
// protected metadata and read-only subpaths inside write roots, so a policy
// deny sitting anywhere else was simply not enforced once the runner used a
// principal token, and a shell child could write where the restricted-token
// backend would have blocked it.
DenyWrite []string
}
// buildWindowsPrincipalACLPlan turns a principal's access into ACL entries.
//
// Ordering matters at apply time: deny entries are emitted before allows so a
// carve-out inside a granted root survives, which mirrors how Windows evaluates
// an explicit DACL (deny ACEs first).
func buildWindowsPrincipalACLPlan(input windowsPrincipalACLInput) (WindowsACLPlan, error) {
if input.PrincipalSID == "" {
return WindowsACLPlan{}, errors.New("windows principal ACL plan requires a principal SID")
}
if len(input.WriteRoots) == 0 && len(input.ReadRoots) == 0 {
return WindowsACLPlan{}, errors.New("windows principal ACL plan requires at least one root")
}
entries := make([]WindowsACLEntry, 0, len(input.WriteRoots)*2+len(input.ReadRoots)+len(input.DenyRead))
// Deny first. A deny ACE inside a write root (protected metadata, git
// internals) has to win over the grant that follows it.
// Materialized, matching the capability plan. applyWindowsACLPlan skips a
// target that does not exist, so without this a deny-read path created after
// setup ran never got an ACE at all and the principal could read it. The
// deny has to be in place before the object is.
for _, path := range normalizeProfilePaths(input.DenyRead) {
entries = append(entries, WindowsACLEntry{
Action: WindowsACLDenyRead,
Path: path,
Capability: input.PrincipalSID,
Materialize: true,
})
}
for _, path := range normalizeProfilePaths(input.DenyWrite) {
entries = append(entries, WindowsACLEntry{
Action: WindowsACLDenyWrite,
Path: path,
Capability: input.PrincipalSID,
Materialize: true,
})
}
for _, root := range input.WriteRoots {
// Normalized the same way as read and deny paths: a write root may arrive
// with "~" or as a relative path, and an ACE has to name the same absolute,
// symlink-resolved object the deny entries do or the two disagree.
cleaned := normalizeProfilePath(root.Root)
if cleaned == "" {
return WindowsACLPlan{}, fmt.Errorf("windows principal ACL plan: unusable write root %q", root.Root)
}
// Materialized, like the metadata and policy denies below and above.
//
// These are the git control-plane carveouts (.git/config, .git/hooks). On a
// workspace where git has not run yet they do not exist at setup time, and
// applyWindowsACLPlan skips a target that is absent, so the ACEs were never
// written. Once git created those paths the principal still held inherited
// write access to the workspace and could install a hook or rewrite
// credential.helper. The capability plan gets away without this because its
// child runs as the caller; a separate principal account does not.
// Which carveouts are files rather than directories comes from the same
// spec list the profile built ReadOnlySubpaths from, so a new carveout
// cannot be added without its shape coming along.
for _, subpath := range normalizeProfilePaths(root.ReadOnlySubpaths) {
entries = append(entries, WindowsACLEntry{
Action: WindowsACLDenyWrite,
Path: subpath,
Capability: input.PrincipalSID,
Materialize: true,
MaterializeFile: gitMetadataCarveoutIsFile(subpath),
})
}
for _, name := range root.ProtectedMetadataNames {
// These are documented as NAMES, and the join below is what makes that
// documentation load-bearing rather than descriptive: ".." or a
// separator would place this deny ACE, and the directory it
// materializes, outside the write root entirely. Today every caller
// passes a package constant, so this is unreachable; it is here so that
// stays true when a future caller sources these from config.
if err := validateWindowsACLComponent(name); err != nil {
return WindowsACLPlan{}, fmt.Errorf("windows principal ACL plan: protected metadata name: %w", err)
}
entries = append(entries, WindowsACLEntry{
Action: WindowsACLDenyWrite,
Path: filepath.Join(cleaned, name),
Capability: input.PrincipalSID,
Materialize: true,
})
}
// .git gets DELETE denied on the directory itself, because the carveouts
// that protect it are attached to .git/config and .git/hooks as OBJECTS.
// Rename .git aside and recreate it and those objects are gone, so the
// fresh config and hooks inherit the workspace allow with no deny of their
// own, handing back credential.helper and core.hooksPath.
//
// Not DenyWrite (git writes index, objects and refs), not materialized
// (git creates .git, and an empty one breaks git init), and not inherited,
// so everything underneath stays writable.
entries = append(entries, WindowsACLEntry{
Action: WindowsACLDenyDelete,
Path: windowsRenameProtectedObject(cleaned),
Capability: input.PrincipalSID,
})
}
// Then the grants the principal cannot work without.
for _, root := range input.WriteRoots {
cleaned := normalizeProfilePath(root.Root)
if cleaned == "" {
continue
}
entries = append(entries, WindowsACLEntry{
Action: WindowsACLAllowWrite,
Path: cleaned,
Capability: input.PrincipalSID,
})
}
for _, path := range normalizeProfilePaths(input.ReadRoots) {
// NEVER grant at a volume root.
//
// permissionProfileReadRoots seeds its list with profileRootPath(), which
// is the separator alone, because the workspace-write posture is
// read-all/write-jail. That is harmless for the capability backend, whose
// child runs as the CALLER and therefore reads what the caller could read
// anyway. It is not harmless here: a principal is a separate local
// account, so this loop turns that synthetic entry into a real,
// persistent, inheritable allow-read ACE for that account at the root of
// the current drive, reaching every directory that does not block
// inheritance.
//
// Dropping it does not take away the reads the principal needs to run
// commands. NetUserAdd with USER_PRIV_USER puts the account in the
// built-in Users group (see usrPrivUser in windows_identity_windows.go),
// and the machine's own ACLs already grant Users read on the system and
// program directories. What the grant added on top was read access to the
// places Users are deliberately kept out of, which is the opposite of what
// a sandbox is for.
//
// Note this inherits rather than asserts: nothing here checks that those
// default ACLs are actually in place, so a hardened image that strips
// Users read would need an explicit bounded read set instead.
if isWindowsVolumeRoot(path) {
continue
}
entries = append(entries, WindowsACLEntry{
Action: WindowsACLAllowRead,
Path: path,
Capability: input.PrincipalSID,
})
}
return WindowsACLPlan{Entries: dedupeWindowsACLEntries(entries)}, nil
}
// windowsPrincipalRevokePlan returns the entries whose ACEs should be removed
// when a principal is retired. Revocation is by TRUSTEE rather than by path:
// every ACE naming this principal is dropped, so cleanup does not depend on
// remembering which paths were granted, and a grant added by an older version
// is still removed.
//
// This is the removal path the capability-SID model never had, where a synthetic
// SID left ACEs behind on the user's tree with nothing to match them against.
func windowsPrincipalRevokePlan(principalSID string, paths []string) (WindowsACLPlan, error) {
if principalSID == "" {
return WindowsACLPlan{}, errors.New("windows principal revoke plan requires a principal SID")
}
cleaned := normalizeProfilePaths(paths)
entries := make([]WindowsACLEntry, 0, len(cleaned))
for _, path := range cleaned {
entries = append(entries, WindowsACLEntry{
Action: windowsACLRevoke,
Path: path,
Capability: principalSID,
})
}
return WindowsACLPlan{Entries: entries}, nil
}
// windowsACLRevoke removes every ACE naming the trustee on a path, whatever
// access it granted or denied.
const windowsACLRevoke WindowsACLAction = "revoke"
// windowsACLPlanPaths lives in windows_identity_runtime_windows.go, beside its
// only callers. It was here, in the portable file, which made it dead code on
// every non-Windows build and failed the static analysis gate.
@@ -0,0 +1,275 @@
package sandbox
import (
"path/filepath"
"strings"
"testing"
)
const testPrincipalSID = "S-1-5-21-1111111111-2222222222-3333333333-1005"
func testPrincipalInput() windowsPrincipalACLInput {
return windowsPrincipalACLInput{
PrincipalSID: testPrincipalSID,
WriteRoots: []WritableRoot{{
Root: filepath.FromSlash("/ws/project"),
ReadOnlySubpaths: []string{filepath.FromSlash("/ws/project/.git/config")},
ProtectedMetadataNames: []string{".zero", ".agents"},
}},
ReadRoots: []string{filepath.FromSlash("/usr/lib")},
DenyRead: []string{filepath.FromSlash("/shared/secrets")},
}
}
// Windows evaluates an explicit DACL deny-before-allow, so a carve-out inside a
// granted root only survives if its deny ACE is written first. If the grant on
// the workspace landed before the deny on .zero, the protected metadata would be
// writable from inside the sandbox.
func TestPrincipalACLPlanEmitsDeniesBeforeAllows(t *testing.T) {
plan, err := buildWindowsPrincipalACLPlan(testPrincipalInput())
if err != nil {
t.Fatalf("build: %v", err)
}
lastDeny, firstAllow := -1, -1
for index, entry := range plan.Entries {
switch entry.Action {
case WindowsACLDenyRead, WindowsACLDenyWrite:
lastDeny = index
case WindowsACLAllowWrite, WindowsACLAllowRead:
if firstAllow == -1 {
firstAllow = index
}
}
}
if firstAllow == -1 || lastDeny == -1 {
t.Fatalf("plan is missing a deny or an allow: %+v", plan.Entries)
}
if lastDeny > firstAllow {
t.Fatalf("deny at %d comes after allow at %d; carve-outs would be overridden", lastDeny, firstAllow)
}
}
// Every ACE must name the sandbox principal. An entry with any other trustee
// would change access for a real user.
func TestPrincipalACLPlanNamesOnlyThePrincipal(t *testing.T) {
plan, err := buildWindowsPrincipalACLPlan(testPrincipalInput())
if err != nil {
t.Fatalf("build: %v", err)
}
for _, entry := range plan.Entries {
if entry.Capability != testPrincipalSID {
t.Fatalf("entry %+v names %q, want the principal SID", entry, entry.Capability)
}
}
}
// A principal is a separate account with no inherent access, so a write root
// must be granted read+write and a read root granted read. Without the grant the
// sandbox cannot open its own workspace.
func TestPrincipalACLPlanGrantsRoots(t *testing.T) {
plan, err := buildWindowsPrincipalACLPlan(testPrincipalInput())
if err != nil {
t.Fatalf("build: %v", err)
}
var grantedWrite, grantedRead bool
for _, entry := range plan.Entries {
if entry.Action == WindowsACLAllowWrite && entry.Path == normalizeProfilePath(filepath.FromSlash("/ws/project")) {
grantedWrite = true
}
if entry.Action == WindowsACLAllowRead && entry.Path == normalizeProfilePath(filepath.FromSlash("/usr/lib")) {
grantedRead = true
}
}
if !grantedWrite {
t.Fatal("write root was not granted; the sandbox could not write its workspace")
}
if !grantedRead {
t.Fatal("read root was not granted; the sandbox could not read it")
}
}
// Protected metadata is denied write and marked Materialize so the ACE is
// created even when the directory does not exist yet, closing the window where
// a sandboxed command creates .zero before the deny lands.
func TestPrincipalACLPlanProtectsMetadata(t *testing.T) {
plan, err := buildWindowsPrincipalACLPlan(testPrincipalInput())
if err != nil {
t.Fatalf("build: %v", err)
}
found := map[string]WindowsACLEntry{}
for _, entry := range plan.Entries {
found[entry.Path] = entry
}
for _, name := range []string{".zero", ".agents"} {
path := filepath.Join(normalizeProfilePath(filepath.FromSlash("/ws/project")), name)
entry, ok := found[path]
if !ok {
t.Fatalf("no entry protecting %s", path)
}
if entry.Action != WindowsACLDenyWrite {
t.Fatalf("%s has action %q, want deny-write", path, entry.Action)
}
if !entry.Materialize {
t.Fatalf("%s must be materialized so the deny exists before the directory does", path)
}
}
}
// A missing principal SID must be a hard error: an empty trustee would either
// fail at apply time or, worse, be interpreted as some other account.
func TestPrincipalACLPlanRequiresSID(t *testing.T) {
input := testPrincipalInput()
input.PrincipalSID = ""
if _, err := buildWindowsPrincipalACLPlan(input); err == nil {
t.Fatal("an empty principal SID must be rejected")
}
}
// A plan with no roots at all is a caller mistake rather than a valid empty
// grant, since the resulting sandbox could not run anything.
func TestPrincipalACLPlanRequiresRoots(t *testing.T) {
input := windowsPrincipalACLInput{PrincipalSID: testPrincipalSID}
if _, err := buildWindowsPrincipalACLPlan(input); err == nil {
t.Fatal("a plan with no roots must be rejected")
}
}
// Revocation is keyed to the trustee, so retiring a principal removes every ACE
// naming it without having to remember what was granted. This is the cleanup
// path the capability-SID model lacks.
func TestPrincipalRevokePlanTargetsTrustee(t *testing.T) {
paths := []string{filepath.FromSlash("/ws/project"), filepath.FromSlash("/usr/lib")}
plan, err := windowsPrincipalRevokePlan(testPrincipalSID, paths)
if err != nil {
t.Fatalf("revoke plan: %v", err)
}
if len(plan.Entries) != len(paths) {
t.Fatalf("got %d entries, want %d", len(plan.Entries), len(paths))
}
for _, entry := range plan.Entries {
if entry.Action != windowsACLRevoke {
t.Fatalf("entry %+v is not a revoke", entry)
}
if entry.Capability != testPrincipalSID {
t.Fatalf("revoke names %q, want the principal", entry.Capability)
}
}
}
func TestPrincipalRevokePlanRequiresSID(t *testing.T) {
if _, err := windowsPrincipalRevokePlan("", []string{"/ws"}); err == nil {
t.Fatal("revoking without a principal SID must be rejected")
}
}
// The action strings end up in a serialized plan consumed by the elevated
// helper, so they must stay stable and distinct from the existing actions.
func TestPrincipalACLActionsAreDistinct(t *testing.T) {
actions := []WindowsACLAction{
WindowsACLAllowWrite, WindowsACLAllowRead,
WindowsACLDenyRead, WindowsACLDenyWrite, windowsACLRevoke,
}
seen := map[WindowsACLAction]bool{}
for _, action := range actions {
if strings.TrimSpace(string(action)) == "" {
t.Fatal("an action string is empty")
}
if seen[action] {
t.Fatalf("duplicate action %q", action)
}
seen[action] = true
}
}
// ProtectedMetadataNames is joined onto the write root to place a deny ACE and to
// materialize the directory it names. A value that is not a single component
// therefore puts both OUTSIDE the workspace: ".." walks up out of it, and a
// separator reaches through whatever sits in between. Every caller passes a
// package constant today, so this is the guard that keeps it true if one ever
// sources these from config.
func TestPrincipalACLPlanRefusesProtectedNamesThatEscapeTheWriteRoot(t *testing.T) {
root := filepath.FromSlash("/ws/project")
for _, name := range []string{"..", ".", "", `..\..\Windows\System32`, "nested/child", `nested\child`, "C:", "stream:name"} {
t.Run(name, func(t *testing.T) {
input := testPrincipalInput()
input.WriteRoots = []WritableRoot{{
Root: root,
ProtectedMetadataNames: []string{name},
}}
plan, err := buildWindowsPrincipalACLPlan(input)
if err == nil {
t.Fatalf("accepted protected metadata name %q, which would place a deny ACE outside %s:\n%#v", name, root, plan.Entries)
}
if len(plan.Entries) != 0 {
t.Errorf("returned %d entries alongside the error, so a caller ignoring err would still apply them", len(plan.Entries))
}
})
}
}
// A PRINCIPAL MUST NEVER BE GRANTED READ AT A VOLUME ROOT.
//
// permissionProfileReadRoots seeds its list with the bare separator, because
// the workspace-write posture is read-all with a write jail. That costs nothing
// for the capability backend, whose child runs as the caller and could read
// those paths anyway. For a principal it is a real, persistent, inheritable
// allow-read ACE for a separate local account at the root of the drive.
//
// Built from the production profile rather than a synthetic fixture, because
// the whole point is that the shipped configuration produced it.
func TestPrincipalACLPlanNeverGrantsReadAtAVolumeRoot(t *testing.T) {
workspace := filepath.FromSlash("/ws/project")
profile := DefaultPermissionProfile(workspace)
// If the profile ever stops carrying a volume root, this test proves nothing
// and should be retired rather than left passing vacuously.
seeded := false
for _, root := range profile.FileSystem.ReadRoots {
if isWindowsVolumeRoot(normalizeProfilePath(root)) {
seeded = true
break
}
}
if !seeded {
t.Skipf("the production profile no longer contains a volume read root: %v", profile.FileSystem.ReadRoots)
}
plan, err := buildWindowsPrincipalACLPlan(windowsPrincipalACLInput{
PrincipalSID: testPrincipalSID,
ReadRoots: profile.FileSystem.ReadRoots,
WriteRoots: profile.FileSystem.WriteRoots,
})
if err != nil {
t.Fatalf("buildWindowsPrincipalACLPlan: %v", err)
}
for _, entry := range plan.Entries {
if entry.Action == WindowsACLAllowRead && isWindowsVolumeRoot(entry.Path) {
t.Errorf("plan grants the principal read at the volume root %q, which inherits into every directory on the drive", entry.Path)
}
}
// And the workspace itself must still be reachable, or this traded a real
// grant for a broken sandbox.
wantWorkspace := normalizeProfilePath(workspace)
reachable := false
for _, entry := range plan.Entries {
if entry.Path == wantWorkspace && (entry.Action == WindowsACLAllowRead || entry.Action == WindowsACLAllowWrite) {
reachable = true
break
}
}
if !reachable {
t.Errorf("no grant for the workspace root %q, so the principal could not read its own workspace", wantWorkspace)
}
}
// The ordinary names must keep working, or the guard above is just a break.
func TestPrincipalACLPlanStillAcceptsTheRealProtectedNames(t *testing.T) {
input := testPrincipalInput()
input.WriteRoots = []WritableRoot{{
Root: filepath.FromSlash("/ws/project"),
ProtectedMetadataNames: sandboxFullyProtectedMetadataNames,
}}
if _, err := buildWindowsPrincipalACLPlan(input); err != nil {
t.Fatalf("the shipped protected names were rejected: %v", err)
}
}
@@ -0,0 +1,76 @@
//go:build windows
package sandbox
// DPAPI wrapping for the stored sandbox principal password.
//
// The file ACL is the primary control and remains the thing that keeps the
// sandbox principal itself from reading its own credential. This adds the layer
// the ACL cannot: an ACL is only meaningful while the filesystem is being asked
// to enforce it, so a backup, a mounted disk image, or a copy taken by anyone
// who can bypass the DACL yields the password in the clear. CryptProtectData
// binds the ciphertext to the invoking user's logon secret, so an offline copy
// is inert without that user's credentials.
//
// The principal name is passed as optional entropy, which makes a blob usable
// only for the account it was minted for; moving one secret file over another
// then fails to decrypt instead of silently authenticating the wrong principal.
import (
"errors"
"fmt"
"unsafe"
"golang.org/x/sys/windows"
)
// protectWindowsSecret encrypts a password to the current user.
//
// CRYPTPROTECT_UI_FORBIDDEN matters here: this runs inside a CLI and, on the
// setup path, potentially without an interactive desktop, so DPAPI must fail
// rather than try to prompt.
func protectWindowsSecret(plaintext string, entropy string) ([]byte, error) {
if plaintext == "" {
return nil, errors.New("windows sandbox secret: refusing to protect an empty password")
}
in := windows.DataBlob{
Size: uint32(len(plaintext)),
Data: &[]byte(plaintext)[0],
}
entropyBytes := []byte(entropy)
var entropyBlob *windows.DataBlob
if len(entropyBytes) > 0 {
entropyBlob = &windows.DataBlob{Size: uint32(len(entropyBytes)), Data: &entropyBytes[0]}
}
var out windows.DataBlob
if err := windows.CryptProtectData(&in, nil, entropyBlob, 0, nil, windows.CRYPTPROTECT_UI_FORBIDDEN, &out); err != nil {
return nil, fmt.Errorf("protect sandbox secret: %w", err)
}
// DPAPI allocates the output with LocalAlloc; copy it out and hand it back.
defer windows.LocalFree(windows.Handle(unsafe.Pointer(out.Data)))
return append([]byte(nil), unsafe.Slice(out.Data, out.Size)...), nil
}
// unprotectWindowsSecret reverses protectWindowsSecret. It fails for any user
// other than the one that wrote the blob, and for a blob minted with a different
// principal name as entropy.
func unprotectWindowsSecret(ciphertext []byte, entropy string) (string, error) {
if len(ciphertext) == 0 {
return "", errWindowsSandboxIdentityUnavailable
}
in := windows.DataBlob{
Size: uint32(len(ciphertext)),
Data: &ciphertext[0],
}
entropyBytes := []byte(entropy)
var entropyBlob *windows.DataBlob
if len(entropyBytes) > 0 {
entropyBlob = &windows.DataBlob{Size: uint32(len(entropyBytes)), Data: &entropyBytes[0]}
}
var out windows.DataBlob
if err := windows.CryptUnprotectData(&in, nil, entropyBlob, 0, nil, windows.CRYPTPROTECT_UI_FORBIDDEN, &out); err != nil {
return "", fmt.Errorf("unprotect sandbox secret: %w", err)
}
defer windows.LocalFree(windows.Handle(unsafe.Pointer(out.Data)))
return string(unsafe.Slice(out.Data, out.Size)), nil
}
@@ -0,0 +1,270 @@
//go:build windows
package sandbox
// Minting a token for a sandbox principal.
//
// A provisioned account is inert until something can log on as it. Windows
// gates that behind account rights held in the local security policy, so setup
// grants the principal exactly one: the right to be logged on as a batch job,
// which is what a non-interactive service-style logon needs. It is deliberately
// NOT granted interactive, network or remote-interactive logon, and those three
// are explicitly DENIED, so the account cannot be used to sign in at the
// console, over SMB, or through RDP even if its password leaked. The password
// exists only so LogonUser can mint a token; nobody is meant to type it.
//
// Rights are granted at setup (elevated) because LsaAddAccountRights requires
// administrator privileges. The per-command path only calls LogonUser, which
// needs no special privilege once the batch right is in place.
import (
"errors"
"fmt"
"runtime"
"unsafe"
"golang.org/x/sys/windows"
)
const (
// Logon type/provider for a non-interactive token. Batch is the closest
// match for "run this command as a service-like principal": it produces a
// full token without a desktop or network-credential footprint.
logon32LogonBatch = 4
logon32ProviderDefault = 0
// LSA policy access rights needed to add account rights.
policyCreateAccount = 0x00000010
policyLookupNames = 0x00000800
// Account rights. The sandbox principal gets the batch right and is denied
// every interactive path.
seBatchLogonRight = "SeBatchLogonRight"
seDenyInteractiveLogonRight = "SeDenyInteractiveLogonRight"
seDenyNetworkLogonRight = "SeDenyNetworkLogonRight"
seDenyRemoteInteractiveRight = "SeDenyRemoteInteractiveLogonRight"
seDenyServiceLogonRightName = "SeDenyServiceLogonRight"
windowsIdentityLogonRightsNote = "granted by `zero sandbox setup`"
)
var (
procLogonUserW = windows.NewLazySystemDLL("advapi32.dll").NewProc("LogonUserW")
procLsaOpenPolicy = windows.NewLazySystemDLL("advapi32.dll").NewProc("LsaOpenPolicy")
procLsaClose = windows.NewLazySystemDLL("advapi32.dll").NewProc("LsaClose")
procLsaAddAccountRights = windows.NewLazySystemDLL("advapi32.dll").NewProc("LsaAddAccountRights")
// Retiring a principal has to drop its rights as well as its account, or the
// LSA policy database keeps an entry keyed to a SID that no longer resolves.
procLsaRemoveAccountRights = windows.NewLazySystemDLL("advapi32.dll").NewProc("LsaRemoveAccountRights")
procLsaNtStatusToWinErr = windows.NewLazySystemDLL("advapi32.dll").NewProc("LsaNtStatusToWinError")
)
// lsaUnicodeString mirrors LSA_UNICODE_STRING. Length and MaximumLength are
// BYTE counts, not rune counts, which is the usual source of bugs here.
type lsaUnicodeString struct {
Length uint16
MaximumLength uint16
Buffer *uint16
}
// lsaObjectAttributes mirrors LSA_OBJECT_ATTRIBUTES. Every field except Length
// is unused for LsaOpenPolicy, but the struct must still be the right size.
type lsaObjectAttributes struct {
Length uint32
RootDirectory windows.Handle
ObjectName *lsaUnicodeString
Attributes uint32
SecurityDescriptor unsafe.Pointer
SecurityQualityOfService unsafe.Pointer
}
// newLSAString builds an LSA_UNICODE_STRING over a UTF-16 buffer the caller
// keeps alive. The returned value borrows that buffer, so the buffer must
// outlive every use of the string.
func newLSAString(buffer []uint16) lsaUnicodeString {
if len(buffer) == 0 {
return lsaUnicodeString{}
}
// The buffer is NUL-terminated; the LSA length counts bytes WITHOUT the
// terminator, while MaximumLength counts bytes WITH it.
runes := len(buffer) - 1
return lsaUnicodeString{
Length: uint16(runes * 2),
MaximumLength: uint16(len(buffer) * 2),
Buffer: &buffer[0],
}
}
// lsaStatusError converts an NTSTATUS from an Lsa* call into a Go error, going
// through LsaNtStatusToWinError so the message is the familiar Win32 one rather
// than a raw NTSTATUS.
func lsaStatusError(call string, status uintptr) error {
if status == 0 {
return nil
}
winErr, _, _ := procLsaNtStatusToWinErr.Call(status)
return fmt.Errorf("%s: %w", call, windows.Errno(winErr))
}
// grantWindowsSandboxLogonRights gives the principal the batch logon right and
// denies every interactive logon path. Idempotent: LsaAddAccountRights silently
// succeeds when the account already holds a right, so setup can re-run.
//
// Requires an elevated caller.
func grantWindowsSandboxLogonRights(sid *windows.SID) error {
if sid == nil {
return fmt.Errorf("grant sandbox logon rights: nil SID")
}
var attributes lsaObjectAttributes
attributes.Length = uint32(unsafe.Sizeof(attributes))
var policy windows.Handle
status, _, _ := procLsaOpenPolicy.Call(
0, // local system
uintptr(unsafe.Pointer(&attributes)),
uintptr(policyCreateAccount|policyLookupNames),
uintptr(unsafe.Pointer(&policy)),
)
// LsaOpenPolicy borrows the attributes struct by address, so it has to stay
// reachable until the call has returned.
runtime.KeepAlive(attributes)
if err := lsaStatusError("LsaOpenPolicy", status); err != nil {
return err
}
defer procLsaClose.Call(uintptr(policy))
rights := []string{
seBatchLogonRight,
seDenyInteractiveLogonRight,
seDenyNetworkLogonRight,
seDenyRemoteInteractiveRight,
seDenyServiceLogonRightName,
}
// Each right is added on its own call so one unsupported name on an odd SKU
// cannot silently drop the others.
for _, right := range rights {
buffer, err := windows.UTF16FromString(right)
if err != nil {
return err
}
entry := newLSAString(buffer)
status, _, _ := procLsaAddAccountRights.Call(
uintptr(policy),
uintptr(unsafe.Pointer(sid)),
uintptr(unsafe.Pointer(&entry)),
1,
)
// Both the descriptor and the buffer it points at are borrowed by the
// call. Kept alive before the error check, not after, so the failure path
// does not return with them already collectable.
runtime.KeepAlive(entry)
runtimeKeepAliveUint16(buffer)
if err := lsaStatusError("LsaAddAccountRights("+right+")", status); err != nil {
return err
}
}
return nil
}
// revokeWindowsSandboxLogonRights drops every account right held by a principal
// and removes its entry from the LSA policy database.
//
// This is the logon-rights counterpart to revoking ACEs by trustee, and it has
// the same reason to exist: deleting the account on its own leaves the rights
// behind, keyed to a SID that no longer resolves, which is the orphaned residue
// this model is supposed to avoid. It must therefore run BEFORE the account is
// deleted, while the SID is still resolvable.
//
// Removing all rights rather than naming them is deliberate. The principal is
// being retired, so anything keyed to it should go, including rights a previous
// version of setup granted and this one no longer knows about.
//
// Requires an elevated caller. A principal that holds no rights is not an error:
// LsaRemoveAccountRights reports ERROR_FILE_NOT_FOUND for an account with no LSA
// entry, which is the state teardown is trying to reach anyway.
func revokeWindowsSandboxLogonRights(sid *windows.SID) error {
if sid == nil {
return fmt.Errorf("revoke sandbox logon rights: nil SID")
}
var attributes lsaObjectAttributes
attributes.Length = uint32(unsafe.Sizeof(attributes))
var policy windows.Handle
status, _, _ := procLsaOpenPolicy.Call(
0, // local system
uintptr(unsafe.Pointer(&attributes)),
uintptr(policyCreateAccount|policyLookupNames),
uintptr(unsafe.Pointer(&policy)),
)
runtime.KeepAlive(attributes)
if err := lsaStatusError("LsaOpenPolicy", status); err != nil {
return err
}
defer procLsaClose.Call(uintptr(policy))
status, _, _ = procLsaRemoveAccountRights.Call(
uintptr(policy),
uintptr(unsafe.Pointer(sid)),
1, // AllRights: drop everything and delete the LSA account object
0, // UserRights ignored when AllRights is set
0, // CountOfRights likewise
)
runtime.KeepAlive(sid)
if err := lsaStatusError("LsaRemoveAccountRights", status); err != nil {
if errors.Is(err, windows.ERROR_FILE_NOT_FOUND) {
return nil
}
return err
}
return nil
}
// logonWindowsSandboxPrincipal mints a primary token for the sandbox account.
// The caller owns the returned token and must Close it.
//
// This needs no elevation: the batch logon right granted at setup is what makes
// it work, which is why the per-command path can run unelevated once setup has
// been done once.
func logonWindowsSandboxPrincipal(username string, password string) (windows.Token, error) {
user, err := windows.UTF16PtrFromString(username)
if err != nil {
return 0, err
}
// "." is the local machine, so the lookup never leaves this host even if the
// machine is domain-joined and a same-named domain account exists.
domain, err := windows.UTF16PtrFromString(".")
if err != nil {
return 0, err
}
secret, err := windows.UTF16PtrFromString(password)
if err != nil {
return 0, err
}
var token windows.Token
result, _, callErr := procLogonUserW.Call(
uintptr(unsafe.Pointer(user)),
uintptr(unsafe.Pointer(domain)),
uintptr(unsafe.Pointer(secret)),
logon32LogonBatch,
logon32ProviderDefault,
uintptr(unsafe.Pointer(&token)),
)
// The three strings are borrowed for the duration of the call.
runtime.KeepAlive(user)
runtime.KeepAlive(domain)
runtime.KeepAlive(secret)
if result == 0 {
if callErr != nil && callErr != windows.ERROR_SUCCESS {
return 0, fmt.Errorf("LogonUser(%s): %w", username, callErr)
}
return 0, fmt.Errorf("LogonUser(%s) failed", username)
}
return token, nil
}
// runtimeKeepAliveUint16 keeps a UTF-16 buffer reachable across a syscall that
// borrows it. Declared rather than inlined so the intent is explicit at each
// call site; the compiler must not free the slice while LSA holds the pointer.
func runtimeKeepAliveUint16(buffer []uint16) {
if len(buffer) == 0 {
return
}
_ = buffer[0]
}
@@ -0,0 +1,41 @@
//go:build windows
package sandbox
import (
"errors"
"testing"
"golang.org/x/sys/windows"
)
// revokeWindowsSandboxLogonRights treats "this account holds no rights" as
// success, because that is the state teardown is trying to reach anyway. That
// relies on the NTSTATUS for it surviving the trip through LsaNtStatusToWinError
// as an error errors.Is can still match, which is exactly the kind of Windows
// errno assumption that quietly turns out to be false. Assert it rather than
// trust it.
//
// Needs no privilege: LsaNtStatusToWinError is a pure status translation, so
// this runs everywhere rather than joining the gated set.
func TestLsaStatusErrorMapsObjectNameNotFound(t *testing.T) {
// STATUS_OBJECT_NAME_NOT_FOUND, what LsaRemoveAccountRights reports for an
// account that has no LSA entry.
const statusObjectNameNotFound = 0xC0000034
err := lsaStatusError("LsaRemoveAccountRights", statusObjectNameNotFound)
if err == nil {
t.Fatal("a nonzero NTSTATUS produced no error")
}
if !errors.Is(err, windows.ERROR_FILE_NOT_FOUND) {
t.Fatalf("error = %v, want one errors.Is matches against ERROR_FILE_NOT_FOUND; "+
"without that, revoking a principal that simply holds no rights fails teardown", err)
}
// The tolerance must be specific. If any failure matched it, revoke would
// swallow a real one and teardown would report success having done nothing.
const statusAccessDenied = 0xC0000022
if other := lsaStatusError("LsaRemoveAccountRights", statusAccessDenied); errors.Is(other, windows.ERROR_FILE_NOT_FOUND) {
t.Fatalf("access denied matched the not-found tolerance: %v", other)
}
}
@@ -0,0 +1,421 @@
//go:build windows
package sandbox
import (
"errors"
"os"
"path/filepath"
"strings"
"testing"
"golang.org/x/sys/windows"
)
// Policy deny-write has to reach the principal plan.
//
// The capability plan has always emitted these. The principal plan denied write
// only on protected metadata and read-only subpaths inside write roots, so once
// the runner used a principal token a policy deny sitting anywhere else was not
// enforced at the OS layer at all, and a shell child could write where the
// restricted-token backend would have stopped it.
func TestPrincipalACLPlanCarriesPolicyDenyWrite(t *testing.T) {
root := filepath.Join(t.TempDir(), "workspace")
denied := filepath.Join(root, "protected", "keep-out")
plan, err := buildWindowsPrincipalACLPlan(windowsPrincipalACLInput{
PrincipalSID: "S-1-5-21-0-0-0-1001",
WriteRoots: []WritableRoot{{Root: root}},
DenyWrite: []string{denied},
})
if err != nil {
t.Fatalf("buildWindowsPrincipalACLPlan: %v", err)
}
entry, ok := findPrincipalACLEntry(plan, WindowsACLDenyWrite, denied)
if !ok {
t.Fatalf("no deny-write ACE for the policy path; plan = %+v", plan.Entries)
}
// Materialized for the same reason the capability plan does it: the applier
// skips targets that do not exist, so a deny on a path created after setup
// would never be written.
if !entry.Materialize {
t.Error("policy deny-write ACE is not materialized, so it is skipped when the path does not exist yet")
}
}
// Deny-read has to be materialized too, which it was not.
func TestPrincipalACLPlanMaterializesDenyRead(t *testing.T) {
root := filepath.Join(t.TempDir(), "workspace")
secret := filepath.Join(t.TempDir(), "elsewhere", "creds")
plan, err := buildWindowsPrincipalACLPlan(windowsPrincipalACLInput{
PrincipalSID: "S-1-5-21-0-0-0-1001",
WriteRoots: []WritableRoot{{Root: root}},
DenyRead: []string{secret},
})
if err != nil {
t.Fatalf("buildWindowsPrincipalACLPlan: %v", err)
}
entry, ok := findPrincipalACLEntry(plan, WindowsACLDenyRead, secret)
if !ok {
t.Fatalf("no deny-read ACE emitted; plan = %+v", plan.Entries)
}
if !entry.Materialize {
t.Fatal("deny-read ACE is not materialized, so a path created after setup never gets one")
}
}
// Deny entries must still precede the grants they carve out of, which is what
// makes them win under Windows DACL evaluation. Adding deny-write to the plan is
// only safe if it did not disturb that ordering.
func TestPrincipalACLPlanKeepsDeniesBeforeGrants(t *testing.T) {
root := filepath.Join(t.TempDir(), "workspace")
plan, err := buildWindowsPrincipalACLPlan(windowsPrincipalACLInput{
PrincipalSID: "S-1-5-21-0-0-0-1001",
WriteRoots: []WritableRoot{{Root: root}},
DenyWrite: []string{filepath.Join(root, "nope")},
DenyRead: []string{filepath.Join(root, "secret")},
})
if err != nil {
t.Fatalf("buildWindowsPrincipalACLPlan: %v", err)
}
firstGrant := -1
for i, entry := range plan.Entries {
switch entry.Action {
case WindowsACLAllowWrite, WindowsACLAllowRead:
if firstGrant == -1 {
firstGrant = i
}
case WindowsACLDenyRead, WindowsACLDenyWrite:
if firstGrant != -1 {
t.Fatalf("deny entry at %d follows a grant at %d; the grant would win", i, firstGrant)
}
}
}
}
func findPrincipalACLEntry(plan WindowsACLPlan, action WindowsACLAction, path string) (WindowsACLEntry, bool) {
want := normalizeProfilePath(path)
for _, entry := range plan.Entries {
if entry.Action == action && entry.Path == want {
return entry, true
}
}
return WindowsACLEntry{}, false
}
// An adopted account must not have its password rotated during provisioning.
//
// Rotating there left every later step running against an account whose password
// had already been replaced with nothing on disk holding it. Any failure in
// between stranded a working principal: the rollback correctly declined to
// delete an account it had not created, so what remained was a live account
// authenticated by a password no longer stored anywhere, and the command path
// read the absent secret as "not provisioned" and quietly fell back to the
// weaker backend.
func TestProvisionWindowsSandboxIdentityDefersPasswordRotation(t *testing.T) {
stubWindowsProvisioning(t, true, nil, nil, nil)
rotated := false
previous := resetWindowsSandboxUserPasswordFn
t.Cleanup(func() { resetWindowsSandboxUserPasswordFn = previous })
resetWindowsSandboxUserPasswordFn = func(string, string) error {
rotated = true
return nil
}
if _, _, _, err := provisionWindowsSandboxIdentity("workspacekey", windowsSandboxRoleOffline); err != nil {
t.Fatalf("provisioning an adopted account: %v", err)
}
if rotated {
t.Fatal("provisioning rotated the password; the window this closes lasts until the secret is committed")
}
}
// The ownership comment carries the full workspace key, so two workspaces whose
// digests collide in the 11 characters the account name can hold are refused
// rather than silently sharing one account, one secret and one ACL identity.
func TestWindowsSandboxUserCommentDistinguishesWorkspaces(t *testing.T) {
first := windowsSandboxUserCommentFor("aaaaaaaaaaaabbbbbbbb")
second := windowsSandboxUserCommentFor("aaaaaaaaaaaacccccccc")
if first == second {
t.Fatal("two workspaces produced the same ownership comment, so a name collision would be adopted")
}
if !strings.HasPrefix(first, windowsSandboxUserComment) {
t.Fatalf("comment %q lost the marker prefix that identifies it as ours", first)
}
// The names DO collide, which is the whole reason the comment has to carry
// the key. If this stops being true the test is no longer covering anything.
if windowsSandboxUserName("aaaaaaaaaaaabbbbbbbb", windowsSandboxRoleOffline) != windowsSandboxUserName("aaaaaaaaaaaacccccccc", windowsSandboxRoleOffline) {
t.Skip("account names no longer collide for these keys; revisit what this test is for")
}
}
// Rollback must not strip an adopted principal's logon rights.
//
// revokeWindowsSandboxLogonRights passes AllRights, which drops every right the
// account holds and deletes its LSA object. On an account this run created that
// is a rollback; on one it adopted it destroys the SeBatchLogonRight and
// deny-logon rights an earlier setup established, which is the working
// principal this path exists to preserve.
func TestSetupRollbackRevokesRightsOnlyForCreatedPrincipals(t *testing.T) {
for name, testCase := range map[string]struct {
existed bool
wantRevoked bool
}{
"adopted principal": {existed: true, wantRevoked: false},
"created principal": {existed: false, wantRevoked: true},
} {
t.Run(name, func(t *testing.T) {
stubWindowsProvisioning(t, testCase.existed, nil, nil, nil)
revoked := false
prevGrant, prevRevoke := grantWindowsSandboxLogonRightsFn, revokeWindowsSandboxLogonRightsFn
t.Cleanup(func() {
grantWindowsSandboxLogonRightsFn, revokeWindowsSandboxLogonRightsFn = prevGrant, prevRevoke
})
// Fail the grant so the undo path runs with rights already attempted,
// which is the state that used to revoke unconditionally.
grantWindowsSandboxLogonRightsFn = func(*windows.SID) error {
return errors.New("LSA grant refused by policy")
}
revokeWindowsSandboxLogonRightsFn = func(*windows.SID) error {
revoked = true
return nil
}
config := WindowsSandboxCommandConfig{
SandboxHome: t.TempDir(),
WorkspaceRoots: []string{`C:\ws`},
}
if _, _, err := provisionWindowsSandboxPrincipalForSetup(config, windowsSandboxRoleOffline); err == nil {
t.Fatal("provisioning reported success despite an injected grant failure")
}
if revoked != testCase.wantRevoked {
if testCase.wantRevoked {
t.Fatal("rights were not revoked for an account this run created, leaving LSA entries keyed to a SID about to be deleted")
}
t.Fatal("rights were revoked for an adopted account; AllRights drops its pre-existing rights and deletes the LSA object")
}
// And the account itself: requested through the fake for the created
// case, never for an adopted one. This fixture fakes creation, so the
// only acceptable deletion is one the fake sees.
removals := len(stubbedWindowsIdentityRemovals)
if testCase.existed && removals != 0 {
t.Fatalf("rollback deleted an adopted account: %v", stubbedWindowsIdentityRemovals)
}
if !testCase.existed && removals != 1 {
t.Fatalf("rollback of a created account requested %d removals through the fake, want exactly one: %v", removals, stubbedWindowsIdentityRemovals)
}
})
}
}
// A secret the current user cannot read is unavailability, not breakage.
//
// The secret's DACL names whoever ran setup. An operator who elevated with a
// separate administrative account, via runas or an over-the-shoulder UAC
// prompt, leaves a secret their ordinary account cannot open. Treating that as a
// hard error made every sandboxed command fail on a machine that was merely set
// up by a different admin; it belongs in the same fail-soft path as a missing
// secret, so the warning fires and the restricted token takes over.
func TestReadWindowsSandboxSecretTreatsPermissionDeniedAsUnavailable(t *testing.T) {
previous := readWindowsSandboxSecretFile
t.Cleanup(func() { readWindowsSandboxSecretFile = previous })
readWindowsSandboxSecretFile = func(string) ([]byte, error) {
return nil, &os.PathError{Op: "open", Path: "secret", Err: windows.ERROR_ACCESS_DENIED}
}
if _, err := readWindowsSandboxSecret(`C:\anything.secret`); err != errWindowsSandboxIdentityUnavailable {
t.Fatalf("permission-denied read returned %v, want errWindowsSandboxIdentityUnavailable so the command falls back", err)
}
}
// A workspace must not bind to another workspace's principal.
//
// The account name carries only 11 characters of the workspace digest, so two
// workspaces can derive the same name. Provisioning refuses that case by
// checking the full key in the account comment, but the command path resolved
// the name straight to a SID. The workspace that lost the race would have failed
// setup and then quietly run as the other one's principal, using its secret and
// its ACL identity.
func TestLookupWindowsSandboxIdentityRejectsForeignWorkspace(t *testing.T) {
previous := windowsSandboxUserIsManagedFn
t.Cleanup(func() { windowsSandboxUserIsManagedFn = previous })
prevSID := resolveWindowsSandboxSIDFn
t.Cleanup(func() { resolveWindowsSandboxSIDFn = prevSID })
// The account resolves; whether it BELONGS to this workspace is the question.
resolveWindowsSandboxSIDFn = func(string) (*windows.SID, error) {
return windows.CreateWellKnownSid(windows.WinLocalSystemSid)
}
var askedKey string
windowsSandboxUserIsManagedFn = func(_ string, workspaceKey string) (bool, error) {
askedKey = workspaceKey
return false, nil
}
_, err := lookupWindowsSandboxIdentity("workspacekey", windowsSandboxRoleOffline)
if err == nil {
t.Fatal("lookup accepted an account belonging to another workspace")
}
if errors.Is(err, errWindowsSandboxIdentityUnavailable) {
t.Fatal("a foreign account must not read as unprovisioned; that would silently fall back instead of reporting the conflict")
}
if askedKey != "" && askedKey != "workspacekey" {
t.Fatalf("ownership was checked against %q, want the caller's workspace key", askedKey)
}
}
// An account that does not exist must stay the unavailable sentinel rather than
// becoming a collision error, since that is the ordinary not-set-up state.
func TestLookupWindowsSandboxIdentityAbsentAccountIsUnavailable(t *testing.T) {
previous := windowsSandboxUserIsManagedFn
t.Cleanup(func() { windowsSandboxUserIsManagedFn = previous })
windowsSandboxUserIsManagedFn = func(string, string) (bool, error) {
t.Fatal("ownership must not be consulted for an account that does not resolve")
return false, nil
}
if _, err := lookupWindowsSandboxIdentity("nosuchworkspacekey", windowsSandboxRoleOffline); !errors.Is(err, errWindowsSandboxIdentityUnavailable) {
t.Fatalf("absent account returned %v, want errWindowsSandboxIdentityUnavailable", err)
}
}
// The git control-plane carveouts must be materialized.
//
// gitMetadataWriteCarveouts supplies .git/config and .git/hooks as
// ReadOnlySubpaths of the workspace. On a workspace where git has not run yet
// they do not exist when setup applies the plan, and applyWindowsACLPlan skips
// an absent target, so the deny ACEs were never written. Once git created those
// paths the principal still held inherited write access and could install a
// hook or rewrite credential.helper.
func TestPrincipalACLPlanMaterializesReadOnlySubpaths(t *testing.T) {
root := filepath.Join(t.TempDir(), "workspace")
carveout := filepath.Join(root, ".git", "config")
plan, err := buildWindowsPrincipalACLPlan(windowsPrincipalACLInput{
PrincipalSID: "S-1-5-21-0-0-0-1001",
WriteRoots: []WritableRoot{{Root: root, ReadOnlySubpaths: []string{carveout}}},
})
if err != nil {
t.Fatalf("buildWindowsPrincipalACLPlan: %v", err)
}
entry, ok := findPrincipalACLEntry(plan, WindowsACLDenyWrite, carveout)
if !ok {
t.Fatalf("no deny-write ACE for the git carveout; plan = %+v", plan.Entries)
}
if !entry.Materialize {
t.Fatal("git carveout deny-write is not materialized, so it is skipped on a workspace where .git does not exist yet")
}
}
// Setup must grant the principal the same runtime root that commands write to.
//
// permissionProfileWithRuntime appends this root to WriteRoots on every command
// and redirects HOME, GOCACHE and npm_config_cache into it, but it lives under
// the user cache rather than the workspace, so the profile setup sees never
// contains it. A principal is a separate account with no rights there, so
// without a grant every npm install or go build fails on a cache write.
//
// The assertion that matters is that the two derivations agree. If they drift,
// setup writes the ACE on one directory while commands use another, and the
// symptom is a bare ACCESS_DENIED with nothing pointing at the sandbox.
func TestSetupGrantsTheRuntimeRootCommandsActuallyUse(t *testing.T) {
isolateSandboxRuntimeRoots(t)
workspace := filepath.Join(t.TempDir(), "ws")
if err := os.MkdirAll(workspace, 0o700); err != nil {
t.Fatal(err)
}
granted, err := setupWindowsSandboxRuntimeRoot(WindowsSandboxCommandConfig{
WorkspaceRoots: []string{workspace},
})
if err != nil {
t.Fatalf("setupWindowsSandboxRuntimeRoot: %v", err)
}
if len(granted) == 0 {
t.Fatal("no runtime root resolved for a configured workspace")
}
// EVERY granted candidate has to exist, not just the one this process would
// pick: applyWindowsACLPlan fails the whole run on a target that is absent.
for _, root := range granted {
if info, err := os.Stat(root); err != nil || !info.IsDir() {
t.Fatalf("runtime root %q was not created; applyWindowsACLPlan skips absent targets so the grant would no-op (stat err %v)", root, err)
}
}
// What a command would actually use.
runtimeState, release, err := prepareSandboxRuntime(workspace)
if err != nil {
t.Fatalf("prepareSandboxRuntime: %v", err)
}
if release != nil {
defer release()
}
// The command's choice has to be one setup provisioned. Setup grants the whole
// candidate set precisely because the choice is made per process, so the
// contract is membership rather than equality.
if !grantedRuntimeRootsCover(granted, runtimeState.Root) {
t.Fatalf("setup granted %q but commands write to %q", granted, runtimeState.Root)
}
}
// grantedRuntimeRootsCover reports whether the root a command selected is one of
// the roots setup granted an ACE on.
func grantedRuntimeRootsCover(granted []string, selected string) bool {
for _, root := range granted {
if filepath.Clean(root) == filepath.Clean(selected) {
return true
}
}
return false
}
// No workspace root means nothing to grant, which is not an error.
func TestSetupRuntimeRootWithoutWorkspaceIsNotAnError(t *testing.T) {
isolateSandboxRuntimeRoots(t)
granted, err := setupWindowsSandboxRuntimeRoot(WindowsSandboxCommandConfig{})
if err != nil {
t.Fatalf("no workspace root should not error: %v", err)
}
if len(granted) != 0 {
t.Fatalf("granted %q with no workspace configured", granted)
}
}
// An account in a privileged group must not be adopted, even when name and
// ownership comment say it is ours.
//
// Adoption resets the password and hands the account to the sandbox. If that
// account is also in Administrators, the sandbox gains the rights the sandbox
// exists to withhold: rewriting the ACLs confining it, reading the secret locked
// to the invoking user, and stopping Zero.
func TestProvisionWindowsSandboxIdentityRefusesPrivilegedAccount(t *testing.T) {
stubWindowsProvisioning(t, true, nil, nil, nil)
previous := windowsSandboxUserIsPrivilegedFn
t.Cleanup(func() { windowsSandboxUserIsPrivilegedFn = previous })
windowsSandboxUserIsPrivilegedFn = func(string) (bool, error) { return true, nil }
_, _, created, err := provisionWindowsSandboxIdentity("workspacekey", windowsSandboxRoleOffline)
if !errors.Is(err, errWindowsSandboxPrivilegedAccount) {
t.Fatalf("provisioning adopted a privileged account, err = %v", err)
}
if created {
t.Fatal("created must stay false for an account this run refused to adopt")
}
}
// The ordinary adopted account is unaffected.
func TestProvisionWindowsSandboxIdentityAdoptsUnprivilegedAccount(t *testing.T) {
stubWindowsProvisioning(t, true, nil, nil, nil)
previous := windowsSandboxUserIsPrivilegedFn
t.Cleanup(func() { windowsSandboxUserIsPrivilegedFn = previous })
windowsSandboxUserIsPrivilegedFn = func(string) (bool, error) { return false, nil }
if _, _, _, err := provisionWindowsSandboxIdentity("workspacekey", windowsSandboxRoleOffline); err != nil {
t.Fatalf("an unprivileged managed account must still be adopted: %v", err)
}
}
@@ -0,0 +1,92 @@
//go:build windows
package sandbox
import (
"errors"
"testing"
"golang.org/x/sys/windows"
)
// Group membership is not frozen at setup. An account provisioned clean can be
// added to Administrators afterwards — by an operator, or by an attacker who
// already has that access and wants the sandbox to hand it back. Provisioning's
// refusal cannot see that; only the path that mints the token can.
func TestLookupPrincipalForCommandRefusesAnAccountThatBecamePrivileged(t *testing.T) {
sid, err := windows.CreateWellKnownSid(windows.WinLocalSystemSid)
if err != nil {
t.Fatalf("CreateWellKnownSid: %v", err)
}
restoreLookupSeams(t, sid)
privilegedCalls := 0
windowsSandboxUserIsPrivilegedFn = func(string) (bool, error) {
privilegedCalls++
return true, nil
}
_, err = lookupWindowsSandboxPrincipalForCommand("workspace-key", windowsSandboxRoleOnline)
if !errors.Is(err, errWindowsSandboxPrivilegedAccount) {
t.Fatalf("err = %v, want errWindowsSandboxPrivilegedAccount", err)
}
if privilegedCalls != 1 {
t.Errorf("privileged check ran %d times, want exactly 1", privilegedCalls)
}
// It must be a hard refusal, not the unavailable sentinel — that one is the
// quiet "not provisioned" fallback and would silently drop the sandbox back
// to the restricted token instead of telling the operator.
if errors.Is(err, errWindowsSandboxIdentityUnavailable) {
t.Error("privileged refusal must not read as the not-provisioned fallback")
}
}
func TestLookupPrincipalForCommandAcceptsAnUnprivilegedAccount(t *testing.T) {
sid, err := windows.CreateWellKnownSid(windows.WinLocalSystemSid)
if err != nil {
t.Fatalf("CreateWellKnownSid: %v", err)
}
restoreLookupSeams(t, sid)
windowsSandboxUserIsPrivilegedFn = func(string) (bool, error) { return false, nil }
identity, err := lookupWindowsSandboxPrincipalForCommand("workspace-key", windowsSandboxRoleOnline)
if err != nil {
t.Fatalf("lookupWindowsSandboxPrincipalForCommand: %v", err)
}
if identity.Username == "" {
t.Error("expected the resolved principal")
}
}
// Teardown must stay able to clean up an account that has become privileged.
// If the refusal lived inside lookupWindowsSandboxIdentity, the account this
// guard exists to catch would become undeletable by Zero.
func TestLookupIdentityItselfDoesNotConsultPrivilege(t *testing.T) {
sid, err := windows.CreateWellKnownSid(windows.WinLocalSystemSid)
if err != nil {
t.Fatalf("CreateWellKnownSid: %v", err)
}
restoreLookupSeams(t, sid)
windowsSandboxUserIsPrivilegedFn = func(string) (bool, error) {
t.Error("teardown's lookup must not be gated on privilege")
return true, nil
}
if _, err := lookupWindowsSandboxIdentity("workspace-key", windowsSandboxRoleOnline); err != nil {
t.Fatalf("lookupWindowsSandboxIdentity: %v", err)
}
}
func restoreLookupSeams(t *testing.T, sid *windows.SID) {
t.Helper()
prevResolve := resolveWindowsSandboxSIDFn
prevManaged := windowsSandboxUserIsManagedFn
prevPrivileged := windowsSandboxUserIsPrivilegedFn
t.Cleanup(func() {
resolveWindowsSandboxSIDFn = prevResolve
windowsSandboxUserIsManagedFn = prevManaged
windowsSandboxUserIsPrivilegedFn = prevPrivileged
})
resolveWindowsSandboxSIDFn = func(string) (*windows.SID, error) { return sid, nil }
windowsSandboxUserIsManagedFn = func(string, string) (bool, error) { return true, nil }
}
@@ -0,0 +1,203 @@
//go:build windows
package sandbox
import (
"errors"
"testing"
"golang.org/x/sys/windows"
)
// stubWindowsProvisioning replaces the four provisioning syscalls so the
// function can run on an ordinary machine. Every one of them needs an elevated
// caller and a real local account, so without this the test would stop at the
// first call and never reach the behaviour it is named for.
func stubWindowsProvisioning(t *testing.T, existed bool, groupErr error, offlineErr error, sidErr error) {
t.Helper()
prevGroup, prevUser := ensureWindowsSandboxGroupFn, ensureWindowsSandboxUserFn
prevOfflineGroup := ensureWindowsSandboxOfflineGroupFn
prevAdd, prevSID := addWindowsSandboxUserToGroupFn, resolveWindowsSandboxSIDFn
prevManaged := windowsSandboxUserIsManagedFn
prevOffline := addWindowsSandboxUserToOfflineGroupFn
prevReset := resetWindowsSandboxUserPasswordFn
prevRemove, prevUpgrade := removeWindowsSandboxIdentityFn, upgradeWindowsSandboxUserCommentFn
stubbedWindowsIdentityRemovals = nil
t.Cleanup(func() {
ensureWindowsSandboxGroupFn, ensureWindowsSandboxUserFn = prevGroup, prevUser
ensureWindowsSandboxOfflineGroupFn = prevOfflineGroup
addWindowsSandboxUserToGroupFn, resolveWindowsSandboxSIDFn = prevAdd, prevSID
windowsSandboxUserIsManagedFn = prevManaged
addWindowsSandboxUserToOfflineGroupFn = prevOffline
resetWindowsSandboxUserPasswordFn = prevReset
removeWindowsSandboxIdentityFn, upgradeWindowsSandboxUserCommentFn = prevRemove, prevUpgrade
})
// THE INVERSE IS FAKED TOO. Creation is faked and ownership is faked, so a
// rollback branch that trusts both would otherwise call the real NetUserDel
// on the current user's deterministic principal for C:ws, an account this
// fixture never created. Removals are recorded for the tests to assert on.
removeWindowsSandboxIdentityFn = func(username, workspaceKey string) error {
stubbedWindowsIdentityRemovals = append(stubbedWindowsIdentityRemovals, username+"|"+workspaceKey)
return nil
}
upgradeWindowsSandboxUserCommentFn = func(string, string) error { return nil }
ensureWindowsSandboxGroupFn = func() error { return nil }
ensureWindowsSandboxOfflineGroupFn = func() error { return nil }
// Adopted accounts are ours in these tests; the ownership check is a real
// syscall and would otherwise refuse before the code under test runs.
windowsSandboxUserIsManagedFn = func(string, string) (bool, error) { return true, nil }
// Stubbed even though provisioning no longer rotates: rotation moved to the
// caller, so nothing under test reaches this today. Left in so that if it
// ever moves back, these tests fail rather than resetting the password of a
// real managed account that happens to exist on the machine running them.
resetWindowsSandboxUserPasswordFn = func(string, string) error {
t.Fatal("provisioning must not rotate an account password; rotation belongs to the caller, immediately before the secret is written")
return nil
}
ensureWindowsSandboxUserFn = func(string, string, string) (bool, error) { return existed, nil }
addWindowsSandboxUserToGroupFn = func(string) error { return groupErr }
addWindowsSandboxUserToOfflineGroupFn = func(string) error { return offlineErr }
resolveWindowsSandboxSIDFn = func(username string) (*windows.SID, error) {
if sidErr != nil {
return nil, sidErr
}
return windows.CreateWellKnownSid(windows.WinLocalSystemSid)
}
}
// A failure after the account has been created must still hand back the name.
//
// The caller's rollback deletes by identity.Username, so returning a zero
// identity alongside created=true asked it to delete "" and quietly left the
// account this run had just made. Group attachment is the case that matters
// most: it is the enforcement boundary and it can fail under local policy.
func TestProvisionWindowsSandboxIdentityReturnsNameForRollback(t *testing.T) {
groupFailure := errors.New("group attachment refused by policy")
offlineFailure := errors.New("offline group attachment refused by policy")
sidFailure := errors.New("sid lookup failed")
for name, testCase := range map[string]struct {
groupErr error
offlineErr error
sidErr error
}{
"group attachment fails": {groupErr: groupFailure},
"offline group attachment fails": {offlineErr: offlineFailure},
"sid resolution fails": {sidErr: sidFailure},
} {
t.Run(name, func(t *testing.T) {
stubWindowsProvisioning(t, false, testCase.groupErr, testCase.offlineErr, testCase.sidErr)
identity, _, created, err := provisionWindowsSandboxIdentity("workspacekey", windowsSandboxRoleOffline)
if err == nil {
t.Fatal("provisioning reported success despite an injected failure")
}
if !created {
t.Fatal("created = false, so the rollback would skip an account this run made")
}
// The whole point: without a name there is nothing to delete.
if identity.Username == "" {
t.Fatal("identity carries no username, so the rollback deletes \"\" and strands the account")
}
if want := windowsSandboxUserName("workspacekey", windowsSandboxRoleOffline); identity.Username != want {
t.Fatalf("username = %q, want %q", identity.Username, want)
}
})
}
}
// An account that already existed must not be deleted because a later step
// failed. created=false is what stops the rollback turning a partial failure
// into the loss of a working principal from an earlier setup.
func TestProvisionWindowsSandboxIdentityDoesNotClaimPreexistingAccount(t *testing.T) {
stubWindowsProvisioning(t, true, errors.New("group attachment refused"), nil, nil)
_, _, created, err := provisionWindowsSandboxIdentity("workspacekey", windowsSandboxRoleOffline)
if err == nil {
t.Fatal("provisioning reported success despite an injected failure")
}
// created is the whole assertion. It is what stops the rollback deleting an
// account it did not make, and it must stay false however provisioning
// fails. The identity is deliberately not checked: an adopted account exits
// early at the ownership check, which is a real syscall and not stubbed
// here, so asserting on the name would be testing the stub rather than the
// contract.
if created {
t.Fatal("created = true for an account this run did not create; rollback would delete a working principal")
}
}
// The write grant has to include delete.
//
// FILE_GENERIC_WRITE covers creating and modifying but not removing or
// renaming, and a rename needs delete on the source. The old same-user token hid
// this because the caller already held inherited rights on its own tree; a
// principal is a separate account with none, so without these it can write files
// it can never remove, which fails ordinary editing and most git operations
// rather than an edge case.
func TestWindowsACLAllowWriteGrantsDelete(t *testing.T) {
mode, mask, err := windowsACLAccess(WindowsACLAllowWrite)
if err != nil {
t.Fatalf("windowsACLAccess: %v", err)
}
if mode != windows.GRANT_ACCESS {
t.Fatalf("mode = %v, want GRANT_ACCESS", mode)
}
// Atomic bits only. FILE_GENERIC_READ and FILE_GENERIC_WRITE both carry
// READ_CONTROL and SYNCHRONIZE, so testing a composite constant with & is
// satisfied by any grant at all and proves nothing.
for label, bit := range map[string]windows.ACCESS_MASK{
"DELETE": windows.DELETE,
"FILE_WRITE_DATA": windows.FILE_WRITE_DATA,
} {
if mask&bit == 0 {
t.Errorf("write grant is missing %s", label)
}
}
// Granting these would let the principal rewrite the very restrictions
// placed on it. They are in the deny mask for that reason and must not
// appear here.
//
// FILE_DELETE_CHILD belongs in this set and was originally in the one
// above, on the reasoning that the grant should mirror the deny mask. On a
// parent it authorises deleting a child whatever the child's own DACL says,
// so on a write root it hands back the write-denied carve-outs underneath:
// delete .git/config, recreate it, and the replacement inherits the grant
// with no deny of its own. Mirroring the deny mask is the wrong instinct —
// denying a capability is not a reason to grant it.
for label, bit := range map[string]windows.ACCESS_MASK{
"WRITE_DAC": windows.WRITE_DAC,
"WRITE_OWNER": windows.WRITE_OWNER,
"FILE_DELETE_CHILD": windowsFileDeleteChild,
} {
if mask&bit != 0 {
t.Errorf("write grant unexpectedly includes %s", label)
}
}
}
// The read grant must stay read-only. Widening the write mask above is only
// safe if this one did not move with it.
func TestWindowsACLAllowReadGrantsNoDelete(t *testing.T) {
_, mask, err := windowsACLAccess(WindowsACLAllowRead)
if err != nil {
t.Fatalf("windowsACLAccess: %v", err)
}
// Atomic bits, for the same reason as above: the read and write composites
// overlap on the standard rights, so a composite check here would report a
// failure that is not real.
for label, bit := range map[string]windows.ACCESS_MASK{
"DELETE": windows.DELETE,
"FILE_DELETE_CHILD": windowsFileDeleteChild,
"FILE_WRITE_DATA": windows.FILE_WRITE_DATA,
} {
if mask&bit != 0 {
t.Errorf("read grant unexpectedly includes %s", label)
}
}
}
// stubbedWindowsIdentityRemovals records every account deletion the mocked
// provisioning fixture was asked for, newest last, as "username|workspaceKey".
var stubbedWindowsIdentityRemovals []string
File diff suppressed because it is too large. Load diff
@@ -0,0 +1,292 @@
//go:build windows
package sandbox
import (
"os"
"strings"
"sync"
"testing"
)
// An opted-in command that ends up on the restricted token anyway must say so.
// Both cases below are correct fallbacks, not errors — but silence leaves the
// operator believing an account boundary is isolating them when it is not, which
// is the same failure the setup-protocol opt-in check exists to prevent, reached
// from the other side. The deny case matters most: deny is the DEFAULT network
// mode, so a fully provisioned, fully agreeing setup still never uses the
// principal for an ordinary command.
func TestWindowsSandboxPrincipalFallbackIsAnnounced(t *testing.T) {
testCases := []struct {
name string
mode NetworkMode
reason string
}{
// The network-deny case is deliberately absent. It used to warn here, but
// this runner is re-exec'd per command, so the sync.Once guarding the notice
// is once per COMMAND — and deny is the default mode, so the warning landed
// on nearly every tool call. That fact belongs to `zero doctor` now, which is
// read once. The deny-mode BEHAVIOUR is still pinned, by
// TestPrincipalBackendDefersToRestrictedTokenWhenNetworkDenied below.
{name: "no principal provisioned on this machine", mode: NetworkAllow, reason: "no sandbox principal is provisioned"},
}
for _, testCase := range testCases {
t.Run(testCase.name, func(t *testing.T) {
var warned []string
originalWarn := warnWindowsSandboxPrincipalNotUsed
warnWindowsSandboxPrincipalNotUsed = func(reason string) { warned = append(warned, reason) }
windowsSandboxPrincipalNotUsedWarnOnce = sync.Once{}
t.Cleanup(func() {
warnWindowsSandboxPrincipalNotUsed = originalWarn
windowsSandboxPrincipalNotUsedWarnOnce = sync.Once{}
})
config := WindowsSandboxCommandConfig{
SandboxHome: t.TempDir(),
CommandCWD: `C:\workspace`,
WorkspaceRoots: []string{`C:\workspace`},
PermissionProfile: PermissionProfile{
FileSystem: FileSystemPolicy{Kind: FileSystemRestricted, WriteRoots: []WritableRoot{{Root: `C:\workspace`}}},
Network: NetworkPolicy{Mode: testCase.mode},
},
Env: map[string]string{windowsSandboxIdentityEnv: "1"},
SandboxLevel: WindowsSandboxLevelRestrictedToken,
Command: []string{"cmd.exe", "/c", "echo"},
}
// Assert the precondition rather than assume it: this must be the quiet
// fallback path, not a token this host actually minted and not an error.
token, ok, err := windowsSandboxPrincipalToken(config)
if ok {
token.Close()
t.Fatalf("host unexpectedly provisioned a principal; this test cannot measure the fallback")
}
if err != nil {
t.Fatalf("windowsSandboxPrincipalToken error = %v, want the quiet fallback", err)
}
if len(warned) != 1 {
t.Fatalf("opted-in fallback warnings = %v, want exactly one naming %q", warned, testCase.reason)
}
if !strings.Contains(warned[0], testCase.reason) {
t.Fatalf("warning = %q, want it to name %q", warned[0], testCase.reason)
}
})
}
}
// The opt-out must stay silent, or the warning becomes noise every user learns
// to ignore.
func TestWindowsSandboxPrincipalFallbackIsSilentWhenOptedOut(t *testing.T) {
var warned []string
originalWarn := warnWindowsSandboxPrincipalNotUsed
warnWindowsSandboxPrincipalNotUsed = func(reason string) { warned = append(warned, reason) }
windowsSandboxPrincipalNotUsedWarnOnce = sync.Once{}
t.Cleanup(func() {
warnWindowsSandboxPrincipalNotUsed = originalWarn
windowsSandboxPrincipalNotUsedWarnOnce = sync.Once{}
})
config := WindowsSandboxCommandConfig{
SandboxHome: t.TempDir(),
CommandCWD: `C:\workspace`,
WorkspaceRoots: []string{`C:\workspace`},
PermissionProfile: PermissionProfile{
FileSystem: FileSystemPolicy{Kind: FileSystemRestricted, WriteRoots: []WritableRoot{{Root: `C:\workspace`}}},
Network: NetworkPolicy{Mode: NetworkDeny},
},
Env: map[string]string{windowsSandboxIdentityEnv: "0"},
SandboxLevel: WindowsSandboxLevelRestrictedToken,
Command: []string{"cmd.exe", "/c", "echo"},
}
if _, ok, err := windowsSandboxPrincipalToken(config); ok || err != nil {
t.Fatalf("windowsSandboxPrincipalToken ok=%v err=%v, want the quiet opted-out fallback", ok, err)
}
if len(warned) != 0 {
t.Fatalf("opted-out command warned %v, want silence", warned)
}
}
// Setup must stay inert unless the principal backend is explicitly opted into.
// This is the property that makes the branch safe to merge while the privileged
// paths are still being validated: without the opt-in, `zero sandbox setup`
// creates no local account and the capability-SID backend is the whole of setup.
func TestWindowsSandboxIdentityGating(t *testing.T) {
for name, testCase := range map[string]struct {
env map[string]string
want bool
}{
// An explicit map entry is authoritative; these cases never reach the
// process environment.
"empty": {env: map[string]string{windowsSandboxIdentityEnv: ""}, want: false},
"zero": {env: map[string]string{windowsSandboxIdentityEnv: "0"}, want: false},
"true not one": {env: map[string]string{windowsSandboxIdentityEnv: "true"}, want: false},
"one": {env: map[string]string{windowsSandboxIdentityEnv: "1"}, want: true},
"one with space": {env: map[string]string{windowsSandboxIdentityEnv: " 1 "}, want: true},
} {
t.Run(name, func(t *testing.T) {
// Pin the process variable too. Every case here supplies an explicit
// map entry so none of them should consult it, and pinning proves
// that rather than assuming it: without this a developer who exports
// the opt-in would see different results from CI.
t.Setenv(windowsSandboxIdentityEnv, "1")
if got := windowsSandboxIdentityEnabled(testCase.env); got != testCase.want {
t.Fatalf("enabled = %v, want %v for %q", got, testCase.want, testCase.env[windowsSandboxIdentityEnv])
}
})
}
}
// With no map entry the process environment decides. That fallback is what the
// elevated setup path actually runs on — it passes no Env — so it needs its own
// coverage rather than riding on a case that also has a map entry.
func TestWindowsSandboxIdentityGatingFallsBackToTheProcessEnvironment(t *testing.T) {
for name, testCase := range map[string]struct {
value string
set bool
want bool
}{
"unset": {set: false, want: false},
"empty": {value: "", set: true, want: false},
"zero": {value: "0", set: true, want: false},
"one": {value: "1", set: true, want: true},
"one with space": {value: " 1 ", set: true, want: true},
} {
t.Run(name, func(t *testing.T) {
// t.Setenv registers the restore even when the variable is then
// cleared, which is the only way to test a genuinely absent variable
// without leaking that state into the rest of the package.
t.Setenv(windowsSandboxIdentityEnv, testCase.value)
if !testCase.set {
if err := os.Unsetenv(windowsSandboxIdentityEnv); err != nil {
t.Fatalf("unset %s: %v", windowsSandboxIdentityEnv, err)
}
}
if got := windowsSandboxIdentityEnabled(nil); got != testCase.want {
t.Fatalf("enabled = %v, want %v (set=%v value=%q)", got, testCase.want, testCase.set, testCase.value)
}
})
}
}
// The command environment wins over the process environment, so a run can opt in
// or out without depending on how the parent shell was launched.
func TestWindowsSandboxIdentityEnvOverridesProcess(t *testing.T) {
t.Setenv(windowsSandboxIdentityEnv, "1")
if windowsSandboxIdentityEnabled(map[string]string{windowsSandboxIdentityEnv: "0"}) {
t.Fatal("command env set to 0 must override a process env of 1")
}
if !windowsSandboxIdentityEnabled(map[string]string{}) {
t.Fatal("with no command-env entry the process env should apply")
}
}
// One workspace maps to one principal, and different workspaces must not share
// an account, or two projects would run under the same identity and could reach
// each other's granted roots.
func TestWindowsSandboxWorkspaceKeyIsStableAndDistinct(t *testing.T) {
first := windowsSandboxWorkspaceKey([]string{`C:\ws\alpha`})
again := windowsSandboxWorkspaceKey([]string{`C:\ws\alpha`})
other := windowsSandboxWorkspaceKey([]string{`C:\ws\beta`})
if first != again {
t.Fatalf("key is not stable: %q vs %q", first, again)
}
if first == other {
t.Fatal("two different workspaces produced the same principal key")
}
if first == "" {
t.Fatal("empty key")
}
// An empty root list still has to yield a usable key rather than a blank one.
if windowsSandboxWorkspaceKey(nil) == "" {
t.Fatal("no workspace roots produced an empty key")
}
}
// Network denial is enforced by WFP filters keyed to the offline-marker SID,
// which only the restricted token carries. A principal token would leave those
// filters matching nothing, so the principal backend must stand down whenever
// the network is denied rather than silently trading network enforcement for
// read confinement.
// The backend now runs under both network modes, so the opt-in is the only thing
// eligibility turns on. The mode selects which principal is used, not whether one
// is used at all.
func TestPrincipalBackendEligibilityTurnsOnlyOnTheOptIn(t *testing.T) {
eligible := func(mode NetworkMode, optIn string) bool {
config := WindowsSandboxCommandConfig{
SandboxHome: t.TempDir(),
WorkspaceRoots: []string{t.TempDir()},
Env: map[string]string{windowsSandboxIdentityEnv: optIn},
}
config.PermissionProfile.Network.Mode = mode
return windowsSandboxPrincipalEligible(config)
}
for _, mode := range []NetworkMode{NetworkDeny, NetworkAllow} {
if !eligible(mode, "1") {
t.Fatalf("principal backend refused with network %q; the mode should choose a principal, not disable the backend", mode)
}
if eligible(mode, "0") {
t.Fatalf("principal backend eligible without the opt-in for network %q", mode)
}
}
}
// The network mode is enforced by WHICH principal runs, because the offline one
// is a member of the group the block filters match. Picking the wrong role is
// therefore a silent loss of network enforcement, so the mapping is asserted
// directly rather than inferred from a token that only exists on a provisioned
// machine.
func TestPrincipalRoleFollowsNetworkMode(t *testing.T) {
if got := windowsSandboxRoleForNetwork(NetworkDeny); got != windowsSandboxRoleOffline {
t.Fatalf("deny selected %q, want the offline principal; the online one is not in the blocked group and would have the network", got)
}
if got := windowsSandboxRoleForNetwork(NetworkAllow); got != windowsSandboxRoleOnline {
t.Fatalf("allow selected %q, want the online principal", got)
}
// Fail closed. An unrecognised mode must lose the network rather than keep it,
// so anything that is not an explicit allow maps to the offline principal.
for _, mode := range []NetworkMode{NetworkMode(""), NetworkMode("bogus"), NetworkMode("ALLOW")} {
if got := windowsSandboxRoleForNetwork(mode); got != windowsSandboxRoleOffline {
t.Fatalf("unrecognised mode %q selected %q, want the offline principal so an unknown mode fails closed", mode, got)
}
}
}
// The account key has to separate USERS, not only workspaces.
//
// The name is machine-wide while the DPAPI secret and the ACL ledger both live
// under the invoking user's sandbox home. Keyed on the workspace alone, two
// Windows users sharing one path derive the same account with private
// bookkeeping: the second finds no ledger of its own and either retires the
// first user's working principal or adopts it and rotates the password while
// storing only its own secret. The first user's marker still validates and its
// next command cannot log on.
//
// Asserting the principal key DIFFERS from the workspace key is what pins that.
// It is the cheapest observable difference; a test that only checked the key was
// stable would pass against the broken version.
func TestPrincipalKeyIsScopedToTheUserNotOnlyTheWorkspace(t *testing.T) {
roots := []string{`C:\ws\shared`}
workspace := windowsSandboxWorkspaceKey(roots)
config := WindowsSandboxCommandConfig{WorkspaceRoots: roots}
principal := windowsSandboxPrincipalKey(config)
if principal == workspace {
t.Fatal("the principal key equals the workspace key, so two users sharing this workspace would derive one account with separate secrets and ledgers")
}
if principal != windowsSandboxPrincipalKey(config) {
t.Error("the principal key is not stable for one user, so a second setup would not find its own account")
}
if other := windowsSandboxPrincipalKey(WindowsSandboxCommandConfig{WorkspaceRoots: []string{`C:\ws\other`}}); other == principal {
t.Error("two workspaces derived the same principal key, so they would share one account")
}
}
// The setup lock must stay keyed to the WORKSPACE alone. Two users setting up
// one shared workspace now provision separate accounts, but they still write
// DACLs on the same paths, so they have to keep serializing against each other.
func TestSetupLockStaysWorkspaceScoped(t *testing.T) {
roots := []string{`C:\ws\shared`}
if windowsSandboxWorkspaceKey(roots) == windowsSandboxPrincipalKey(WindowsSandboxCommandConfig{WorkspaceRoots: roots}) {
t.Fatal("the lock key and the principal key are the same, so making the account per-user also made the lock per-user")
}
}
@@ -0,0 +1,140 @@
//go:build windows
package sandbox
import (
"os"
"path/filepath"
"testing"
)
// AND THE ANCESTOR IS PART OF THE PATH TOO.
//
// The sibling test puts the junction at the directory the secret is addressed
// into, which the no-follow open of that directory refuses. This one puts it
// ABOVE a component that does not exist yet, which is the case the refusal never
// saw: os.MkdirAll walked the pathname, followed the junction, and created the
// missing component on the other side of it as Administrator. The no-follow open
// that came next then found a perfectly ordinary directory at the requested
// pathname, because the caller-controlled redirection had already happened one
// level up, and the elevated write landed outside the sandbox home.
//
// A junction rather than a symlink for the same reason as the sibling test: it
// needs no privilege, so it is reachable by exactly the unprivileged user this
// guards against.
func TestWriteWindowsSandboxSecretRefusesAJunctionedAncestor(t *testing.T) {
base := t.TempDir()
outside := filepath.Join(base, "outside")
if err := os.MkdirAll(outside, 0o700); err != nil {
t.Fatal(err)
}
// home is the junction. The secret is addressed two levels below it, and the
// level in between does not exist, so it has to be created.
home := filepath.Join(base, "home")
makeJunction(t, home, outside)
path := filepath.Join(home, "identity", "zero-sbx-test.secret")
err := writeWindowsSandboxSecret(path, "Zs1!EXAMPLEPASSWORDVALUE")
if err == nil {
t.Error("wrote the principal secret below a junctioned ancestor, so an elevated setup placed it in a tree the caller controls")
}
// The refusal is only half of it: nothing may have been created on the other
// side of the junction, because an elevated create there is a write primitive
// at a path the caller chose even when no secret follows it.
entries, readErr := os.ReadDir(outside)
if readErr != nil {
t.Fatal(readErr)
}
if len(entries) != 0 {
names := []string{}
for _, entry := range entries {
names = append(names, entry.Name())
}
t.Errorf("the junction target gained %v, so an elevated create followed the ancestor", names)
}
}
// The same shape for the runtime root, which is the other elevated pathname
// create in this setup path. Its candidates sit under the invoking user's own
// cache directory, which is to say under a tree the party this sandbox contains
// can rearrange before elevated setup runs.
func TestSetupWindowsSandboxRuntimeRootRefusesAJunctionedAncestor(t *testing.T) {
isolateSandboxRuntimeRoots(t)
cache := t.TempDir()
t.Setenv("LOCALAPPDATA", cache)
t.Setenv("XDG_CACHE_HOME", cache)
workspace := filepath.Join(t.TempDir(), "ws")
if err := os.MkdirAll(workspace, 0o700); err != nil {
t.Fatal(err)
}
config := WindowsSandboxCommandConfig{WorkspaceRoots: []string{workspace}}
candidates := windowsSandboxRuntimeCandidates(config.WorkspaceRoots)
if len(candidates) == 0 {
t.Fatal("SETUP INVALID: no runtime root candidate for a configured workspace")
}
// PICKED BY EXCLUDING THE OTHER ONE, NOT BY PATH PREFIX. The second candidate
// is the shared fallback under the system temp directory, which this test
// must not junction. Selecting the cache-derived one by prefix looks
// equivalent and is not: a CI runner spells one directory two ways
// (RUNNER~1 against runneradmin), so os.UserCacheDir and t.TempDir disagree
// on a path they both mean and the prefix matches nothing.
fallback, _ := fallbackSandboxRuntimeRoot(workspace)
cacheCandidate := ""
for _, candidate := range candidates {
if candidate != fallback {
cacheCandidate = candidate
break
}
}
if cacheCandidate == "" {
t.Fatalf("SETUP INVALID: no cache-derived candidate among %v (fallback %q)", candidates, fallback)
}
// The swap: the candidate's parent is a junction out of the cache tree, and
// the candidate itself does not exist, so it has to be created.
outside := filepath.Join(t.TempDir(), "outside")
if err := os.MkdirAll(outside, 0o700); err != nil {
t.Fatal(err)
}
parent := filepath.Dir(cacheCandidate)
if err := os.MkdirAll(filepath.Dir(parent), 0o700); err != nil {
t.Fatal(err)
}
makeJunction(t, parent, outside)
if _, err := setupWindowsSandboxRuntimeRoot(config); err == nil {
t.Error("created the runtime root below a junctioned ancestor, as an elevated process, in a tree the caller controls")
}
entries, readErr := os.ReadDir(outside)
if readErr != nil {
t.Fatal(readErr)
}
if len(entries) != 0 {
names := []string{}
for _, entry := range entries {
names = append(names, entry.Name())
}
t.Errorf("the junction target gained %v, so an elevated create followed the ancestor", names)
}
}
// And an ordinary nested directory is still created, or the refusals above
// prove only that these functions fail.
func TestWriteWindowsSandboxSecretCreatesAMissingChain(t *testing.T) {
base := t.TempDir()
path := filepath.Join(base, "home", "identity", "nested", "zero-sbx-test.secret")
const password = "Zs1!EXAMPLEPASSWORDVALUE"
if err := writeWindowsSandboxSecret(path, password); err != nil {
t.Fatalf("write: %v", err)
}
got, err := readWindowsSandboxSecret(path)
if err != nil {
t.Fatalf("read: %v", err)
}
if got != password {
t.Fatalf("read %q, want the stored password", got)
}
}
@@ -0,0 +1,107 @@
//go:build windows
package sandbox
import (
"errors"
"os"
"path/filepath"
"strings"
"testing"
"golang.org/x/sys/windows"
)
// CLEANUP HAS TO UNDO WHAT CREATE DID, ON THE SAME OBJECT.
//
// Everything between creating the secret file and writing it is handle-relative
// and no-follow. The failure path was not: it called os.Remove on the pathname,
// which is the one resolution the rest of the function exists to avoid, and it
// did not even work. The leaf is created with FILE_SHARE_READ alone, so a delete
// by name while that handle is open is a sharing violation; the error was
// discarded, the directory unwind did not cover the file, and a failed
// provisioning left an empty secret behind that a later run would read as a
// stale password.
func TestWriteWindowsSandboxSecretRemovesTheLeafWhenLockingFails(t *testing.T) {
restore := failWindowsSecretLock(t, errors.New("SetSecurityInfo refused"))
defer restore()
path := filepath.Join(t.TempDir(), "cfg", "zero-sbx-test.secret")
err := writeWindowsSandboxSecret(path, "Zs1!EXAMPLEPASSWORDVALUE")
if err == nil {
t.Fatal("SETUP INVALID: the injected lock failure was not reported")
}
if !strings.Contains(err.Error(), "SetSecurityInfo refused") {
t.Fatalf("err = %v, want the injected cause", err)
}
if _, statErr := os.Stat(path); !errors.Is(statErr, os.ErrNotExist) {
t.Fatalf("the secret file survived a failed lock (stat: %v); a later run would read it as a stale password", statErr)
}
// The directory this attempt created goes too, which is the half that
// already worked and must keep working.
if _, statErr := os.Stat(filepath.Dir(path)); !errors.Is(statErr, os.ErrNotExist) {
t.Errorf("the directory chain this attempt created was left behind (stat: %v)", statErr)
}
}
// AND A CLEANUP THAT CANNOT FINISH SAYS SO. Leftover state after a failed
// provisioning is the caller's business, and an empty secret file is exactly
// what a later run would mistake for a stored password.
//
// The delete is injected rather than blocked for real. Making a Windows delete
// fail means arranging a sharing conflict, and my first attempt at that held a
// second handle on the leaf and did not block anything: the cleanup succeeded
// and the test asserted its way to a false negative. A seam says what the code
// does with a failure, which is the thing under test here.
func TestWriteWindowsSandboxSecretReportsAFailedCleanup(t *testing.T) {
restoreLock := failWindowsSecretLock(t, errors.New("SetSecurityInfo refused"))
defer restoreLock()
previousDelete := deleteWindowsSecretLeafFn
deleteWindowsSecretLeafFn = func(windows.Handle, string) error {
return errors.New("STATUS_CANNOT_DELETE")
}
defer func() { deleteWindowsSecretLeafFn = previousDelete }()
path := filepath.Join(t.TempDir(), "cfg", "zero-sbx-test.secret")
err := writeWindowsSandboxSecret(path, "Zs1!EXAMPLEPASSWORDVALUE")
if err == nil {
t.Fatal("SETUP INVALID: the injected lock failure was not reported")
}
if !strings.Contains(err.Error(), "SetSecurityInfo refused") {
t.Errorf("err = %v, want the original cause preserved", err)
}
if !strings.Contains(err.Error(), "remove partially written secret") {
t.Errorf("err = %v, want the failed cleanup reported rather than discarded", err)
}
if !strings.Contains(err.Error(), "STATUS_CANNOT_DELETE") {
t.Errorf("err = %v, want the delete failure carried too", err)
}
}
// The ordinary path is unchanged, or the two refusals above would prove only
// that this function fails.
func TestWriteWindowsSandboxSecretStillStoresAndReadsBack(t *testing.T) {
path := filepath.Join(t.TempDir(), "cfg", "zero-sbx-test.secret")
const password = "Zs1!EXAMPLEPASSWORDVALUE"
if err := writeWindowsSandboxSecret(path, password); err != nil {
t.Fatalf("write: %v", err)
}
got, err := readWindowsSandboxSecret(path)
if err != nil {
t.Fatalf("read: %v", err)
}
if got != password {
t.Fatalf("read %q, want the stored password", got)
}
}
// failWindowsSecretLock makes the DACL step fail for one test.
func failWindowsSecretLock(t *testing.T, cause error) func() {
t.Helper()
previous := lockWindowsSecretHandleToOwnerFn
lockWindowsSecretHandleToOwnerFn = func(windows.Handle, *windows.SID) error { return cause }
return func() { lockWindowsSecretHandleToOwnerFn = previous }
}
@@ -0,0 +1,112 @@
//go:build windows
package sandbox
import (
"fmt"
"unsafe"
"golang.org/x/sys/windows"
)
// createWindowsSecretFileNoFollow creates (or replaces) the secret file as a
// CHILD of a pinned parent handle and returns a handle to it.
//
// The pathname version this replaces resolved the path four separate times in an
// elevated process: MkdirAll, an O_TRUNC open, SetNamedSecurityInfo by name, then
// WriteFile by name. The sandbox home belongs to the invoking user, who is the
// party this sandbox exists to contain, so each of those resolutions was a place
// to swap a component. Worst case an attacker-chosen file gets truncated and then
// has its DACL rewritten by an Administrator; the milder junction-only case still
// plants the deterministic secret somewhere the caller then owns.
//
// One handle, one resolution. The parent chain is built no-follow by the caller
// and its deepest handle is passed in here, the leaf is created relative to that
// handle so its name can never be resolved again, and both the DACL and the
// bytes are applied to the handle rather than to a path.
//
// FILE_OVERWRITE_IF, not FILE_CREATE: an existing secret must be replaced, since
// a stale password makes LogonUser fail in a way that reads as a sandbox bug.
// FILE_OPEN_REPARSE_POINT means a leaf that IS a reparse point comes back as
// itself rather than being followed, and the attribute check below then refuses
// it instead of writing through it.
func createWindowsSecretFileAt(parent windows.Handle, name string) (windows.Handle, error) {
if err := validateWindowsACLComponent(name); err != nil {
return 0, fmt.Errorf("secret file name: %w", err)
}
objectName, err := windows.NewNTUnicodeString(name)
if err != nil {
return 0, fmt.Errorf("encode secret file name %s: %w", name, err)
}
attributes := windows.OBJECT_ATTRIBUTES{
RootDirectory: parent,
ObjectName: objectName,
Attributes: windows.OBJ_CASE_INSENSITIVE,
}
attributes.Length = uint32(unsafe.Sizeof(attributes))
var handle windows.Handle
var status windows.IO_STATUS_BLOCK
if err := windows.NtCreateFile(
&handle,
// WRITE_DAC to lock it down and FILE_WRITE_DATA to fill it, both through
// this one handle. READ_CONTROL because SetSecurityInfo reads the existing
// descriptor before replacing it, and FILE_READ_ATTRIBUTES because the
// reparse-point check below asks the handle what it landed on.
windows.FILE_WRITE_DATA|windows.FILE_READ_ATTRIBUTES|windows.WRITE_DAC|windows.READ_CONTROL|windows.SYNCHRONIZE,
&attributes,
&status,
nil,
windows.FILE_ATTRIBUTE_NORMAL,
windows.FILE_SHARE_READ,
windows.FILE_OVERWRITE_IF,
windows.FILE_NON_DIRECTORY_FILE|windows.FILE_OPEN_REPARSE_POINT|windows.FILE_SYNCHRONOUS_IO_NONALERT,
0,
0,
); err != nil {
return 0, fmt.Errorf("create secret file %s: %w", name, err)
}
if err := rejectWindowsACLReparseHandle(handle, name); err != nil {
_ = windows.CloseHandle(handle)
return 0, err
}
return handle, nil
}
// lockWindowsSecretHandleToOwner applies the owner-and-SYSTEM-only DACL to an
// open handle instead of to a pathname, so the object being locked is provably
// the object that was just created rather than whatever the name resolves to now.
func lockWindowsSecretHandleToOwner(handle windows.Handle, owner *windows.SID) error {
acl, err := windowsSecretOwnerACL(owner)
if err != nil {
return err
}
if err := windows.SetSecurityInfo(
handle,
windows.SE_FILE_OBJECT,
windows.DACL_SECURITY_INFORMATION|windows.PROTECTED_DACL_SECURITY_INFORMATION,
nil,
nil,
acl,
nil,
); err != nil {
return fmt.Errorf("lock secret to owner: %w", err)
}
return nil
}
// writeWindowsSecretHandle writes the whole payload through the handle.
func writeWindowsSecretHandle(handle windows.Handle, payload []byte) error {
for written := 0; written < len(payload); {
var n uint32
if err := windows.WriteFile(handle, payload[written:], &n, nil); err != nil {
return fmt.Errorf("write secret: %w", err)
}
if n == 0 {
return fmt.Errorf("write secret: wrote no bytes with %d remaining", len(payload)-written)
}
written += int(n)
}
return nil
}
@@ -0,0 +1,71 @@
//go:build windows
package sandbox
import (
"os"
"path/filepath"
"strings"
"testing"
)
// THE SECRET MUST NOT BE WRITTEN THROUGH A REPARSE POINT.
//
// The sandbox home belongs to the invoking user, who is the party this sandbox
// exists to contain, so they can put a junction where the secret directory is
// expected before elevated setup runs. The pathname version resolved the path
// four times over (MkdirAll, an O_TRUNC open, SetNamedSecurityInfo by name, then
// WriteFile by name) and every one of them followed it, so an Administrator
// process created the principal's password in a directory of the caller's
// choosing and then granted them control of it.
//
// A junction rather than a symlink on purpose: it needs no privilege, so it is
// reachable by exactly the unprivileged user this guards against. os.Symlink
// would need SeCreateSymbolicLinkPrivilege and would skip on an ordinary
// developer or CI account, which is where this most needs to run.
func TestWriteWindowsSandboxSecretRefusesAJunctionedDirectory(t *testing.T) {
base := t.TempDir()
outside := filepath.Join(base, "outside")
if err := os.MkdirAll(outside, 0o700); err != nil {
t.Fatalf("MkdirAll: %v", err)
}
// The swap: the directory the secret is addressed into is a junction that
// leads out of the sandbox home. The pathname never changes.
cfg := filepath.Join(base, "cfg")
makeJunction(t, cfg, outside)
path := filepath.Join(cfg, "zero-sbx-test.secret")
err := writeWindowsSandboxSecret(path, "Zs1!EXAMPLEPASSWORDVALUE")
if err == nil {
t.Fatal("wrote the principal secret through a junction, so an elevated setup would have placed it in a directory the caller controls")
}
if !strings.Contains(err.Error(), "reparse") {
t.Fatalf("refused for the wrong reason: %v", err)
}
// Refusing is only half of it. Nothing may survive on the other side, or the
// caller still ends up holding a file the sandbox created for them.
entries, readErr := os.ReadDir(outside)
if readErr != nil {
t.Fatalf("ReadDir: %v", readErr)
}
if len(entries) != 0 {
t.Fatalf("junction target holds %d entries after the refusal, want none", len(entries))
}
}
// The ordinary path must still work, or the refusal above proves only that the
// function fails.
func TestWriteWindowsSandboxSecretStillWritesAnOrdinaryDirectory(t *testing.T) {
path := filepath.Join(t.TempDir(), "cfg", "zero-sbx-test.secret")
const password = "Zs1!EXAMPLEPASSWORDVALUE"
if err := writeWindowsSandboxSecret(path, password); err != nil {
t.Fatalf("write: %v", err)
}
got, err := readWindowsSandboxSecret(path)
if err != nil {
t.Fatalf("read: %v", err)
}
if got != password {
t.Fatalf("read %q, want the stored password", got)
}
}
@@ -0,0 +1,313 @@
//go:build windows
package sandbox
// Storing a sandbox principal's password.
//
// The elevated setup path provisions the account, but the per-command path runs
// UNELEVATED and needs the password to call LogonUser. So the secret has to
// cross that boundary on disk, and the only thing standing between it and the
// sandboxed child is the file's ACL.
//
// The file is locked to the invoking user: an explicit, INHERITANCE-PROTECTED
// DACL granting that user and SYSTEM, and nobody else. The sandbox principal is
// deliberately absent from it, which is the property that matters, because a
// principal that could read this file could mint its own token and the whole
// identity boundary would be decorative. Administrators are not added either;
// an admin can already take ownership, so naming them buys nothing and widens
// the visible grant.
//
// Ordering is load-bearing: the ACL is applied to an EMPTY file before the
// password is written, so the bytes never exist under the directory's inherited
// permissions even briefly.
import (
"errors"
"fmt"
"os"
"path/filepath"
"strings"
"golang.org/x/sys/windows"
)
// windowsSandboxSecretDirName holds per-principal secrets under the Zero config
// directory. Kept in its own directory so the whole set can be removed when the
// sandbox is torn down.
const windowsSandboxSecretDirName = "windows-sandbox"
// windowsSandboxSecretPath returns where a principal's password lives. The
// account name is already sanitised to [a-z0-9-] by windowsSandboxUserName, so
// it cannot escape the directory.
func windowsSandboxSecretPath(configDir string, username string) (string, error) {
if strings.TrimSpace(configDir) == "" {
return "", errors.New("windows sandbox secret: empty config directory")
}
if strings.TrimSpace(username) == "" {
return "", errors.New("windows sandbox secret: empty principal name")
}
// Defence in depth against a caller passing something windowsSandboxUserName
// did not produce: refuse anything with a separator or a parent reference.
if strings.ContainsAny(username, `\/:`) || strings.Contains(username, "..") {
return "", fmt.Errorf("windows sandbox secret: unsafe principal name %q", username)
}
return filepath.Join(configDir, windowsSandboxSecretDirName, username+".secret"), nil
}
// currentTokenUserSID returns the SID of the user this process runs as. Under
// UAC the elevated token keeps the same user SID as the desktop session, so
// setup and the later unelevated command path agree on the owner, which is what
// makes an owner-scoped ACL usable across the elevation boundary.
func currentTokenUserSID() (*windows.SID, error) {
var token windows.Token
if err := windows.OpenProcessToken(windows.CurrentProcess(), windows.TOKEN_QUERY, &token); err != nil {
return nil, fmt.Errorf("open process token: %w", err)
}
defer token.Close()
user, err := token.GetTokenUser()
if err != nil {
return nil, fmt.Errorf("get token user: %w", err)
}
// The SID points into a buffer owned by the Tokenuser, so copy it out before
// that buffer goes away.
copied, err := user.User.Sid.Copy()
if err != nil {
return nil, fmt.Errorf("copy token user SID: %w", err)
}
return copied, nil
}
// windowsSecretOwnerACL builds the explicit, inheritance-protected DACL granting
// only owner and SYSTEM. PROTECTED is what drops any ACE inherited from the
// config directory; without it a permissive parent would still grant access to
// whoever it names.
//
// Returns the ACL rather than applying it, because the caller applies it to an
// open HANDLE. Applying by pathname meant the object being locked was whatever
// the name resolved to at that instant, which is not necessarily the object that
// was just created.
func windowsSecretOwnerACL(owner *windows.SID) (*windows.ACL, error) {
if owner == nil {
return nil, errors.New("windows sandbox secret: nil owner SID")
}
system, err := windows.CreateWellKnownSid(windows.WinLocalSystemSid)
if err != nil {
return nil, fmt.Errorf("resolve SYSTEM SID: %w", err)
}
entries := []windows.EXPLICIT_ACCESS{
{
AccessPermissions: windows.GENERIC_ALL,
AccessMode: windows.GRANT_ACCESS,
Inheritance: windows.NO_INHERITANCE,
Trustee: windows.TRUSTEE{
TrusteeForm: windows.TRUSTEE_IS_SID,
TrusteeType: windows.TRUSTEE_IS_USER,
TrusteeValue: windows.TrusteeValueFromSID(owner),
},
},
{
AccessPermissions: windows.GENERIC_ALL,
AccessMode: windows.GRANT_ACCESS,
Inheritance: windows.NO_INHERITANCE,
Trustee: windows.TRUSTEE{
TrusteeForm: windows.TRUSTEE_IS_SID,
TrusteeType: windows.TRUSTEE_IS_USER,
TrusteeValue: windows.TrusteeValueFromSID(system),
},
},
}
acl, err := windows.ACLFromEntries(entries, nil)
if err != nil {
return nil, fmt.Errorf("build secret ACL: %w", err)
}
return acl, nil
}
// writeWindowsSandboxSecret stores a principal's password readable only by the
// invoking user.
//
// The file is created empty, locked down, and only then written, so the secret
// is never on disk under the directory's inherited ACL. An existing file is
// replaced rather than appended, since a stale password would make LogonUser
// fail in a way that looks like a sandbox bug.
func writeWindowsSandboxSecret(path string, password string) error {
owner, err := currentTokenUserSID()
if err != nil {
return err
}
// THE PARENT CHAIN IS PART OF THE RESOLUTION COUNT. os.MkdirAll walks a
// pathname, so a junction planted on the way down pointed this elevated
// create at a directory of the caller's choosing, and the no-follow open
// below then refused a tree this process had already made outside the
// sandbox home. The chain is built the same way the ACL targets are: from
// the deepest existing ancestor, one component at a time relative to the
// handle above it, with a record of what was created so a later failure
// unwinds exactly that and nothing else.
created, parent, err := makeWindowsACLDirChainNoFollow(filepath.Dir(path))
if err != nil {
if _, unwindErr := rollbackWindowsACLMaterialization(created); unwindErr != nil {
err = errors.Join(err, unwindErr)
}
return fmt.Errorf("create secret directory: %w", err)
}
defer func() { _ = windows.CloseHandle(parent) }()
unwindChain := func(cause error) error {
if _, unwindErr := rollbackWindowsACLMaterialization(created); unwindErr != nil {
return errors.Join(cause, unwindErr)
}
return cause
}
// Sealed BEFORE the file exists, so a failure here leaves nothing on disk at
// all rather than an empty file for someone else to win a race on.
//
// Encrypted to the invoking user on top of the ACL, so a copy taken outside
// the filesystem's enforcement (backup, disk image) is inert. The principal
// name is the entropy, which keeps one principal's blob from authenticating
// another.
sealed, err := protectWindowsSecret(password, windowsSandboxSecretEntropy(path))
if err != nil {
return unwindChain(err)
}
// ONE resolution of the path, not four. The parent chain above was built
// relative to handles, the leaf is created relative to the deepest of them,
// and the DACL and the bytes are both applied to the leaf handle. Resolving
// the name again between any two of those steps is what let a junction or
// symlink swap point an elevated write at a file of the caller's choosing.
leaf := filepath.Base(path)
handle, err := createWindowsSecretFileAt(parent, leaf)
if err != nil {
return unwindChain(err)
}
leafClosed := false
closeLeaf := func() {
if leafClosed {
return
}
leafClosed = true
_ = windows.CloseHandle(handle)
}
defer closeLeaf()
// CLEANUP ACTS ON THE OBJECT THE CREATE MADE, NOT ON THE NAME AGAIN.
//
// This used to call os.Remove(path), which is the one pathname resolution
// the rest of this function was written to remove, and it did not even
// work: the leaf is created with FILE_SHARE_READ alone, so a delete by
// name while this handle is open comes back as a sharing violation. The
// error was discarded, unwindChain rolled back only the directories, and a
// failed provisioning left an empty secret file it believed it had removed.
//
// The handle is closed first and the leaf is then deleted relative to the
// pinned parent, the same way rollbackWindowsACLMaterialization removes
// what it created. Closing first rather than widening the share mask keeps
// the secret file unshareable for delete while it exists, which is the
// narrower of the two ways to make this work.
removeLeaf := func(cause error) error {
closeLeaf()
if deleteErr := deleteWindowsSecretLeafFn(parent, leaf); deleteErr != nil {
// Reported, not discarded: a secret file left behind after a failed
// provisioning is state the caller has to know about, and the empty
// file is the thing a later run would read as a stale password.
cause = errors.Join(cause, fmt.Errorf("remove partially written secret %s: %w", path, deleteErr))
}
return unwindChain(cause)
}
if err := lockWindowsSecretHandleToOwnerFn(handle, owner); err != nil {
return removeLeaf(err)
}
if err := writeWindowsSecretHandle(handle, sealed); err != nil {
return removeLeaf(err)
}
return nil
}
// lockWindowsSecretHandleToOwnerFn is a seam for the one step between creating
// the secret file and writing it, so the cleanup that runs when it fails is
// reachable without an elevated machine or a way to make SetSecurityInfo fail.
var lockWindowsSecretHandleToOwnerFn = lockWindowsSecretHandleToOwner
// deleteWindowsSecretLeafFn is the matching seam for the cleanup itself, so the
// case where cleanup cannot finish is reachable without arranging a Windows
// sharing conflict, which is not something a test can stage reliably.
var deleteWindowsSecretLeafFn = deleteWindowsACLChildFile
// windowsSandboxSecretEntropy derives the DPAPI entropy from the secret's own
// filename, which is the principal name. Deriving it rather than threading the
// name through keeps read and write agreeing by construction.
func windowsSandboxSecretEntropy(path string) string {
return strings.TrimSuffix(filepath.Base(path), ".secret")
}
// Seamed so the permission-denied mapping in readWindowsSandboxSecret is
// testable. Producing a real ERROR_ACCESS_DENIED needs DACL surgery on Windows,
// since a 0000 file is still readable and reading a directory reports
// "Incorrect function", so a test built that way would exercise the platform
// rather than the mapping.
var readWindowsSandboxSecretFile = os.ReadFile
// readWindowsSandboxSecret loads a principal's password. A missing file means
// setup has not run for this workspace, which the caller turns into a fallback
// rather than a hard failure.
func readWindowsSandboxSecret(path string) (string, error) {
data, err := readWindowsSandboxSecretFile(path)
if err != nil {
if os.IsNotExist(err) {
return "", errWindowsSandboxIdentityUnavailable
}
// Permission denied is unavailability, not breakage. The secret's DACL
// names whoever ran setup, so an operator who elevated with a separate
// administrative account, through runas or an over-the-shoulder UAC
// prompt, ends up with a secret their ordinary account cannot open. That
// is the documented fail-soft case: fall back to the restricted token and
// let the warning say so. Treating it as a hard error instead made every
// sandboxed command fail on a machine that was merely set up by a
// different admin, which is a common way to run an elevated setup.
if os.IsPermission(err) {
return "", errWindowsSandboxIdentityUnavailable
}
return "", fmt.Errorf("read sandbox secret: %w", err)
}
if len(data) == 0 {
return "", errWindowsSandboxIdentityUnavailable
}
secret, err := unprotectWindowsSecret(data, windowsSandboxSecretEntropy(path))
if err != nil {
// A blob written by another user, for another principal, or by an older
// build that stored the password in the clear. Report it as unavailable so
// the caller falls back to the restricted token; the next elevated setup
// rewrites the secret in the current format.
return "", errWindowsSandboxIdentityUnavailable
}
if strings.TrimSpace(secret) == "" {
return "", errWindowsSandboxIdentityUnavailable
}
return secret, nil
}
// removeWindowsSandboxSecret deletes a stored password. Called before the
// account itself is removed so a secret never outlives the principal it
// authenticates.
// errWindowsSandboxSecretNotOurs reports a secret this account cannot delete
// because another administrator's setup owns its DACL.
//
// Distinguishable so teardown can carry on. The alternative is what it used to
// do: abort before removing the account, its logon rights, its ACEs and its
// ledger, leaving a fully provisioned principal on the machine because one file
// could not be unlinked.
var errWindowsSandboxSecretNotOurs = errors.New("the sandbox secret belongs to a different administrator's setup")
func removeWindowsSandboxSecret(path string) error {
err := os.Remove(path)
if err == nil || os.IsNotExist(err) {
return nil
}
// The read path already treats permission-denied as unavailability rather
// than breakage, for the reason documented on readWindowsSandboxSecret: an
// operator who elevated with a separate administrative account gets a secret
// their ordinary account cannot open. Removal has to agree. It did not, so on
// exactly those machines teardown stopped at the first file and stranded
// everything after it.
if os.IsPermission(err) {
return fmt.Errorf("%w: %s", errWindowsSandboxSecretNotOurs, path)
}
return fmt.Errorf("remove sandbox secret: %w", err)
}
@@ -0,0 +1,300 @@
//go:build windows
package sandbox
import (
"bytes"
"errors"
"fmt"
"os"
"path/filepath"
"strings"
"testing"
"unsafe"
"golang.org/x/sys/windows"
)
func TestWindowsSandboxSecretRoundTrip(t *testing.T) {
path := filepath.Join(t.TempDir(), "cfg", "zero-sbx-test.secret")
const password = "Zs1!EXAMPLEPASSWORDVALUE"
if err := writeWindowsSandboxSecret(path, password); err != nil {
t.Fatalf("write: %v", err)
}
got, err := readWindowsSandboxSecret(path)
if err != nil {
t.Fatalf("read: %v", err)
}
if got != password {
t.Fatalf("read %q, want the stored password", got)
}
}
// THE security property: the stored password must be readable only by the user
// who owns it. If any other trustee appears in the DACL, and in particular the
// sandbox principal, that account could mint its own token and the identity
// boundary would be worthless.
func TestWindowsSandboxSecretIsLockedToOwner(t *testing.T) {
path := filepath.Join(t.TempDir(), "locked.secret")
if err := writeWindowsSandboxSecret(path, "Zs1!SECRET"); err != nil {
t.Fatalf("write: %v", err)
}
descriptor, err := windows.GetNamedSecurityInfo(
path,
windows.SE_FILE_OBJECT,
windows.DACL_SECURITY_INFORMATION,
)
if err != nil {
t.Fatalf("read back security info: %v", err)
}
dacl, _, err := descriptor.DACL()
if err != nil {
t.Fatalf("read DACL: %v", err)
}
if dacl == nil {
t.Fatal("secret has a nil DACL, which grants everyone access")
}
owner, err := currentTokenUserSID()
if err != nil {
t.Fatalf("owner SID: %v", err)
}
system, err := windows.CreateWellKnownSid(windows.WinLocalSystemSid)
if err != nil {
t.Fatalf("SYSTEM SID: %v", err)
}
entries, err := windowsSecretACEList(dacl)
if err != nil {
t.Fatalf("enumerate ACEs: %v", err)
}
if len(entries) == 0 {
t.Fatal("secret DACL has no ACEs")
}
for _, sid := range entries {
if sid.Equals(owner) || sid.Equals(system) {
continue
}
t.Fatalf("secret DACL grants an unexpected trustee %s; only the owner and SYSTEM may appear", sid)
}
}
// The DACL must be inheritance-protected, otherwise a permissive ACE on the
// config directory would still reach the secret.
func TestWindowsSandboxSecretDaclIsProtected(t *testing.T) {
path := filepath.Join(t.TempDir(), "protected.secret")
if err := writeWindowsSandboxSecret(path, "Zs1!SECRET"); err != nil {
t.Fatalf("write: %v", err)
}
descriptor, err := windows.GetNamedSecurityInfo(path, windows.SE_FILE_OBJECT, windows.DACL_SECURITY_INFORMATION)
if err != nil {
t.Fatalf("read back security info: %v", err)
}
control, _, err := descriptor.Control()
if err != nil {
t.Fatalf("read control bits: %v", err)
}
if control&windows.SE_DACL_PROTECTED == 0 {
t.Fatal("secret DACL is not protected, so inherited ACEs still apply")
}
}
// Rewriting must replace the previous secret rather than append to it, or
// LogonUser would be handed two concatenated passwords.
func TestWindowsSandboxSecretOverwrites(t *testing.T) {
path := filepath.Join(t.TempDir(), "rewrite.secret")
if err := writeWindowsSandboxSecret(path, "Zs1!FIRST"); err != nil {
t.Fatalf("first write: %v", err)
}
if err := writeWindowsSandboxSecret(path, "Zs1!SECOND"); err != nil {
t.Fatalf("second write: %v", err)
}
got, err := readWindowsSandboxSecret(path)
if err != nil {
t.Fatalf("read: %v", err)
}
if got != "Zs1!SECOND" {
t.Fatalf("read %q, want only the newest password", got)
}
}
// A workspace whose setup has not run must report the actionable sentinel so the
// command path falls back to the restricted-token backend instead of failing.
func TestWindowsSandboxSecretMissingIsSentinel(t *testing.T) {
path := filepath.Join(t.TempDir(), "absent.secret")
if _, err := readWindowsSandboxSecret(path); err != errWindowsSandboxIdentityUnavailable {
t.Fatalf("missing secret returned %v, want errWindowsSandboxIdentityUnavailable", err)
}
}
// An empty file is a half-written secret, not a valid empty password.
//
// Both seeds matter and only one of them tests what the name says. A
// zero-length file is the truncated-write case, and it is the only one that
// reaches the length check. Whitespace is several bytes, so it travels on to
// DPAPI and fails to unprotect instead, which is the path
// TestWindowsSandboxSecretRejectsLegacyPlaintext already covers. Seeding only
// the whitespace, as this did, left the branch in the test's own name
// unexercised.
func TestWindowsSandboxSecretEmptyIsSentinel(t *testing.T) {
for name, seed := range map[string][]byte{
"truncated write": {},
"whitespace only": []byte(" \r\n"),
} {
t.Run(name, func(t *testing.T) {
path := filepath.Join(t.TempDir(), "empty.secret")
if err := os.WriteFile(path, seed, 0o600); err != nil {
t.Fatalf("seed: %v", err)
}
if _, err := readWindowsSandboxSecret(path); err != errWindowsSandboxIdentityUnavailable {
t.Fatalf("secret of %d bytes returned %v, want the unavailable sentinel", len(seed), err)
}
})
}
}
// The principal name lands in a filename, so anything that could escape the
// directory has to be refused even though windowsSandboxUserName already
// sanitises its output.
func TestWindowsSandboxSecretPathRejectsTraversal(t *testing.T) {
for _, name := range []string{`..\evil`, "sub/dir", `C:\abs`, "..", ""} {
if _, err := windowsSandboxSecretPath(`C:\cfg`, name); err == nil {
t.Fatalf("principal name %q was accepted", name)
}
}
if _, err := windowsSandboxSecretPath("", "zero-sbx-a"); err == nil {
t.Fatal("empty config directory was accepted")
}
path, err := windowsSandboxSecretPath(`C:\cfg`, "zero-sbx-abc")
if err != nil {
t.Fatalf("valid name rejected: %v", err)
}
if !strings.HasSuffix(path, `zero-sbx-abc.secret`) {
t.Fatalf("unexpected secret path %q", path)
}
}
// Removal must be idempotent so teardown converges the same way provisioning
// does, and must actually delete the secret.
func TestWindowsSandboxSecretRemoveIsIdempotent(t *testing.T) {
path := filepath.Join(t.TempDir(), "gone.secret")
if err := writeWindowsSandboxSecret(path, "Zs1!SECRET"); err != nil {
t.Fatalf("write: %v", err)
}
if err := removeWindowsSandboxSecret(path); err != nil {
t.Fatalf("first remove: %v", err)
}
if _, err := os.Stat(path); !os.IsNotExist(err) {
t.Fatalf("secret still present after removal (stat err %v)", err)
}
if err := removeWindowsSandboxSecret(path); err != nil {
t.Fatalf("removing an absent secret must succeed, got %v", err)
}
}
// windowsSecretACEList returns the trustee SID of every ACE in a DACL so a test
// can assert exactly who is named.
func windowsSecretACEList(dacl *windows.ACL) ([]*windows.SID, error) {
var out []*windows.SID
for index := uint32(0); index < uint32(dacl.AceCount); index++ {
var ace *windows.ACCESS_ALLOWED_ACE
if err := windows.GetAce(dacl, index, &ace); err != nil {
return nil, err
}
// GetAce hands back a generic ACE_HEADER and we reinterpret it. That is
// only sound for the fixed-layout types: an object ACE carries Flags and
// two GUIDs ahead of the trustee, so SidStart would land mid-structure
// and Copy would read whatever bytes happen to be there. The caller's
// "unexpected trustee" assertion would then print a nonsense SID instead
// of naming the ACE that does not belong, which is the opposite of what
// a failing test should do. Nothing under test builds anything but
// allowed ACEs today, so this exists to keep the failure legible if that
// ever changes.
if ace.Header.AceType != windows.ACCESS_ALLOWED_ACE_TYPE {
return nil, fmt.Errorf("ACE %d has type %d, want ACCESS_ALLOWED_ACE_TYPE (%d); refusing to decode its trustee", index, ace.Header.AceType, windows.ACCESS_ALLOWED_ACE_TYPE)
}
sid := (*windows.SID)(unsafe.Pointer(&ace.SidStart))
copied, err := sid.Copy()
if err != nil {
return nil, err
}
out = append(out, copied)
}
return out, nil
}
// DPAPI round-trip through the real store, which needs no privilege and so is
// genuine coverage rather than a gated stub.
func TestWindowsSandboxSecretRoundTripsThroughDPAPI(t *testing.T) {
path, err := windowsSandboxSecretPath(t.TempDir(), "zero-sbx-roundtrip")
if err != nil {
t.Fatalf("secret path: %v", err)
}
const password = "S0me-Sandbox-P@ssw0rd-value"
if err := writeWindowsSandboxSecret(path, password); err != nil {
t.Fatalf("write secret: %v", err)
}
got, err := readWindowsSandboxSecret(path)
if err != nil {
t.Fatalf("read secret: %v", err)
}
if got != password {
t.Fatalf("round-trip returned %q, want %q", got, password)
}
// The point of the exercise: the password must not be recoverable by reading
// the file, or the encryption layer is decorative.
raw, err := os.ReadFile(path)
if err != nil {
t.Fatalf("read raw secret file: %v", err)
}
if bytes.Contains(raw, []byte(password)) {
t.Fatal("the password appears verbatim in the stored file; it was not encrypted")
}
}
// Entropy is the principal name, so a blob moved onto another principal's secret
// path must fail to decrypt rather than authenticate the wrong account.
func TestWindowsSandboxSecretDoesNotTransferBetweenPrincipals(t *testing.T) {
home := t.TempDir()
minePath, err := windowsSandboxSecretPath(home, "zero-sbx-mine")
if err != nil {
t.Fatalf("secret path: %v", err)
}
theirsPath, err := windowsSandboxSecretPath(home, "zero-sbx-theirs")
if err != nil {
t.Fatalf("secret path: %v", err)
}
if err := writeWindowsSandboxSecret(minePath, "a-password-for-mine"); err != nil {
t.Fatalf("write secret: %v", err)
}
blob, err := os.ReadFile(minePath)
if err != nil {
t.Fatalf("read blob: %v", err)
}
if err := os.WriteFile(theirsPath, blob, 0o600); err != nil {
t.Fatalf("plant blob: %v", err)
}
if _, err := readWindowsSandboxSecret(theirsPath); !errors.Is(err, errWindowsSandboxIdentityUnavailable) {
t.Fatalf("a blob planted at another principal's path decrypted; got err = %v", err)
}
}
// An older plaintext secret must degrade to a fallback rather than being handed
// to LogonUser as if it were a password.
func TestWindowsSandboxSecretRejectsLegacyPlaintext(t *testing.T) {
path, err := windowsSandboxSecretPath(t.TempDir(), "zero-sbx-legacy")
if err != nil {
t.Fatalf("secret path: %v", err)
}
if err := os.MkdirAll(filepath.Dir(path), 0o700); err != nil {
t.Fatalf("mkdir: %v", err)
}
if err := os.WriteFile(path, []byte("plaintext-password"), 0o600); err != nil {
t.Fatalf("write legacy secret: %v", err)
}
if _, err := readWindowsSandboxSecret(path); !errors.Is(err, errWindowsSandboxIdentityUnavailable) {
t.Fatalf("legacy plaintext secret was accepted; got err = %v", err)
}
}
File diff suppressed because it is too large. Load diff
@@ -0,0 +1,513 @@
//go:build windows
package sandbox
import (
"errors"
"fmt"
"os"
"path/filepath"
"strings"
"testing"
"unsafe"
"golang.org/x/sys/windows"
)
// A local Windows account name is capped at 20 characters, so the derived name
// must truncate rather than produce a name NetUserAdd rejects.
func TestWindowsSandboxUserNameRespectsLengthLimit(t *testing.T) {
name := windowsSandboxUserName(strings.Repeat("a", 64), windowsSandboxRoleOffline)
if len(name) > windowsSandboxUserNameMax {
t.Fatalf("name %q is %d chars, want at most %d", name, len(name), windowsSandboxUserNameMax)
}
if !strings.HasPrefix(name, windowsSandboxUserPrefix) {
t.Fatalf("name %q lost the managed prefix", name)
}
}
// The same workspace must map to the same principal, otherwise re-running setup
// would accumulate a new local account every time.
func TestWindowsSandboxUserNameIsStable(t *testing.T) {
first := windowsSandboxUserName("abc123", windowsSandboxRoleOffline)
second := windowsSandboxUserName("abc123", windowsSandboxRoleOffline)
if first != second {
t.Fatalf("name is not stable: %q vs %q", first, second)
}
if other := windowsSandboxUserName("def456", windowsSandboxRoleOffline); other == first {
t.Fatalf("different workspaces produced the same principal %q", first)
}
}
// The key is sanitised to characters a local account name accepts, so a hash or
// path fragment cannot smuggle a separator or a space into the name.
func TestWindowsSandboxUserNameRejectsUnsafeCharacters(t *testing.T) {
name := windowsSandboxUserName(`C:\Users\me\proj ect`, windowsSandboxRoleOffline)
for _, r := range strings.TrimPrefix(name, windowsSandboxUserPrefix) {
isLower := r >= 'a' && r <= 'z'
isDigit := r >= '0' && r <= '9'
if !isLower && !isDigit {
t.Fatalf("name %q contains unsafe rune %q", name, r)
}
}
if name == windowsSandboxUserPrefix {
t.Fatal("sanitising removed every character, leaving a bare prefix")
}
}
// An empty or fully-sanitised-away key must still yield a usable name rather
// than the bare prefix.
func TestWindowsSandboxUserNameHandlesEmptyKey(t *testing.T) {
for _, key := range []string{"", "///", " "} {
if got := windowsSandboxUserName(key, windowsSandboxRoleOffline); got == windowsSandboxUserPrefix {
t.Fatalf("key %q produced a bare prefix", key)
}
}
}
// The password must be fresh per call and carry the character classes a default
// Windows complexity policy demands, or NetUserAdd fails with ERROR_PASSWORD_RESTRICTION.
func TestNewWindowsSandboxPasswordIsRandomAndComplex(t *testing.T) {
first, err := newWindowsSandboxPassword()
if err != nil {
t.Fatalf("generate: %v", err)
}
second, err := newWindowsSandboxPassword()
if err != nil {
t.Fatalf("generate: %v", err)
}
if first == second {
t.Fatal("two generated passwords are identical, so they are not random")
}
if len(first) < 12 {
t.Fatalf("password is only %d chars", len(first))
}
var hasUpper, hasLower, hasDigit bool
for _, r := range first {
switch {
case r >= 'A' && r <= 'Z':
hasUpper = true
case r >= 'a' && r <= 'z':
hasLower = true
case r >= '0' && r <= '9':
hasDigit = true
}
}
if !hasUpper || !hasLower || !hasDigit {
t.Fatalf("password %q lacks a required character class", first)
}
}
// "Already exists" is the normal result of re-running setup and must not surface
// as an error, while a genuine failure must.
func TestNetAPIStatusTreatsExistingAsSuccess(t *testing.T) {
if err := netAPIStatus("NetUserAdd", nerrSuccess); err != nil {
t.Fatalf("success status returned %v", err)
}
if err := netAPIStatus("NetUserAdd", nerrUserExists, nerrUserExists); err != nil {
t.Fatalf("existing user must be success, got %v", err)
}
if err := netAPIStatus("NetLocalGroupAdd", nerrGroupExists, nerrGroupExists, errorAliasExists); err != nil {
t.Fatalf("existing group must be success, got %v", err)
}
if err := netAPIStatus("NetUserAdd", 2245); err == nil {
t.Fatal("an unexpected status must surface as an error")
}
}
// Access-denied is the status an unelevated run gets, and it must say so rather
// than reporting a bare number the user cannot act on.
func TestNetAPIStatusExplainsAccessDenied(t *testing.T) {
err := netAPIStatus("NetUserAdd", errorAccessDenied32)
if err == nil {
t.Fatal("access denied must be an error")
}
if !strings.Contains(err.Error(), "elevated") {
t.Fatalf("error %q should point at elevation", err)
}
}
// The Win32 structs are passed to netapi32 as raw buffers, so their layout must
// match what the API expects. A wrong size means silent memory corruption.
func TestWindowsIdentityStructLayouts(t *testing.T) {
ptr := unsafe.Sizeof(uintptr(0))
if got, want := unsafe.Sizeof(localGroupMembersInfo3{}), ptr; got != want {
t.Fatalf("LOCALGROUP_MEMBERS_INFO_3 size = %d, want %d", got, want)
}
if got, want := unsafe.Sizeof(localGroupInfo1{}), 2*ptr; got != want {
t.Fatalf("LOCALGROUP_INFO_1 size = %d, want %d", got, want)
}
// USER_INFO_1 is four pointers plus three DWORDs, with the compiler padding
// each DWORD pair up to pointer alignment on amd64.
if got := unsafe.Sizeof(userInfo1{}); got < 4*ptr {
t.Fatalf("USER_INFO_1 size = %d, smaller than its four pointer fields", got)
}
if unsafe.Offsetof(userInfo1{}.Password) != ptr {
t.Fatal("USER_INFO_1.Password must directly follow Name")
}
}
// LSA_UNICODE_STRING counts BYTES, not runes, and excludes the NUL terminator
// from Length while including it in MaximumLength. Getting either wrong makes
// LsaAddAccountRights read past the buffer or silently match no right, so pin it.
func TestNewLSAStringUsesByteLengths(t *testing.T) {
buffer, err := windows.UTF16FromString("SeBatchLogonRight")
if err != nil {
t.Fatalf("encode: %v", err)
}
entry := newLSAString(buffer)
const runes uint16 = uint16(len("SeBatchLogonRight"))
if entry.Length != runes*2 {
t.Fatalf("Length = %d, want %d (bytes, excluding NUL)", entry.Length, runes*2)
}
if entry.MaximumLength != (runes+1)*2 {
t.Fatalf("MaximumLength = %d, want %d (bytes, including NUL)", entry.MaximumLength, (runes+1)*2)
}
if entry.Buffer == nil {
t.Fatal("Buffer must point at the encoded string")
}
}
// An empty buffer must not produce a struct pointing at nothing with a nonzero
// length, which would hand LSA a wild pointer.
func TestNewLSAStringHandlesEmptyBuffer(t *testing.T) {
entry := newLSAString(nil)
if entry.Buffer != nil || entry.Length != 0 || entry.MaximumLength != 0 {
t.Fatalf("empty buffer produced %+v, want a zero value", entry)
}
}
// The LSA structs are passed to advapi32 as raw buffers, so their sizes must
// match the Win32 definitions.
func TestLSAStructLayouts(t *testing.T) {
ptr := unsafe.Sizeof(uintptr(0))
// LSA_UNICODE_STRING: two uint16 then a pointer, padded to pointer alignment.
if got, want := unsafe.Sizeof(lsaUnicodeString{}), 2*ptr; got != want {
t.Fatalf("LSA_UNICODE_STRING size = %d, want %d", got, want)
}
if unsafe.Offsetof(lsaUnicodeString{}.Buffer) != ptr {
t.Fatal("LSA_UNICODE_STRING.Buffer must sit at the second pointer slot")
}
var attributes lsaObjectAttributes
if unsafe.Sizeof(attributes) < 6*ptr-ptr {
t.Fatalf("LSA_OBJECT_ATTRIBUTES size = %d, smaller than its fields", unsafe.Sizeof(attributes))
}
if unsafe.Offsetof(attributes.ObjectName) == 0 {
t.Fatal("LSA_OBJECT_ATTRIBUTES.ObjectName must not alias Length")
}
}
// Provisioning creates real local accounts, so it only runs when explicitly
// opted into on an elevated machine. Everything above covers the logic that can
// be exercised without touching the account database.
func TestProvisionWindowsSandboxIdentityRoundTrip(t *testing.T) {
if os.Getenv("ZERO_WINDOWS_IDENTITY_PROVISION_TEST") != "1" {
// Spelled out per shell because `set VAR=1` is cmd syntax and silently
// sets a shell variable rather than an environment variable in
// PowerShell, which makes this skip look like the elevation check failing.
t.Skip("provisioning test not enabled: PowerShell `$env:ZERO_WINDOWS_IDENTITY_PROVISION_TEST = \"1\"`, cmd `set ZERO_WINDOWS_IDENTITY_PROVISION_TEST=1`, bash `export ZERO_WINDOWS_IDENTITY_PROVISION_TEST=1` (also needs an elevated terminal)")
}
if !windowsProcessIsElevated() {
t.Skip("provisioning requires an elevated process")
}
// Starting clean keeps a failure here from being explained by residue from a
// previous run. Provisioning no longer resets an adopted account's password,
// so a leftover account would otherwise be adopted with a password this test
// never learns.
_ = removeWindowsSandboxIdentity(windowsSandboxUserName("ziptest01", windowsSandboxRoleOffline), "ziptest01")
identity, password, _, err := provisionWindowsSandboxIdentity("ziptest01", windowsSandboxRoleOffline)
if err != nil {
t.Fatalf("provision: %v", err)
}
// Registered immediately after provisioning so every failure path below is
// covered. This test grants a real batch-logon right to a real local account;
// leaving either behind on a developer machine is not acceptable residue, and
// rights are revoked before the account so nothing is left keyed to a SID that
// no longer resolves.
t.Cleanup(func() {
if err := revokeWindowsSandboxLogonRights(identity.SID); err != nil {
t.Errorf("cleanup: revoke logon rights: %v", err)
}
if err := removeWindowsSandboxIdentity(identity.Username, "ziptest01"); err != nil && !errors.Is(err, errWindowsSandboxForeignAccountRetained) {
t.Errorf("cleanup: remove principal: %v", err)
}
})
if identity.SID == nil {
t.Fatal("provisioned identity has no SID")
}
if password == "" {
t.Fatal("provisioning returned an empty password")
}
// Re-running must converge on the same principal rather than failing or
// creating a second account.
again, secondPassword, _, err := provisionWindowsSandboxIdentity("ziptest01", windowsSandboxRoleOffline)
if err != nil {
t.Fatalf("second provision: %v", err)
}
if again.Username != identity.Username || !again.SID.Equals(identity.SID) {
t.Fatalf("provisioning is not idempotent: %s then %s", identity, again)
}
if secondPassword == "" {
t.Fatal("second provision returned an empty password")
}
// Deliberately NOT logging on with secondPassword. Provisioning does not
// rotate an adopted account any more, so that value is a fresh random string
// the account does not hold; rotation happens in
// provisionWindowsSandboxPrincipalForSetup, immediately before the secret is
// written, to keep the window where no stored password authenticates as small
// as possible.
//
// The guarantee worth asserting is therefore the one the setup path makes:
// after it returns, the stored secret logs the principal on. That covers
// rotation, the secret write and the logon right in one assertion, and it is
// the thing a broken re-setup would actually break.
// A SECOND ACCOUNT THIS FIXTURE OWNS, CLEANED UP BY ITS OWN KEY. The key is
// derived from the workspace, so a fixture-owned workspace gives a key no
// other test or developer state can collide with, and cleanup uses that same
// derived key rather than a literal the ownership guard would refuse. It is
// registered the moment ownership exists, before the secret read and the
// logon below can fail, and it only deletes what this run created.
config := WindowsSandboxCommandConfig{
SandboxHome: t.TempDir(),
WorkspaceRoots: []string{filepath.Join(t.TempDir(), "ws")},
}
secondKey := windowsSandboxPrincipalKey(config)
setupIdentity, secondCreated, err := provisionWindowsSandboxPrincipalForSetup(config, windowsSandboxRoleOffline)
if err != nil {
t.Fatalf("setup provision: %v", err)
}
t.Cleanup(func() {
if !secondCreated {
return
}
if err := revokeWindowsSandboxLogonRights(setupIdentity.SID); err != nil {
t.Errorf("revoke logon rights for the second account: %v", err)
}
if err := removeWindowsSandboxIdentity(setupIdentity.Username, secondKey); err != nil {
t.Errorf("remove the second account %s: %v", setupIdentity.Username, err)
}
})
secretPath, err := windowsSandboxSecretPath(config.SandboxHome, setupIdentity.Username)
if err != nil {
t.Fatalf("secret path: %v", err)
}
storedPassword, err := readWindowsSandboxSecret(secretPath)
if err != nil {
t.Fatalf("read stored secret: %v", err)
}
token, err := logonWindowsSandboxPrincipal(setupIdentity.Username, storedPassword)
if err != nil {
t.Fatalf("logon with the secret the setup path stored: %v", err)
}
_ = token.Close()
// Lookup must find what provisioning created.
found, err := lookupWindowsSandboxIdentity("ziptest01", windowsSandboxRoleOffline)
if err != nil {
t.Fatalf("lookup after provision: %v", err)
}
if !found.SID.Equals(identity.SID) {
t.Fatalf("lookup returned %s, want %s", found, identity)
}
}
// The other half of the privileged chain: granting logon rights and actually
// minting a token. Provisioning proves the account exists; this proves it is
// USABLE, which is the part the runner depends on.
//
// The batch logon doubles as the assertion that LsaAddAccountRights worked. A
// LOGON32_LOGON_BATCH logon fails with ERROR_LOGON_TYPE_NOT_GRANTED (1385)
// unless SeBatchLogonRight is actually held, so a token coming back is proof the
// grant landed rather than merely that the call returned success.
//
// Creates a real local account and removes it again, so it is gated the same way
// as the provisioning round-trip.
func TestGrantLogonRightsAndMintPrincipalToken(t *testing.T) {
if os.Getenv("ZERO_WINDOWS_IDENTITY_PROVISION_TEST") != "1" {
t.Skip("provisioning test not enabled: PowerShell `$env:ZERO_WINDOWS_IDENTITY_PROVISION_TEST = \"1\"`, cmd `set ZERO_WINDOWS_IDENTITY_PROVISION_TEST=1`, bash `export ZERO_WINDOWS_IDENTITY_PROVISION_TEST=1` (also needs an elevated terminal)")
}
if !windowsProcessIsElevated() {
t.Skip("granting logon rights requires an elevated process")
}
const key = "ziplogon01"
// A leftover account from an interrupted run would keep its old password,
// which the freshly generated one will not match, so start from a clean slate.
_ = removeWindowsSandboxIdentity(windowsSandboxUserName(key, windowsSandboxRoleOffline), key)
identity, password, _, err := provisionWindowsSandboxIdentity(key, windowsSandboxRoleOffline)
if err != nil {
t.Fatalf("provision: %v", err)
}
t.Cleanup(func() {
// Rights first, then the account: the reverse order strands an LSA entry
// keyed to a SID that no longer resolves.
if err := revokeWindowsSandboxLogonRights(identity.SID); err != nil {
t.Errorf("cleanup: revoke logon rights: %v", err)
}
if err := removeWindowsSandboxIdentity(identity.Username, key); err != nil && !errors.Is(err, errWindowsSandboxForeignAccountRetained) {
t.Errorf("cleanup: remove principal: %v", err)
}
})
// Exercises LsaAddAccountRights, including the LSA_UNICODE_STRING byte-length
// handling that nothing else has run.
if err := grantWindowsSandboxLogonRights(identity.SID); err != nil {
t.Fatalf("grant logon rights: %v", err)
}
// Idempotent: setup re-runs must not fail on rights the account already holds.
if err := grantWindowsSandboxLogonRights(identity.SID); err != nil {
t.Fatalf("granting logon rights twice must succeed: %v", err)
}
token, err := logonWindowsSandboxPrincipal(identity.Username, password)
if err != nil {
t.Fatalf("logon as principal: %v", err)
}
defer token.Close()
// The token must BE the principal. If this came back as the caller, the whole
// identity boundary would be an illusion and reads would still run as the user.
user, err := token.GetTokenUser()
if err != nil {
t.Fatalf("token user: %v", err)
}
if !user.User.Sid.Equals(identity.SID) {
t.Fatalf("token belongs to %s, want the principal %s", user.User.Sid, identity.SID)
}
t.Logf("minted a token for %s", identity)
}
// A workspace with no provisioned principal must report the actionable
// "run setup" error rather than a raw lookup failure, so the command path can
// fall back instead of surfacing a Win32 code.
func TestLookupWindowsSandboxIdentityUnprovisioned(t *testing.T) {
_, err := lookupWindowsSandboxIdentity("nosuchworkspacekey9z", windowsSandboxRoleOffline)
if err == nil {
t.Skip("a principal for this key unexpectedly exists on this machine")
}
if err != errWindowsSandboxIdentityUnavailable {
t.Fatalf("error = %v, want errWindowsSandboxIdentityUnavailable", err)
}
}
// A name that resolves to something other than a user account is a conflict,
// not an absent principal, and must not be reported as "setup has not run": the
// command path treats that sentinel as permission to fall back silently, so
// collapsing the two would hide a squatted account behind a quiet downgrade to
// the restricted token.
//
// Every machine already has well-known non-user names to test against, so this
// needs no privilege and no provisioning.
func TestLookupWindowsSandboxIdentityRejectsNonUserAccount(t *testing.T) {
// Groups that exist on any Windows install. Whichever resolves first is
// enough; localized machines may not carry the English name.
for _, group := range []string{"Administrators", "Users", "Guests"} {
sid, _, accountType, err := windows.LookupSID("", group)
if err != nil || sid == nil {
continue
}
if accountType == windows.SidTypeUser {
continue
}
resolveErr := func() error {
_, err := resolveWindowsSandboxSID(group)
return err
}()
if resolveErr == nil {
t.Fatalf("resolveWindowsSandboxSID(%q) accepted a non-user account (type %d)", group, accountType)
}
// The classification is the part that matters: the sentinel is what
// licenses the command path to fall back silently, so this refusal must
// survive it rather than be folded into it.
if classified := classifyWindowsSandboxLookupError(resolveErr); errors.Is(classified, errWindowsSandboxIdentityUnavailable) {
t.Fatalf("non-user account %q classified as unprovisioned, which would silently downgrade to the restricted token: %v", group, classified)
}
return
}
t.Skip("no well-known non-user account resolved on this machine")
}
// The account name is derived from a workspace hash, not discovered, so it can
// be occupied by a local account that has nothing to do with Zero. Adopting one
// means resetting a stranger's password, so provisioning has to prove ownership
// first and refuse otherwise.
//
// Driven against real accounts every Windows install carries, which are
// definitively not ours. Unprivileged: it only has to establish that they are
// not classified as managed, so nothing is ever created or modified.
func TestWindowsSandboxUserIsManagedRefusesForeignAccounts(t *testing.T) {
checked := 0
for _, name := range []string{"Administrator", "Guest", "DefaultAccount"} {
managed, err := windowsSandboxUserIsManaged(name, "workspacekey")
if err != nil {
// Localized or disabled installs may not carry every one of these.
continue
}
checked++
if managed {
t.Fatalf("%q classified as a Zero sandbox principal; provisioning would reset its password", name)
}
}
if checked == 0 {
t.Skip("no well-known local account could be queried on this machine")
}
// An absent account must answer false rather than error, since provisioning
// asks this question about names that usually do not exist yet.
managed, err := windowsSandboxUserIsManaged("zero-sbx-nosuchacct", "workspacekey")
if err != nil {
t.Fatalf("querying a missing account: %v", err)
}
if managed {
t.Fatal("a missing account was classified as managed")
}
}
// The refusal has to be a typed, recognisable collision rather than a generic
// failure, so setup can say what is wrong instead of reporting a Win32 status.
func TestWindowsSandboxNameCollisionIsTyped(t *testing.T) {
wrapped := fmt.Errorf("%w: %q", errWindowsSandboxNameCollision, "zero-sbx-dexample")
if !errors.Is(wrapped, errWindowsSandboxNameCollision) {
t.Fatal("collision error does not match its sentinel")
}
if !strings.Contains(wrapped.Error(), "not created by Zero") {
t.Fatalf("collision message = %q, want it to say the account is not ours", wrapped.Error())
}
}
// The two roles must never collide onto one account. If they did, the online
// principal would be whatever the offline one is, which means either an approved
// network command silently has no network, or an ordinary command silently has
// one. The second is the dangerous direction.
func TestWindowsSandboxUserNameSeparatesRoles(t *testing.T) {
const key = "abc123"
offline := windowsSandboxUserName(key, windowsSandboxRoleOffline)
online := windowsSandboxUserName(key, windowsSandboxRoleOnline)
if offline == online {
t.Fatalf("both roles produced %q", offline)
}
// Still stable per role, or setup would create a new account every run.
if again := windowsSandboxUserName(key, windowsSandboxRoleOnline); again != online {
t.Fatalf("online name is not stable: %q then %q", online, again)
}
// The role tag has to survive truncation. A very long key is exactly when the
// name is cut to the 20-character limit, and losing the tag there is what
// would collide the roles on precisely the workspaces most likely to hit it.
longKey := strings.Repeat("f", 200)
longOffline := windowsSandboxUserName(longKey, windowsSandboxRoleOffline)
longOnline := windowsSandboxUserName(longKey, windowsSandboxRoleOnline)
if longOffline == longOnline {
t.Fatalf("truncation collided the roles onto %q", longOffline)
}
for _, name := range []string{longOffline, longOnline} {
if len(name) > windowsSandboxUserNameMax {
t.Fatalf("name %q is %d chars, want at most %d", name, len(name), windowsSandboxUserNameMax)
}
}
// Different workspaces still get different accounts within a role.
if other := windowsSandboxUserName("def456", windowsSandboxRoleOffline); other == offline {
t.Fatalf("two workspaces produced the same offline account %q", other)
}
}
@@ -0,0 +1,90 @@
//go:build windows
package sandbox
import (
"testing"
"golang.org/x/sys/windows"
)
// THE UPGRADE HAS TO BE OBSERVABLE, or it is not really there.
//
// windowsSandboxUserIsManaged accepts the old bare account comment and promises
// the workspace key gets stamped on so the bare form can eventually be retired.
// The probe for the legacy comment was seamed and the upgrade itself was not, so
// nothing in the suite could tell whether the call ran: deleting it left
// everything green. This repository has already had a fix silently reverted by a
// later change, which is the failure this pins.
func TestAdoptingALegacyAccountStampsTheWorkspaceKey(t *testing.T) {
stub := func(t *testing.T, legacy bool) *string {
t.Helper()
var upgraded string
prevGroup := ensureWindowsSandboxGroupFn
prevOffline := ensureWindowsSandboxOfflineGroupFn
prevEnsure := ensureWindowsSandboxUserFn
prevManaged := windowsSandboxUserIsManagedFn
prevLegacy := windowsSandboxUserHasLegacyCommentFn
prevPrivileged := windowsSandboxUserIsPrivilegedFn
prevUpgrade := upgradeWindowsSandboxUserCommentFn
prevReset := resetWindowsSandboxUserPasswordFn
prevGroupAdd := addWindowsSandboxUserToGroupFn
prevOfflineAdd := addWindowsSandboxUserToOfflineGroupFn
prevSID := resolveWindowsSandboxSIDFn
t.Cleanup(func() {
ensureWindowsSandboxGroupFn = prevGroup
ensureWindowsSandboxOfflineGroupFn = prevOffline
ensureWindowsSandboxUserFn = prevEnsure
windowsSandboxUserIsManagedFn = prevManaged
windowsSandboxUserHasLegacyCommentFn = prevLegacy
windowsSandboxUserIsPrivilegedFn = prevPrivileged
upgradeWindowsSandboxUserCommentFn = prevUpgrade
resetWindowsSandboxUserPasswordFn = prevReset
addWindowsSandboxUserToGroupFn = prevGroupAdd
addWindowsSandboxUserToOfflineGroupFn = prevOfflineAdd
resolveWindowsSandboxSIDFn = prevSID
})
ensureWindowsSandboxGroupFn = func() error { return nil }
ensureWindowsSandboxOfflineGroupFn = func() error { return nil }
// existed = true: the adoption path, which is the only one that upgrades.
ensureWindowsSandboxUserFn = func(string, string, string) (bool, error) { return true, nil }
windowsSandboxUserIsManagedFn = func(string, string) (bool, error) { return true, nil }
windowsSandboxUserHasLegacyCommentFn = func(string) (bool, error) { return legacy, nil }
windowsSandboxUserIsPrivilegedFn = func(string) (bool, error) { return false, nil }
upgradeWindowsSandboxUserCommentFn = func(_ string, workspaceKey string) error {
upgraded = workspaceKey
return nil
}
resetWindowsSandboxUserPasswordFn = func(string, string) error { return nil }
addWindowsSandboxUserToGroupFn = func(string) error { return nil }
addWindowsSandboxUserToOfflineGroupFn = func(string) error { return nil }
resolveWindowsSandboxSIDFn = func(string) (*windows.SID, error) {
return windows.StringToSid("S-1-5-32-546")
}
return &upgraded
}
t.Run("a legacy comment is upgraded", func(t *testing.T) {
upgraded := stub(t, true)
if _, _, _, err := provisionWindowsSandboxIdentity("workspacekey", windowsSandboxRoleOffline); err != nil {
t.Fatalf("provisionWindowsSandboxIdentity: %v", err)
}
if *upgraded != "workspacekey" {
t.Errorf("the workspace key was never stamped onto the adopted legacy account (got %q); windowsSandboxUserIsManaged goes on accepting the bare comment forever", *upgraded)
}
})
// And an account that already carries the key is left alone, or the
// assertion above would be satisfied by an unconditional rewrite.
t.Run("a current comment is left alone", func(t *testing.T) {
upgraded := stub(t, false)
if _, _, _, err := provisionWindowsSandboxIdentity("workspacekey", windowsSandboxRoleOffline); err != nil {
t.Fatalf("provisionWindowsSandboxIdentity: %v", err)
}
if *upgraded != "" {
t.Errorf("an account that already carried the workspace key was rewritten anyway: %q", *upgraded)
}
})
}
@@ -0,0 +1,108 @@
package sandbox
import (
"errors"
"sort"
"strings"
"testing"
)
// The predecessor of this branch provisioned ONE account per workspace, named
// "zero-sbx-<key>" with no role tag. Splitting the roles changed both names, so
// on an upgraded machine neither role resolves to the account that is actually
// installed. Every other path on this branch then reports the principal as never
// provisioned, and the untagged account keeps its secret, its logon rights, its
// ACEs and its ledger with nothing left that looks for them.
//
// windowsSandboxRoleLegacy exists to reproduce that name exactly so retirement
// can still find it. If its tag ever stops being empty, this stops matching what
// the predecessor wrote and the residue becomes unreachable again.
func TestLegacyRoleReproducesTheUntaggedPredecessorName(t *testing.T) {
// Short enough that the 20-character account-name limit does not truncate,
// so the comparison is against the spelling itself rather than the cap.
const key = "abc123"
legacy := windowsSandboxUserName(key, windowsSandboxRoleLegacy)
if want := windowsSandboxUserPrefix + key; legacy != want {
t.Fatalf("legacy account name = %q, want the pre-split spelling %q", legacy, want)
}
// And the cap still applies to it exactly as it did before the split, since
// the predecessor truncated the same way.
long := windowsSandboxUserName("averylongworkspacekeyindeed", windowsSandboxRoleLegacy)
if len(long) > windowsSandboxUserNameMax {
t.Errorf("legacy name %q is %d characters, over the %d-character limit", long, len(long), windowsSandboxUserNameMax)
}
if tag := windowsSandboxRoleLegacy.roleTag(); tag != "" {
t.Errorf("legacy role tag = %q, want empty; a tag here would stop matching the installed account", tag)
}
// It must not collide with either live role, or retiring the predecessor
// would delete an account this branch is still using.
offline := windowsSandboxUserName(key, windowsSandboxRoleOffline)
online := windowsSandboxUserName(key, windowsSandboxRoleOnline)
for _, live := range []string{offline, online} {
if strings.EqualFold(legacy, live) {
t.Errorf("legacy name %q collides with a live role name %q", legacy, live)
}
}
if strings.EqualFold(offline, online) {
t.Fatalf("the two live roles derived the same account name %q", offline)
}
}
// THE LEGACY ROLE IS RETIRED, NEVER PROVISIONED. It derives the untagged name
// on purpose, so provisioning it would create the very account this branch
// replaced, on every setup, forever. Adding it to the retirement list and the
// provisioning list are one character apart in the source and the difference is
// invisible at a glance, so it is asserted rather than left to review.
func TestSetupNeverProvisionsTheLegacyPrincipal(t *testing.T) {
previous := provisionWindowsSandboxPrincipalForSetupFn
t.Cleanup(func() { provisionWindowsSandboxPrincipalForSetupFn = previous })
var provisioned []windowsSandboxRole
provisionWindowsSandboxPrincipalForSetupFn = func(_ WindowsSandboxCommandConfig, role windowsSandboxRole) (windowsSandboxIdentity, bool, error) {
provisioned = append(provisioned, role)
return windowsSandboxIdentity{}, false, errStopProvisioningForTest
}
// The error stops setup at the first role; what matters is which roles it
// was willing to ask for, and legacy must never be among them.
_, _ = setupWindowsSandboxPrincipal(WindowsSandboxCommandConfig{SandboxHome: t.TempDir()})
for _, role := range provisioned {
if role == windowsSandboxRoleLegacy {
t.Fatalf("setup tried to provision the legacy role, which would recreate the pre-split account: %v", provisioned)
}
}
}
var errStopProvisioningForTest = errors.New("stop provisioning for test")
// Opting out or re-running setup has to retire the predecessor as well as both
// live roles. Retiring only the two this branch knows about is what leaves a
// fully provisioned account on a machine whose marker says it has none.
func TestSetupRetirementCoversTheLegacyPrincipal(t *testing.T) {
previous := removeWindowsSandboxPrincipalForSetupFn
t.Cleanup(func() { removeWindowsSandboxPrincipalForSetupFn = previous })
var retired []string
removeWindowsSandboxPrincipalForSetupFn = func(_ WindowsSandboxCommandConfig, role windowsSandboxRole) error {
retired = append(retired, string(role))
return nil
}
if err := removeWindowsSandboxPrincipalsForSetup(WindowsSandboxCommandConfig{SandboxHome: t.TempDir()}); err != nil {
t.Fatalf("removeWindowsSandboxPrincipalsForSetup: %v", err)
}
sort.Strings(retired)
want := []string{"legacy", "offline", "online"}
if len(retired) != len(want) {
t.Fatalf("retired %v, want all of %v; a role left out keeps its account and everything it owns", retired, want)
}
for index := range want {
if retired[index] != want[index] {
t.Fatalf("retired %v, want %v", retired, want)
}
}
}
+176 -1
View File
@@ -62,15 +62,190 @@ func BuildWindowsNetworkInfraPlan(config WindowsSandboxCommandConfig) (WindowsNe
if err != nil {
return WindowsNetworkPlan{}, err
}
// The offline-marker SID stays first: the setup marker records
// IdentitySIDs[0] as the offline filter identity.
identitySIDs := []string{offlineSID}
// A sandbox principal cannot carry the offline-marker SID, because LogonUser
// builds a token from an account's real group memberships and the marker is a
// synthetic capability SID. So the same filters additionally match a real
// local group that network-denied principals belong to.
//
// Gated on THIS home's opt-in, not merely on the group existing.
//
// The group is machine-global, so keying off its existence meant the first
// workspace to opt in changed the computed plan for every OTHER sandbox home
// on the machine. The plan is hashed into the setup marker and compared on
// every command, so those homes started failing every command with "setup is
// out of date" until each was re-run from an elevated terminal, having never
// opted into anything. Existing markers have to keep validating.
//
// Reading the opt-in instead keeps an opted-out home computing exactly the
// plan it computed before any of this existed. An opted-in home records the
// group in its own marker, and setup and the command path both derive the
// flag from the same environment, so they agree. Opting in AFTER setup does
// invalidate that home's marker, which is correct: it has no principals yet
// and setup is genuinely required.
if windowsSandboxIdentityEnabled(config.Env) && resolveWindowsSandboxOfflineGroupSIDHook != nil {
groupSID, err := resolveWindowsSandboxOfflineGroupSIDHook()
if err != nil {
return WindowsNetworkPlan{}, err
}
if trimmed := strings.TrimSpace(groupSID); trimmed != "" {
identitySIDs = append(identitySIDs, trimmed)
}
}
return WindowsNetworkPlan{
Mode: NetworkDeny,
ProviderKey: windowsWFPProviderKey,
SubLayerKey: windowsWFPSubLayerKey,
IdentitySIDs: []string{offlineSID},
IdentitySIDs: identitySIDs,
Filters: windowsDenyWFPFilterSpecs(),
}, nil
}
// WindowsNetworkPlanForApply returns the plan to INSTALL, which is not always
// the plan a home fingerprints.
//
// The filters are machine-global and every setup installs them by deleting and
// recreating the fixed set. So an opted-OUT setup for workspace B was replacing
// filters that workspace A's opted-in setup had installed, dropping the offline
// group SID as it went. A's offline principal still passed the runtime
// membership check and A's marker still validated, but no filter matched its
// token any more, so a NetworkDeny command in A quietly gained egress. Nothing
// on either side reported anything: B did exactly what it was asked to.
//
// The gate in BuildWindowsNetworkInfraPlan stays as it is, and this is
// deliberately a SEPARATE function rather than a change to it. That gate exists
// because the plan is hashed into each home's setup marker: keying it on the
// group's existence made the first workspace to opt in invalidate every other
// home's marker on the machine, and those homes then failed every command with
// "setup is out of date" having opted into nothing. That has to keep working.
//
// The two questions are simply different. What a home RECORDS is about that
// home's own configuration; what setup INSTALLS is about the machine, where the
// group either exists or does not. Answering both from one plan is what forced a
// choice between stale markers and a silent hole.
//
// The group not existing is the ordinary opted-out machine, and it adds nothing.
//
// A resolution FAILURE is a different answer and is fatal, because the filters
// are replaced wholesale. The earlier reasoning here was that refusing to
// install would trade a partial denial for no denial at all, and that is wrong:
// the alternative to installing is leaving the filters that are already there
// alone. Returning a marker-only plan does not decline to add coverage, it
// actively REMOVES coverage another workspace is relying on. An opted-out home
// skips assertWindowsNetworkPlanCoversOfflineGroup entirely (it is gated on
// provisioned), so this is the only thing between a transient lookup error and
// workspace A silently regaining egress under NetworkDeny.
//
// "Absent" and "could not be read" have to be different answers, which is the
// same distinction the marker/apply split above is built on.
func WindowsNetworkPlanForApply(plan WindowsNetworkPlan, resolveOfflineGroupSID func() (string, error)) (WindowsNetworkPlan, error) {
if resolveOfflineGroupSID == nil {
return plan, nil
}
groupSID, err := resolveOfflineGroupSID()
if err != nil {
return WindowsNetworkPlan{}, fmt.Errorf("resolve the sandbox offline group before replacing the machine network filters: %w", err)
}
trimmed := strings.TrimSpace(groupSID)
if trimmed == "" {
return plan, nil
}
for _, existing := range plan.IdentitySIDs {
if strings.EqualFold(strings.TrimSpace(existing), trimmed) {
return plan, nil
}
}
// Copied rather than appended in place: the caller's plan is what gets
// fingerprinted, and growing its backing array would risk changing the
// recorded plan as a side effect of installing one.
augmented := plan
augmented.IdentitySIDs = append(append([]string{}, plan.IdentitySIDs...), trimmed)
return augmented, nil
}
// WindowsNetworkPlanCoversPrincipals reports whether a plan's block filters name
// the offline group, which is the only thing that makes them apply to a sandbox
// principal.
//
// This exists to be asserted, not consulted. The plan must be built AFTER
// provisioning, because provisioning is what creates the group it resolves; a
// plan built first names only the offline marker and leaves every offline
// principal with an open network while setup reports success. That is a control
// that enforces nothing while claiming to work, and the ordering which prevents
// it is invisible at the call site, so a later refactor can undo it silently.
func WindowsNetworkPlanCoversPrincipals(plan WindowsNetworkPlan, offlineGroupSID string) bool {
offlineGroupSID = strings.TrimSpace(offlineGroupSID)
if offlineGroupSID == "" {
// No group provisioned on this host, so there is no principal for the
// filters to miss and nothing to assert.
return true
}
for _, sid := range plan.IdentitySIDs {
if strings.EqualFold(strings.TrimSpace(sid), offlineGroupSID) {
return true
}
}
return false
}
// assertWindowsNetworkPlanCoversOfflineGroup is the post-provisioning check that
// setup runs before it installs filters and reports success.
//
// It fails closed on every answer that is not a definite yes, because the thing
// it guards is invisible when it goes wrong: filters that do not name the
// offline group leave every offline principal with an open network on a machine
// whose setup marker says it is protected. Nobody sees an error, and the sandbox
// looks correctly installed.
//
// Two answers other than "the plan omits the group" also mean the check did not
// happen and must not be treated as a pass:
//
// - The lookup failed. Whether the group is covered is then unknown, and the
// Win32 reason is worth surfacing: an operator seeing "access is denied"
// knows to re-run elevated.
// - The lookup succeeded and found nothing. ("", nil) means the group does not
// exist, which is the ordinary state BEFORE provisioning and an impossible
// one after it, so here it means the group vanished or was never created.
// WindowsNetworkPlanCoversPrincipals answers true for an empty SID, correctly
// for the pre-provisioning callers that ask it, so the emptiness has to be
// rejected here rather than delegated to it.
//
// provisioned says whether principals were actually provisioned on this run.
// When they were not there is no offline group, no principal carrying it, and
// nothing for the filters to miss, so there is nothing to assert. Running the
// check anyway turns the ordinary opt-out setup into a hard failure, because a
// machine with no group resolves to ("", nil) and the empty-SID rejection below
// is correct only after provisioning.
func assertWindowsNetworkPlanCoversOfflineGroup(plan WindowsNetworkPlan, resolve func() (string, error), provisioned bool) error {
if !provisioned {
return nil
}
if resolve == nil {
return errors.New("sandbox offline group resolver is not wired up, so filter coverage cannot be verified")
}
groupSID, err := resolve()
if err != nil {
return fmt.Errorf("resolve the sandbox offline group after provisioning, so filter coverage cannot be verified: %w", err)
}
if strings.TrimSpace(groupSID) == "" {
return errors.New("the sandbox offline group does not exist after provisioning, so the block filters would not apply to any sandbox principal")
}
if !WindowsNetworkPlanCoversPrincipals(plan, groupSID) {
return errors.New("network block filters do not name the sandbox offline group, so they would not apply to any sandbox principal; the network plan must be built after principals are provisioned")
}
return nil
}
// resolveWindowsSandboxOfflineGroupSIDHook resolves the local group that
// network-denied principals belong to. It is wired up on Windows only, so this
// file stays free of Win32 calls and the plan on other platforms is unchanged.
//
// Returning ("", nil) means the group does not exist yet, which is the state
// before principals have ever been provisioned.
var resolveWindowsSandboxOfflineGroupSIDHook func() (string, error)
// WindowsNetworkInfraHash fingerprints the provisioned (mode-independent) network
// infrastructure so the setup marker validates against the same setup for BOTH
// command modes. It never folds in the per-command network mode.
@@ -0,0 +1,129 @@
package sandbox
import (
"errors"
"strings"
"testing"
)
// The post-provisioning coverage assertion is the last thing standing between a
// mis-ordered plan and a machine that reports a successful setup while every
// offline principal has an open network. It has to fail closed on every way of
// not knowing the answer, not just on a definite negative.
func TestAssertWindowsNetworkPlanCoversOfflineGroupFailsClosed(t *testing.T) {
const groupSID = "S-1-5-32-9999"
covering := WindowsNetworkPlan{IdentitySIDs: []string{"S-1-5-21-marker", groupSID}}
notCovering := WindowsNetworkPlan{IdentitySIDs: []string{"S-1-5-21-marker"}}
lookupFailed := errors.New("look up zero-sandbox-offline: access is denied")
tests := []struct {
name string
plan WindowsNetworkPlan
resolve func() (string, error)
wantErr bool
wantText string
}{
{
name: "plan names the group",
plan: covering,
resolve: func() (string, error) { return groupSID, nil },
},
{
// The finding anandh8x raised: a failed lookup skipped the assertion
// entirely and setup carried on to write a success marker.
name: "lookup fails",
plan: covering,
resolve: func() (string, error) { return "", lookupFailed },
wantErr: true,
wantText: "access is denied",
},
{
// Empty-and-no-error means "the group does not exist", which is a
// legitimate answer BEFORE provisioning and an impossible one after it.
// WindowsNetworkPlanCoversPrincipals answers true for an empty SID, so
// without an explicit check the assertion passes vacuously.
name: "group missing after provisioning",
plan: covering,
resolve: func() (string, error) { return "", nil },
wantErr: true,
wantText: "does not exist",
},
{
name: "whitespace-only SID",
plan: covering,
resolve: func() (string, error) { return " ", nil },
wantErr: true,
wantText: "does not exist",
},
{
name: "plan omits the group",
plan: notCovering,
resolve: func() (string, error) { return groupSID, nil },
wantErr: true,
wantText: "do not name the sandbox offline group",
},
}
for _, test := range tests {
t.Run(test.name, func(t *testing.T) {
err := assertWindowsNetworkPlanCoversOfflineGroup(test.plan, test.resolve, true)
if test.wantErr && err == nil {
t.Fatalf("assertWindowsNetworkPlanCoversOfflineGroup() = nil, want an error so setup rolls back")
}
if !test.wantErr {
if err != nil {
t.Fatalf("assertWindowsNetworkPlanCoversOfflineGroup() = %v, want nil", err)
}
return
}
if !strings.Contains(err.Error(), test.wantText) {
t.Fatalf("error = %q, want it to mention %q so the operator can tell the cases apart", err, test.wantText)
}
})
}
// The lookup failure has to stay unwrapped-comparable: setup logs it and an
// operator needs the underlying Win32 reason, not a flattened string.
err := assertWindowsNetworkPlanCoversOfflineGroup(covering, func() (string, error) { return "", lookupFailed }, true)
if !errors.Is(err, lookupFailed) {
t.Fatalf("errors.Is(err, lookupFailed) = false; the cause was dropped: %v", err)
}
}
// The assert only means something AFTER principals were provisioned. The offline
// group is created inside provisionWindowsSandboxIdentity, which runs only under
// the ZERO_WINDOWS_SANDBOX_IDENTITY opt-in, so on a default machine there is no
// group, no principal, and nothing for the filters to miss.
//
// Rejecting an empty SID is right once provisioning ran (that is the vacuous
// pass anandh8x found) and wrong before it: it turned the ordinary opt-out setup
// into a hard failure, which is the regression jatmn caught on #812.
func TestAssertWindowsNetworkPlanCoversOfflineGroupSkipsWhenNothingWasProvisioned(t *testing.T) {
plan := WindowsNetworkPlan{IdentitySIDs: []string{"S-1-5-21-marker"}}
// The default machine: no group exists, so the resolver reports ("", nil).
if err := assertWindowsNetworkPlanCoversOfflineGroup(plan, func() (string, error) { return "", nil }, false); err != nil {
t.Fatalf("opt-out setup was refused: %v", err)
}
// Same state WITH provisioning claimed: now the missing group is a real fault.
if err := assertWindowsNetworkPlanCoversOfflineGroup(plan, func() (string, error) { return "", nil }, true); err == nil {
t.Fatal("a missing group after provisioning must still fail closed")
}
// Not provisioned must not become a licence to skip a lookup failure either:
// the resolver is never consulted, so a broken lookup cannot matter here.
if err := assertWindowsNetworkPlanCoversOfflineGroup(plan, func() (string, error) {
t.Fatal("the resolver must not be consulted when nothing was provisioned")
return "", nil
}, false); err != nil {
t.Fatalf("opt-out setup was refused: %v", err)
}
}
// A nil resolver is a wiring mistake, and guessing that coverage is fine is the
// one thing it must not do.
func TestAssertWindowsNetworkPlanCoversOfflineGroupRejectsNilResolver(t *testing.T) {
plan := WindowsNetworkPlan{IdentitySIDs: []string{"S-1-5-32-9999"}}
if err := assertWindowsNetworkPlanCoversOfflineGroup(plan, nil, true); err == nil {
t.Fatal("assertWindowsNetworkPlanCoversOfflineGroup(nil resolver) = nil, want an error")
}
}
@@ -0,0 +1,163 @@
package sandbox
import (
"errors"
"strings"
"testing"
)
// THE BLOCK FILTERS ARE MACHINE-GLOBAL, SO ONE WORKSPACE'S SETUP DECIDES ANOTHER
// WORKSPACE'S NETWORK.
//
// Every setup installs them by deleting and recreating one fixed set. The plan
// each home builds names the offline group only when THAT home opted in, which
// is right for the marker it fingerprints and wrong for the filters it installs:
// an ordinary opted-out setup for a second workspace replaced the filters
// without the group SID, and the first workspace's offline principal — still in
// the group, still passing the runtime membership check, still holding a valid
// marker — was no longer matched by any filter. A NetworkDeny command there
// gained egress, silently, because the second setup did exactly what it was
// asked to do.
//
// The plan a home installs and the plan it records are therefore different
// questions, and these pin both.
const testOfflineGroupSID = "S-1-5-32-9990"
func offlineGroupResolver(sid string) func() (string, error) {
return func() (string, error) { return sid, nil }
}
// The regression itself: an opted-OUT home must still install filters covering
// the managed offline group, because an opted-IN home's principals depend on it.
func TestOptedOutSetupKeepsOfflineGroupCoverageForOtherWorkspaces(t *testing.T) {
optedOut, err := BuildWindowsNetworkInfraPlan(WindowsSandboxCommandConfig{
SandboxHome: t.TempDir(),
// No opt-in in the environment: this is the ordinary workspace.
Env: map[string]string{},
})
if err != nil {
t.Fatalf("BuildWindowsNetworkInfraPlan: %v", err)
}
// What this home RECORDS must not change, or every opted-out marker on the
// machine goes stale the moment another workspace opts in.
if WindowsNetworkPlanCoversPrincipals(optedOut, testOfflineGroupSID) {
t.Fatal("the recorded plan named the offline group; that is what invalidated other homes' markers")
}
// What this home INSTALLS must cover the group, since the group exists.
applied, err := WindowsNetworkPlanForApply(optedOut, offlineGroupResolver(testOfflineGroupSID))
if err != nil {
t.Fatalf("WindowsNetworkPlanForApply: %v", err)
}
if !WindowsNetworkPlanCoversPrincipals(applied, testOfflineGroupSID) {
t.Errorf("an opted-out setup would install filters that do not match the offline group, so another workspace's NetworkDeny commands gain egress: %v", applied.IdentitySIDs)
}
// The offline-marker SID has to survive alongside it: the restricted-token
// tier is matched by that one, and it is the whole denial on machines with no
// principals at all.
if len(applied.IdentitySIDs) == 0 || strings.TrimSpace(applied.IdentitySIDs[0]) == "" {
t.Fatalf("the offline-marker SID was lost from the applied plan: %v", applied.IdentitySIDs)
}
if applied.IdentitySIDs[0] != optedOut.IdentitySIDs[0] {
t.Errorf("the marker SID must stay first, since the setup marker records IdentitySIDs[0]: %v", applied.IdentitySIDs)
}
}
// Augmenting must not mutate the plan the caller fingerprints. Appending in
// place would let installing a plan change the plan that was recorded.
func TestPlanForApplyDoesNotMutateTheRecordedPlan(t *testing.T) {
recorded, err := BuildWindowsNetworkInfraPlan(WindowsSandboxCommandConfig{
SandboxHome: t.TempDir(),
Env: map[string]string{},
})
if err != nil {
t.Fatalf("BuildWindowsNetworkInfraPlan: %v", err)
}
before := append([]string{}, recorded.IdentitySIDs...)
if _, err := WindowsNetworkPlanForApply(recorded, offlineGroupResolver(testOfflineGroupSID)); err != nil {
t.Fatalf("WindowsNetworkPlanForApply: %v", err)
}
if len(recorded.IdentitySIDs) != len(before) {
t.Fatalf("the recorded plan grew from %v to %v", before, recorded.IdentitySIDs)
}
for index := range before {
if recorded.IdentitySIDs[index] != before[index] {
t.Errorf("the recorded plan changed at %d: %v vs %v", index, before, recorded.IdentitySIDs)
}
}
}
// An opted-IN home already names the group, and must not name it twice: a
// duplicate identity would change the installed filter set for no reason.
func TestPlanForApplyDoesNotDuplicateAnAlreadyCoveredGroup(t *testing.T) {
plan := WindowsNetworkPlan{IdentitySIDs: []string{"S-1-5-21-marker", testOfflineGroupSID}}
applied, err := WindowsNetworkPlanForApply(plan, offlineGroupResolver(strings.ToLower(testOfflineGroupSID)))
if err != nil {
t.Fatalf("WindowsNetworkPlanForApply: %v", err)
}
if len(applied.IdentitySIDs) != 2 {
t.Errorf("the group was added again despite already being covered: %v", applied.IdentitySIDs)
}
}
// On an ordinary machine with no principals the group does not exist, and the
// plan must be left exactly as it was.
func TestPlanForApplyLeavesAMachineWithoutTheGroupAlone(t *testing.T) {
plan := WindowsNetworkPlan{IdentitySIDs: []string{"S-1-5-21-marker"}}
for _, testCase := range []struct {
name string
resolve func() (string, error)
}{
{name: "no resolver", resolve: nil},
{name: "group absent", resolve: func() (string, error) { return "", nil }},
{name: "blank SID", resolve: func() (string, error) { return " ", nil }},
} {
t.Run(testCase.name, func(t *testing.T) {
applied, err := WindowsNetworkPlanForApply(plan, testCase.resolve)
if err != nil {
t.Fatalf("a machine with no offline group is not a failure: %v", err)
}
if len(applied.IdentitySIDs) != 1 || applied.IdentitySIDs[0] != "S-1-5-21-marker" {
t.Errorf("plan changed on a machine with no offline group: %v", applied.IdentitySIDs)
}
})
}
}
// A LOOKUP FAILURE IS NOT AN ABSENT GROUP. The filters are machine-global and
// are replaced wholesale, so returning a marker-only plan here does not decline
// to add coverage, it removes coverage another workspace is relying on.
//
// This is reachable only from an opted-OUT home, because
// assertWindowsNetworkPlanCoversOfflineGroup is gated on provisioned and never
// runs for one. Workspace A opts in, the group SID lands in the global filters;
// workspace B is opted out and its lookup fails transiently; B installs a plan
// without the group and A's NetworkDeny commands silently regain egress while
// A's marker and its direct membership check both still pass.
func TestPlanForApplyRefusesToReplaceFiltersWhenTheGroupCannotBeRead(t *testing.T) {
// Opted-out home B: the coverage assert is skipped for it, so nothing else
// stands between the failure and the wholesale replace.
if err := assertWindowsNetworkPlanCoversOfflineGroup(
WindowsNetworkPlan{IdentitySIDs: []string{"S-1-5-21-B-marker"}},
func() (string, error) { return "", errors.New("group lookup failed") },
false,
); err != nil {
t.Fatalf("the coverage assert is meant to be skipped for an opted-out home: %v", err)
}
plan := WindowsNetworkPlan{IdentitySIDs: []string{"S-1-5-21-B-marker"}}
applied, err := WindowsNetworkPlanForApply(plan, func() (string, error) {
return "", errors.New("group lookup failed")
})
if err == nil {
t.Fatalf("a failed group lookup installed %v, stripping the offline group from the machine's filters", applied.IdentitySIDs)
}
if !strings.Contains(err.Error(), "group lookup failed") {
t.Errorf("the underlying failure must be reported so the operator can act on it: %v", err)
}
}
+151
View File
@@ -118,3 +118,154 @@ func assertWindowsWFPCommonFilter(t *testing.T, specs map[string]WindowsWFPFilte
// Coverage for the network infra plan + hash and the per-mode token-SID
// composition lives in windows_online_offline_test.go.
// The block filters have to name the offline group as well as the offline-marker
// SID, or a sandbox principal is not covered by them at all: LogonUser builds a
// token from real group memberships and cannot carry the synthetic marker. This
// is the single property that makes network denial work for the principal
// backend, so assert it on the plan rather than trusting the wiring.
func TestNetworkInfraPlanIncludesOfflineGroupIdentity(t *testing.T) {
previous := resolveWindowsSandboxOfflineGroupSIDHook
t.Cleanup(func() { resolveWindowsSandboxOfflineGroupSIDHook = previous })
config := WindowsSandboxCommandConfig{SandboxHome: t.TempDir(), Env: map[string]string{windowsSandboxIdentityEnv: "1"}}
// Before principals have ever been provisioned the group does not exist, and
// the plan must be exactly what it was before this feature. The plan is hashed
// into the setup marker and re-derived on every command, so an identity set
// that appeared out of nowhere would fail every command with "setup is out of
// date".
resolveWindowsSandboxOfflineGroupSIDHook = func() (string, error) { return "", nil }
base, err := BuildWindowsNetworkInfraPlan(config)
if err != nil {
t.Fatalf("build plan without the group: %v", err)
}
if len(base.IdentitySIDs) != 1 {
t.Fatalf("identity SIDs = %v, want only the offline marker when the group is absent", base.IdentitySIDs)
}
const groupSID = "S-1-5-32-9999"
resolveWindowsSandboxOfflineGroupSIDHook = func() (string, error) { return groupSID, nil }
withGroup, err := BuildWindowsNetworkInfraPlan(config)
if err != nil {
t.Fatalf("build plan with the group: %v", err)
}
if len(withGroup.IdentitySIDs) != 2 || withGroup.IdentitySIDs[1] != groupSID {
t.Fatalf("identity SIDs = %v, want the offline marker plus %s", withGroup.IdentitySIDs, groupSID)
}
// The marker records IdentitySIDs[0] as the offline filter identity, so the
// marker SID has to stay first.
if withGroup.IdentitySIDs[0] != base.IdentitySIDs[0] {
t.Fatalf("offline marker moved from position 0: %v", withGroup.IdentitySIDs)
}
// Adding the group must change the fingerprint, or setup and the command path
// could disagree about the installed filters without anything noticing.
baseHash, err := WindowsNetworkInfraHash(base)
if err != nil {
t.Fatalf("hash base: %v", err)
}
groupHash, err := WindowsNetworkInfraHash(withGroup)
if err != nil {
t.Fatalf("hash with group: %v", err)
}
if baseHash == groupHash {
t.Fatal("the infra hash ignored the offline group identity")
}
}
// A lookup failure must not be swallowed into "no group", because that silently
// produces a plan whose filters do not cover sandbox principals.
func TestNetworkInfraPlanPropagatesOfflineGroupLookupFailure(t *testing.T) {
previous := resolveWindowsSandboxOfflineGroupSIDHook
t.Cleanup(func() { resolveWindowsSandboxOfflineGroupSIDHook = previous })
resolveWindowsSandboxOfflineGroupSIDHook = func() (string, error) {
return "", errors.New("boom")
}
if _, err := BuildWindowsNetworkInfraPlan(WindowsSandboxCommandConfig{SandboxHome: t.TempDir(), Env: map[string]string{windowsSandboxIdentityEnv: "1"}}); err == nil {
t.Fatal("a failed offline-group lookup produced a plan; the filters would not cover any principal")
}
}
// The ordering that makes the block filters apply to sandbox principals is
// invisible at the call site: the plan must be built AFTER provisioning,
// because provisioning creates the group the filters name. A plan built first
// names only the offline marker, and a machine would then report a successful
// setup while every offline principal had an open network.
//
// Asserted on the predicate setup checks before installing anything, so moving
// the plan build back ahead of provisioning fails loudly instead of silently
// producing a control that enforces nothing.
func TestNetworkPlanCoverageDetectsPrincipalsLeftUncovered(t *testing.T) {
const groupSID = "S-1-5-32-4242"
// What a plan built BEFORE provisioning looks like: marker only.
tooEarly := WindowsNetworkPlan{IdentitySIDs: []string{"S-1-15-3-1111"}}
if WindowsNetworkPlanCoversPrincipals(tooEarly, groupSID) {
t.Fatal("a plan naming only the offline marker was reported as covering principals; the ordering guard would not fire")
}
// And after: marker plus the group.
correct := WindowsNetworkPlan{IdentitySIDs: []string{"S-1-15-3-1111", groupSID}}
if !WindowsNetworkPlanCoversPrincipals(correct, groupSID) {
t.Fatal("a plan naming the offline group was reported as not covering principals; setup would refuse a correct plan")
}
// SID comparison is case-insensitive, so a differently-cased resolve does not
// read as a missing group and block a valid setup.
mixed := WindowsNetworkPlan{IdentitySIDs: []string{strings.ToLower(groupSID)}}
if !WindowsNetworkPlanCoversPrincipals(mixed, groupSID) {
t.Fatal("case difference read as a missing group")
}
// A host with no group provisioned has no principal to miss, so there is
// nothing to assert and setup must not refuse.
if !WindowsNetworkPlanCoversPrincipals(tooEarly, "") {
t.Fatal("an unprovisioned host was treated as a coverage failure")
}
}
// AN OPTED-OUT HOME MUST KEEP ITS EXISTING MARKER VALID.
//
// The offline group is machine-global. Keyed on its existence, the first
// workspace to opt in changed the computed plan for every OTHER sandbox home on
// the machine, so their stored NetworkInfraHash stopped matching and every one
// of their commands failed with "setup is out of date" until each was re-run
// from an elevated terminal. They had opted into nothing.
//
// The hashes are compared rather than the SID lists because the hash is what the
// marker actually stores and what validation compares.
func TestOfflineGroupDoesNotChangeAnOptedOutHomesInfraHash(t *testing.T) {
previous := resolveWindowsSandboxOfflineGroupSIDHook
t.Cleanup(func() { resolveWindowsSandboxOfflineGroupSIDHook = previous })
optedOut := WindowsSandboxCommandConfig{SandboxHome: t.TempDir()}
// No group on the machine yet: the state before anyone opted in.
resolveWindowsSandboxOfflineGroupSIDHook = nil
before, err := BuildWindowsNetworkInfraPlan(optedOut)
if err != nil {
t.Fatalf("build plan before any opt-in: %v", err)
}
beforeHash, err := WindowsNetworkInfraHash(before)
if err != nil {
t.Fatalf("hash before: %v", err)
}
// Another workspace has now opted in and created the machine-global group.
resolveWindowsSandboxOfflineGroupSIDHook = func() (string, error) {
return "S-1-5-21-1111111111-1111111111-1111111111-4002", nil
}
after, err := BuildWindowsNetworkInfraPlan(optedOut)
if err != nil {
t.Fatalf("build plan after another home opted in: %v", err)
}
afterHash, err := WindowsNetworkInfraHash(after)
if err != nil {
t.Fatalf("hash after: %v", err)
}
if beforeHash != afterHash {
t.Fatalf("another workspace opting in changed this home's infra hash (%s -> %s), so its stored marker stops validating and every command fails until it is re-set-up",
beforeHash, afterHash)
}
}
@@ -0,0 +1,96 @@
//go:build windows
package sandbox
import (
"errors"
"strings"
"testing"
)
// The offline group's SID goes onto the persistent WFP deny filters and the
// sandbox principal is made a member of it. Adopting a same-named group that
// something else owns therefore cuts off every existing member's outbound
// traffic and hands our principal that group's permissions, so an unmarked
// group has to be refused rather than reused.
func TestEnsureWindowsLocalGroupRefusesForeignSameNameGroup(t *testing.T) {
for name, testCase := range map[string]struct {
status uintptr
owned bool
ownedErr error
wantError string
}{
"foreign group with our name": {
status: nerrGroupExists, owned: false,
wantError: "not managed by zero",
},
"foreign group reported via ERROR_ALIAS_EXISTS": {
status: errorAliasExists, owned: false,
wantError: "not managed by zero",
},
"our own group on a re-run": {
status: nerrGroupExists, owned: true,
},
"ownership lookup fails": {
status: nerrGroupExists, ownedErr: errors.New("lookup refused"),
wantError: "lookup refused",
},
"group did not exist": {
status: nerrSuccess,
},
} {
t.Run(name, func(t *testing.T) {
prevAdd, prevOwned := addWindowsLocalGroupFn, windowsLocalGroupOwnedByZeroFn
t.Cleanup(func() {
addWindowsLocalGroupFn = prevAdd
windowsLocalGroupOwnedByZeroFn = prevOwned
})
addWindowsLocalGroupFn = func(string, string) (uintptr, error) { return testCase.status, nil }
lookups := 0
windowsLocalGroupOwnedByZeroFn = func(string, string) (bool, error) {
lookups++
return testCase.owned, testCase.ownedErr
}
err := ensureWindowsSandboxOfflineGroup()
if testCase.wantError == "" {
if err != nil {
t.Fatalf("ensureWindowsSandboxOfflineGroup: %v", err)
}
return
}
if err == nil {
t.Fatalf("adopted a group it should have refused (lookups=%d)", lookups)
}
if !strings.Contains(err.Error(), testCase.wantError) {
t.Fatalf("error = %q, want it to mention %q", err, testCase.wantError)
}
})
}
}
// The marker compared against is the offline group's own comment, not the
// principals group's: two managed groups with different markers must not be
// mistaken for each other.
func TestEnsureWindowsLocalGroupChecksTheGroupsOwnMarker(t *testing.T) {
prevAdd, prevOwned := addWindowsLocalGroupFn, windowsLocalGroupOwnedByZeroFn
t.Cleanup(func() {
addWindowsLocalGroupFn = prevAdd
windowsLocalGroupOwnedByZeroFn = prevOwned
})
addWindowsLocalGroupFn = func(string, string) (uintptr, error) { return nerrGroupExists, nil }
var gotName, gotComment string
windowsLocalGroupOwnedByZeroFn = func(name, comment string) (bool, error) {
gotName, gotComment = name, comment
return true, nil
}
if err := ensureWindowsSandboxOfflineGroup(); err != nil {
t.Fatalf("ensureWindowsSandboxOfflineGroup: %v", err)
}
if gotName != windowsSandboxOfflineGroupName {
t.Fatalf("checked group %q, want %q", gotName, windowsSandboxOfflineGroupName)
}
if gotComment != windowsSandboxOfflineGroupComment {
t.Fatalf("compared marker %q, want %q", gotComment, windowsSandboxOfflineGroupComment)
}
}
@@ -0,0 +1,102 @@
//go:build windows
package sandbox
import (
"errors"
"testing"
"golang.org/x/sys/windows"
)
// Choosing the offline account is only half of what denies it the network: the
// WFP filters match the offline GROUP'S SID. An account that has drifted out of
// that group still logs on from its stored secret, and its token no longer
// satisfies the filter condition — so a no-network profile would get full
// egress. The command path has to re-check the membership, not trust the marker
// setup wrote when it last succeeded.
func TestPrincipalTokenRechecksOfflineGroupMembership(t *testing.T) {
for name, testCase := range map[string]struct {
mode NetworkMode
member bool
memberErr error
wantChecked bool
wantReached bool
wantErr bool
}{
"offline principal drifted out of the group": {
mode: NetworkDeny, member: false,
wantChecked: true, wantReached: false,
},
"offline principal still a member": {
mode: NetworkDeny, member: true,
wantChecked: true, wantReached: true,
},
"membership lookup fails": {
mode: NetworkDeny, memberErr: errors.New("group lookup refused"),
wantChecked: true, wantReached: false, wantErr: true,
},
// An allow-network command uses the online principal, which is not in the
// offline group by design. Checking it there would refuse every approved
// network command.
"online principal is not checked": {
mode: NetworkAllow, member: false,
wantChecked: false, wantReached: true,
},
} {
t.Run(name, func(t *testing.T) {
prevLookup := lookupWindowsSandboxPrincipalForCommandFn
prevMember := windowsSandboxUserInLocalGroupFn
prevSecret := readWindowsSandboxSecretFn
prevWarn := warnWindowsSandboxOfflineMembershipMissing
t.Cleanup(func() {
lookupWindowsSandboxPrincipalForCommandFn = prevLookup
windowsSandboxUserInLocalGroupFn = prevMember
readWindowsSandboxSecretFn = prevSecret
warnWindowsSandboxOfflineMembershipMissing = prevWarn
})
sid, err := windows.CreateWellKnownSid(windows.WinLocalSystemSid)
if err != nil {
t.Fatal(err)
}
lookupWindowsSandboxPrincipalForCommandFn = func(string, windowsSandboxRole) (windowsSandboxIdentity, error) {
return windowsSandboxIdentity{Username: "zero-sbx-test", SID: sid}, nil
}
checkedGroup := ""
windowsSandboxUserInLocalGroupFn = func(_ string, group string) (bool, error) {
checkedGroup = group
return testCase.member, testCase.memberErr
}
secretRead := false
readWindowsSandboxSecretFn = func(string) (string, error) {
secretRead = true
return "", errWindowsSandboxIdentityUnavailable
}
warnWindowsSandboxOfflineMembershipMissing = func(string) {}
config := windowsSandboxTestConfig(t)
config.Env = map[string]string{windowsSandboxIdentityEnv: "1"}
config.PermissionProfile.Network.Mode = testCase.mode
_, ok, err := windowsSandboxPrincipalToken(config)
if testCase.wantErr {
if err == nil {
t.Fatal("a failed membership lookup was swallowed")
}
} else if err != nil {
t.Fatalf("windowsSandboxPrincipalToken: %v", err)
}
_ = ok
if secretRead != testCase.wantReached {
t.Fatalf("reached the secret read = %v, want %v (gate must short-circuit before it)", secretRead, testCase.wantReached)
}
if checked := checkedGroup != ""; checked != testCase.wantChecked {
t.Fatalf("membership checked = %v, want %v", checked, testCase.wantChecked)
}
if testCase.wantChecked && checkedGroup != windowsSandboxOfflineGroupName {
t.Fatalf("checked group %q, want %q", checkedGroup, windowsSandboxOfflineGroupName)
}
})
}
}
@@ -37,9 +37,25 @@ func TestWindowsRuntimeTokenSIDs(t *testing.T) {
// setup serves both modes (and its fingerprint is stable across modes).
func TestBuildWindowsNetworkInfraPlanIsModeIndependent(t *testing.T) {
home := t.TempDir()
// Pinned, because the count below depends on whether this machine happens to
// have the offline group already. BuildWindowsNetworkInfraPlan folds that
// group's SID in when it resolves, so on a Windows host where an earlier
// elevated setup created ZeroSandboxOffline the plan legitimately carries two
// identity SIDs and this test failed on a correct plan. CI never saw it: the
// Linux and macOS jobs leave the hook nil, and a fresh Windows runner has no
// group yet. Stubbing it makes the assertion about the plan rather than about
// the machine it runs on.
previousHook := resolveWindowsSandboxOfflineGroupSIDHook
t.Cleanup(func() { resolveWindowsSandboxOfflineGroupSIDHook = previousHook })
resolveWindowsSandboxOfflineGroupSIDHook = nil
mk := func(mode NetworkMode) WindowsSandboxCommandConfig {
return WindowsSandboxCommandConfig{
SandboxHome: home,
SandboxHome: home,
// Opted in, because the offline group only enters the plan for a home
// that asked for principals. Without this the plan is the pre-principal
// one and the group assertions below have nothing to find.
Env: map[string]string{windowsSandboxIdentityEnv: "1"},
CommandCWD: `C:\ws`,
WorkspaceRoots: []string{`C:\ws`},
PermissionProfile: PermissionProfile{
@@ -72,6 +88,40 @@ func TestBuildWindowsNetworkInfraPlanIsModeIndependent(t *testing.T) {
if denyPlan.IdentitySIDs[0] != offline {
t.Errorf("infra plan SID = %q, want offline-marker %q", denyPlan.IdentitySIDs[0], offline)
}
// Mode independence has to hold on a machine that already has the offline
// group too, which is where the pinned counts above would otherwise be
// asserting something about the host rather than the plan. The group SID is
// folded in for both modes, so the hashes must still agree; only the count
// changes.
resolveWindowsSandboxOfflineGroupSIDHook = func() (string, error) { return "S-1-5-32-9999", nil }
withGroupDeny, err := BuildWindowsNetworkInfraPlan(mk(NetworkDeny))
if err != nil {
t.Fatalf("deny infra plan with the group present: %v", err)
}
withGroupAllow, err := BuildWindowsNetworkInfraPlan(mk(NetworkAllow))
if err != nil {
t.Fatalf("allow infra plan with the group present: %v", err)
}
// Assert the SIDs themselves, not the count. A duplicate offline marker or an
// unrelated SID would satisfy a length check while meaning something quite
// different.
if len(withGroupDeny.IdentitySIDs) != 2 ||
withGroupDeny.IdentitySIDs[0] != offline ||
withGroupDeny.IdentitySIDs[1] != "S-1-5-32-9999" {
t.Fatalf("group present should add its SID after the offline marker, got %v (offline marker %q)", withGroupDeny.IdentitySIDs, offline)
}
groupDenyHash, _ := WindowsNetworkInfraHash(withGroupDeny)
groupAllowHash, _ := WindowsNetworkInfraHash(withGroupAllow)
if groupDenyHash != groupAllowHash || groupDenyHash == "" {
t.Fatalf("infra hash must stay mode-independent with the group present: deny=%q allow=%q", groupDenyHash, groupAllowHash)
}
// And it must differ from the no-group hash, which is the cross-workspace
// coupling called out for a maintainer decision: one workspace creating the
// group changes every other sandbox home's expected fingerprint.
if groupDenyHash == denyHash {
t.Error("group presence did not change the infra hash; the marker staleness this causes is a deliberate property and should be visible here")
}
}
// A pre-existing schema-1 capability file (no Offline SID) is upgraded in place:
@@ -0,0 +1,67 @@
//go:build windows
package sandbox
import (
"os"
"path/filepath"
"strings"
)
// windowsPrincipalIdentityEnvironment rewrites the variables that name WHO the
// command is running as.
//
// The child environment starts life as the invoking user's, and the deliberate
// sandbox redirects only replace HOME, the temp variables and the per-tool cache
// dirs. Everything identifying the account was left alone, so a command running
// as the principal still read USERPROFILE, APPDATA, LOCALAPPDATA, HOMEDRIVE,
// HOMEPATH and USERNAME describing the CALLER, whose profile the principal
// deliberately cannot open. Native tools resolve config and per-user state
// through exactly those, so they either fail during startup or, worse, quietly
// look somewhere they have no business reading.
//
// The values point into the sandbox runtime tree rather than at the principal's
// real Windows profile. That tree is already granted to the principal and
// already holds its caches, so the paths are writable by construction. Naming
// the real profile would need LoadUserProfile to have run, and a variable
// pointing at a directory that does not exist yet is a worse answer than one
// pointing somewhere usable.
//
// Layered UNDER the deliberate redirects: HOME, TMPDIR, TMP and TEMP are not
// touched here, so sandboxRuntimeEnvironment stays the single owner of those.
func windowsPrincipalIdentityEnvironment(env map[string]string, username string, runtime *SandboxRuntime) map[string]string {
username = strings.TrimSpace(username)
if env == nil || username == "" || runtime == nil {
return env
}
base := strings.TrimSpace(runtime.Data)
if base == "" {
base = strings.TrimSpace(runtime.Root)
}
if base == "" {
// No runtime tree means no writable place to point at, and inventing one
// outside the grants would only move the failure. Leaving the caller's
// values would be worse, so name the account and stop there.
env["USERNAME"] = username
return env
}
profile := filepath.Join(base, "profile")
env["USERPROFILE"] = profile
env["APPDATA"] = filepath.Join(profile, "AppData", "Roaming")
env["LOCALAPPDATA"] = filepath.Join(profile, "AppData", "Local")
env["USERNAME"] = username
if host, err := os.Hostname(); err == nil && strings.TrimSpace(host) != "" {
// A local account's domain is the machine. Left as the caller's it would
// name a domain the principal is not a member of.
env["USERDOMAIN"] = host
}
// HOMEDRIVE and HOMEPATH are a split of the same location, and tools join
// them back together, so they have to be split from the value above rather
// than carried over from the caller.
if volume := filepath.VolumeName(profile); volume != "" {
env["HOMEDRIVE"] = volume
env["HOMEPATH"] = strings.TrimPrefix(profile, volume)
}
return env
}
@@ -0,0 +1,90 @@
//go:build windows
package sandbox
import (
"strings"
"testing"
)
// callerEnvironment is the shape the child starts from: the invoking user's
// values, with the deliberate sandbox redirects already layered on top.
func callerEnvironment() map[string]string {
return map[string]string{
"USERPROFILE": `C:\Users\caller`,
"APPDATA": `C:\Users\caller\AppData\Roaming`,
"LOCALAPPDATA": `C:\Users\caller\AppData\Local`,
"HOMEDRIVE": `C:`,
"HOMEPATH": `\Users\caller`,
"USERNAME": "caller",
"USERDOMAIN": "CALLERDOMAIN",
// Owned by sandboxRuntimeEnvironment, and this must not touch them.
"HOME": `C:\runtime\home`,
"TEMP": `C:\runtime\temp`,
"TMP": `C:\runtime\temp`,
}
}
// NOTHING MAY STILL NAME THE CALLER.
//
// A principal is a separate account that deliberately cannot open the invoking
// user's profile, so every variable a native tool resolves per-user state
// through has to describe the principal instead. Left alone they pointed at the
// caller, and tools either failed during startup or looked somewhere they had no
// business reading.
func TestPrincipalEnvironmentStopsNamingTheCaller(t *testing.T) {
runtime := &SandboxRuntime{
Root: `C:\runtime`,
Data: `C:\runtime\data`,
}
env := windowsPrincipalIdentityEnvironment(callerEnvironment(), "zero-sbx-abc123", runtime)
for _, key := range []string{"USERPROFILE", "APPDATA", "LOCALAPPDATA"} {
if strings.Contains(strings.ToLower(env[key]), "caller") {
t.Errorf("%s still points into the caller's profile: %s", key, env[key])
}
if !strings.HasPrefix(strings.ToLower(env[key]), strings.ToLower(runtime.Data)) {
t.Errorf("%s is not inside the runtime tree the principal can write: %s", key, env[key])
}
}
if strings.Contains(strings.ToLower(env["HOMEPATH"]), "caller") {
t.Errorf("HOMEPATH still points into the caller's profile: %s", env["HOMEPATH"])
}
if env["USERNAME"] != "zero-sbx-abc123" {
t.Errorf("USERNAME = %q, want the principal account", env["USERNAME"])
}
if env["USERDOMAIN"] == "CALLERDOMAIN" {
t.Error("USERDOMAIN still names the caller's domain, which the principal is not a member of")
}
// HOMEDRIVE and HOMEPATH are rejoined by tools, so they have to describe the
// same location as USERPROFILE rather than a mix of both identities.
if rejoined := env["HOMEDRIVE"] + env["HOMEPATH"]; rejoined != env["USERPROFILE"] {
t.Errorf("HOMEDRIVE+HOMEPATH = %s, want the same location as USERPROFILE %s", rejoined, env["USERPROFILE"])
}
}
// The deliberate redirects stay owned by sandboxRuntimeEnvironment. Clobbering
// them here would silently move the sandbox's temp and cache handling into a
// second place, which is how the two drift apart.
func TestPrincipalEnvironmentLeavesTheSandboxRedirectsAlone(t *testing.T) {
before := callerEnvironment()
env := windowsPrincipalIdentityEnvironment(callerEnvironment(), "zero-sbx-abc123", &SandboxRuntime{
Root: `C:\runtime`,
Data: `C:\runtime\data`,
})
for _, key := range []string{"HOME", "TEMP", "TMP"} {
if env[key] != before[key] {
t.Errorf("%s = %q, want it left at the sandbox redirect %q", key, env[key], before[key])
}
}
}
// Without a runtime tree there is nowhere writable to point at, and inventing a
// path outside the grants would only move the failure. Naming the account is
// still strictly better than advertising the caller's.
func TestPrincipalEnvironmentWithoutARuntimeTreeStillRenamesTheAccount(t *testing.T) {
env := windowsPrincipalIdentityEnvironment(callerEnvironment(), "zero-sbx-abc123", &SandboxRuntime{})
if env["USERNAME"] != "zero-sbx-abc123" {
t.Errorf("USERNAME = %q, want the principal account even with no runtime tree", env["USERNAME"])
}
}
Loaded 100 of 137 files, more files were not shown because too many files have changed in this diff. Show more