{"version":"2.1.233","anchor":"windows-cygwin-symlink-re-check-on-approved-bash-commands-dr","canonical_anchor":"windows-cygwin-symlink-re-check-on-approved-bash-commands-dr","heading":"Windows Cygwin-symlink re-check on approved Bash commands dropped","tier":"notice","area":"Windows","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233\/e\/windows-cygwin-symlink-re-check-on-approved-bash-commands-dr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233","markdown":"### Windows Cygwin-symlink re-check on approved Bash commands dropped\n\nOn Windows and Git Bash, commands you already approved won't be re-prompted by a symlink safety check.\n\n**What**\n\nThe 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.\n\n**Details**\n\n- 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)\".\n- 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.\n\n**Evidence**\n\n`on Windows its writes cannot be checked for Cygwin symlink redirection and need human review.`\n\n- Area: Windows\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5"}