{"version":"2.1.232","anchor":"windows-paths-through-cygwin-emulated-symlinks-need-manual-a","canonical_anchor":"windows-paths-through-cygwin-emulated-symlinks-need-manual-a","heading":"Windows: paths through Cygwin-emulated symlinks need manual approval","tier":"notice","area":"Windows","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/windows-paths-through-cygwin-emulated-symlinks-need-manual-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Windows: paths through Cygwin-emulated symlinks need manual approval\n\nOn Windows, file paths that sneak through Cygwin-style symlinks now need your approval or get refused.\n\n**What**\n\nOn 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.\n\n**Details**\n\n- The refusal is marked as not approvable by the permission classifier, so it always goes to you.\n- The branch runs only when the platform is Windows; other platforms are unchanged.\n\n**Evidence**\n\n`Path traverses a Cygwin-emulated symlink (Git Bash follows it, Node does not)`\n\n- Area: Windows\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}