enhance(#3619): ratchet the platform seam with local/no-private-binary-resolution (epic #3411 Phase 3) (#3636)
* chore(#3619): ratchet the platform seam with local/no-private-binary-resolution
Epic #3411 Phase 3, the ratchet. Scope revised with maintainer approval and
recorded on the issue: the epic's literal ask was a rule rejecting a bare-name
spawn outside the seam. Surveyed at ac1b6d679, ~30 such sites exist and none is
a defect — git, gh and npm ship native .exe that CreateProcess resolves unaided,
and the rest are POSIX-only tools. ADR-1703 rules 2 and 3 forbid grandfathering
and escape hatches, so a literal rule would be unsuppressable and would force
rewriting 30 correct calls.
The epic's actual thesis was four private RESOLVERS, not four bare spawns. So
the rule flags re-implementing resolution: reading PATHEXT in any casing from
any object, and a hardcoded list carrying two or more of .exe/.cmd/.bat/.com —
precisely the shapes fallow-runner's candidateNames and gsd-tools' PATHEXT
string had before Phases 1 and 2 deleted them.
Three boundaries were arrived at rather than assumed:
two-or-more a single .endsWith('.cmd') is a classification, not a candidate
set; runtime-hooks-surface derives .cmd shim paths that way
boundary-aware a naive substring test flags .execute and .compacting, caught
on src/host-integration.cts before it could become a false
positive nobody could suppress
suffix-anchored the seam exemption matches src/shell-command-projection.cts
exactly; a substring match would also exempt the dispatch test
file. Case I9 pins it.
PATH scans are deliberately NOT flagged — membership checks (bin/install.js)
are indistinguishable from resolution scans, and an unsound rule in a
zero-escape-hatch architecture is worse than no rule.
To make the ratchet strict with no carve-out, resolveExecutableBinary gained
pathOverride: search THIS PATH, read everything else including PATHEXT from the
ambient environment. resolveFallowBinary now supplies its own search path
without hand-threading PATHEXT, which would itself have been a private read.
The three alternatives were all worse: exempting the file is grandfathering,
exempting the AST shape is a carve-out every future caller must replicate, and
dropping the pass-through would silently ignore a user's real PATHEXT — buying
a lint rule with a correctness regression.
eslint-rules/** is outside the rule's globs rather than exempted, because
portability-vocab.cjs owns the extension set. scripts/**/*.cjs got its own block
so that exclusion does not leave a hole in the ratchet.
Started green with nothing suppressed. Proven able to fail: a fixture with both
signals reports two errors.
Refs #3411
* fix(#3619): close the PATHEXT destructuring evasion and correct two overclaims
Adversarial review found a trivial evasion of the rule's primary signal: the
visitor only handled MemberExpression, so
const { PATHEXT } = process.env
const { PATHEXT: exts } = process.env
const { Pathext } = opts.env
were all unflagged. That is a common idiom, not an exotic bypass. An ObjectPattern
visitor now catches it in every form — renamed, any casing, any receiver, string
keys — while leaving a computed key alone, since it is not statically decidable.
I10-I13 pin the invalid forms and V9/V10 pin PATH and the computed key.
Two overclaims corrected, both mine:
Standards review proved the docs were factually wrong. Both the ADR amendment and
the CONTEXT.md entry asserted that tests/shell-command-projection-dispatch.test.cjs
is still linted by this rule. It is not — the rule's surface is src, gsd-core/bin,
scripts and hooks, and tests/** is deliberately outside it because test setup
legitimately assigns process.env.PATHEXT (fallow-runner's P3 does exactly that).
The suffix-vs-substring distinction is therefore proven by RuleTester case I9
feeding a synthetic filename, NOT by real coverage of that file. Both documents now
say so.
The rule's own docstring claimed the seam exemption matches the seam path
'exactly'. It is a suffix match, so a nested foo/src/shell-command-projection.cts
would also be exempt. Suffix matching is kept — it is how sibling rules resolve
paths and the nested case does not exist — but the docstring now states the
boundary rather than overstating the precision.
The evasion fix was verified by executing eslint against both destructuring forms
in scripts/, not by inspection. Probe: 31/31.
Refs #3411
* chore(#3619): backfill changeset pr number 3636
---------
Co-authored-by: sim <sim@local>
This commit is contained in:
@@ -326,4 +326,43 @@ describe('resolveFallowBinary (#3618)', () => {
|
||||
cleanup(cwd);
|
||||
}
|
||||
});
|
||||
|
||||
// P3 (#3619, epic #3411 Phase 3): resolveFallowBinary switched from
|
||||
// `env: { PATH: envPath, PATHEXT: process.env['PATHEXT'] ?? '' }` to
|
||||
// `pathOverride: envPath` so this module never reads PATHEXT itself (the
|
||||
// shape local/no-private-binary-resolution forbids outside the seam). The
|
||||
// seam's `env` param is left unset, so it defaults to `process.env` inside
|
||||
// resolveExecutableBinary — a REAL ambient process.env.PATHEXT must still
|
||||
// govern win32 resolution exactly as it did before the switch. This is the
|
||||
// row the whole switch could have silently broken.
|
||||
//
|
||||
// PATHEXT is meaningless on POSIX (R21), so per F4's pattern above, BOTH
|
||||
// platform contracts are asserted explicitly rather than skipping either:
|
||||
// a `t.skip()`/bare `return` would make this a vacuous pass on that lane.
|
||||
test('P3: a real ambient process.env.PATHEXT still governs win32 resolution after the env -> pathOverride switch', () => {
|
||||
const cwd = createTempDir();
|
||||
const pathDir = createTempDir();
|
||||
const originalPathext = process.env.PATHEXT;
|
||||
try {
|
||||
process.env.PATHEXT = '.XYZ';
|
||||
const distinctiveFixture = path.join(pathDir, 'fallow.XYZ');
|
||||
fs.writeFileSync(distinctiveFixture, '');
|
||||
const resolved = resolveFallowBinary({ cwd, envPath: pathDir });
|
||||
if (process.platform === 'win32') {
|
||||
// win32: ambient process.env.PATHEXT ('.XYZ') is consulted, so the
|
||||
// distinctively-extensioned fixture resolves — proving the pass-through
|
||||
// was preserved by pathOverride, not silently dropped.
|
||||
assert.equal(resolved, distinctiveFixture);
|
||||
} else {
|
||||
// POSIX: PATHEXT plays no role in resolution at all (resolveExecutableBinary
|
||||
// matches the bare name 'fallow' exactly); a file named 'fallow.XYZ' is not
|
||||
// that name, so nothing is found.
|
||||
assert.equal(resolved, null);
|
||||
}
|
||||
} finally {
|
||||
if (originalPathext === undefined) delete process.env.PATHEXT; else process.env.PATHEXT = originalPathext;
|
||||
cleanup(cwd);
|
||||
cleanup(pathDir);
|
||||
}
|
||||
});
|
||||
});
|
||||
|
||||
Reference in New Issue
Block a user