You'll notice
Useful3 Signal2
On Windows, file paths that sneak through Cygwin-style symlinks now need your approval or get refused.
What's wrong with this entry?
Anonymous. No account, no email.
What
On Windows only, file permission checks now walk the resolved path for Cygwin-style symlink emulation, including trailing-dot and cookie remainders. If the path really resolves somewhere else, matching deny rules apply first and otherwise the request is refused outright.
Details
- The refusal is marked as not approvable by the permission classifier, so it always goes to you.
- The branch runs only when the platform is Windows; other platforms are unchanged.
Evidence
Path traverses a Cygwin-emulated symlink (Git Bash follows it, Node does not)
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Windows policy helpers can be PowerShell scripts
Both mention window
-
v2.1.234
Windows sandbox refusals now say why an exclusion did not apply
Both mention window
-
v2.1.234
Terminal is restored on Ctrl+Break on Windows
Both mention window