{"version":"2.1.221","anchor":"deny-rules-are-checked-against-every-form-of-a-path","canonical_anchor":"deny-rules-are-checked-against-every-form-of-a-path","heading":"Deny rules are checked against every form of a path","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/deny-rules-are-checked-against-every-form-of-a-path","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Deny rules are checked against every form of a path\n\nYour deny rules now block a path even when it's written a different way.\n\n**What**\n\nA deny rule now matches even when the path is written in a form other than the one that got resolved.\n\n**Details**\n\n- the deny lookup iterates over the path's variants and returns the first matching rule, instead of testing only the single resolved path\n- the drive-relative rejection message now names the original argument when one is available\n- drive-relative paths still require manual approval because they resolve against the per-drive current directory\n\n**Evidence**\n\n`is drive-relative (resolves against the per-drive current directory, which cannot be statically validated) and requires manual approval`\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 0\/5"}