{"version":"2.1.288","anchor":"read-permission-matching-tightened-for-trailing-whitespace-p","canonical_anchor":"read-permission-matching-tightened-for-trailing-whitespace-p","heading":"Read-deny rules can no longer be dodged with trailing spaces or invisible characters","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/read-permission-matching-tightened-for-trailing-whitespace-p","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Read-deny rules can no longer be dodged with trailing spaces or invisible characters\n\nRead-deny rules now also catch paths with trailing spaces or a trailing invisible byte order mark character\n\n**What**\n\nRead-deny rules are settings that stop Claude from reading certain files. Two ways of slipping a path past them are now closed:\n\n- Paths that end in whitespace are also checked with `\/.` added on the end.\n\n- A trailing byte order mark (U+FEFF, an invisible character) in a path is treated as a space before the check.\n\nBefore, the check used the path only exactly as given.\n\n**Why**\n\nThis hardens deny rules, so a file you have blocked stays blocked even when its path is written in an unusual way.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}