You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 3fd1af2
Browse filesBrowse the repository at this point in the historyBrowse files
file-safety: accept a two-dotted directory name under a pin and pin created dirs by their own name
_isInside refused every name beginning with two dots, so a directory named ..cache
sitting under a sole pin read as a walk out of it and the created-directory guard
refused the write. It now refuses only an absolute answer and a traversal segment -
".." alone or ".." as the first segment - and accepts an ordinary child whose name
happens to begin with two dots.
The created-directory guard selected the authorized location by the created
directory's resolved path, so with pins for /ws and /ws/a a created /ws/a/new that
resolves into /ws/other selected the shallower /ws and then passed its own
containment check. Selection is now made by the name the caller pinned
(_deepestPinnedDirectory, which also honours the location a pinned alias was
authorized against) and the resolved directory is only compared against that
selection. The path-form parent branch is untouched.
Regression rows: safeWriteText.spec.ts:2155 (two-dotted name publishes), :2181 (two
pins, shallower resolved pin refused), :2217 (pinned-alias chain still publishes).
The existing created-directory row at :2127 and the UNC row keep refusing the same
scenarios and now assert the message the selection change produces.
Legs: named services selection 4 failed | 100 passed over the head production with
the new rows, 104 passed with the change; prettier 3.9.10 --check . exit 0; knip and
src tsc byte-identical to the same host run at the untouched head.
0 commit comments