{"version":"2.1.260","anchor":"ambiguous-backslashparenthesis-detection-in-permission-rule","canonical_anchor":"ambiguous-backslashparenthesis-detection-in-permission-rule","heading":"Ambiguous backslash\/parenthesis detection in permission rules","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/ambiguous-backslashparenthesis-detection-in-permission-rule","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### Ambiguous backslash\/parenthesis detection in permission rules\n\nPermission rules with ambiguous backslashes, common in Windows paths, now error clearly instead of misparsing.\n\nPermission rule validation, such as for `Bash(...)` allow\/deny rules, now catches rules where a backslash before a parenthesis is ambiguous, a pattern common in Windows paths, and returns a dedicated error instead of silently misparsing the rule. The error suggests using forward slashes or doubling backslashes and escaping parentheses.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}