You'll notice
Useful4 Signal2
On Windows and Git Bash, commands you already approved won't be re-prompted by a symlink safety check.
What's wrong with this entry?
Anonymous. No account, no email.
What
The safety layer that could turn an already-allowed Bash command back into a prompt on Windows is gone. That means fewer manual approvals under Windows and Git Bash, and one less check over commands you had previously approved.
Details
- Removed asks include "This previously-approved command runs shell code from a string its security scan cannot see into; on Windows its writes cannot be checked for Cygwin symlink redirection and need human review.", the cd-compound note about Cygwin-emulated symlinks, and "Path traverses a Cygwin-emulated symlink (Git Bash follows it, Node does not)".
- The overlong-command ask, "Command exceeds the maximum analyzable length; its full text cannot be security-scanned and requires human review.", is gone too; only the sed-specific length check remains.
Evidence
on Windows its writes cannot be checked for Cygwin symlink redirection and need human review.
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