{"version":"2.1.233","anchor":"sort-and-uniq-no-longer-get-a-special-write-pre-check","canonical_anchor":"sort-and-uniq-no-longer-get-a-special-write-pre-check","heading":"sort and uniq no longer get a special write pre-check","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233\/e\/sort-and-uniq-no-longer-get-a-special-write-pre-check","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233","markdown":"### `sort` and `uniq` no longer get a special write pre-check\n\nBash permission checks no longer special-case sort and uniq; they default to read access like other commands.\n\n**What**\n\nPath-restricted Bash permission checks stopped extracting `sort`'s `-o`\/`--output=` target and stopped running a separate write-permission deny pass for `sort` and `uniq`. Both now use the generic positional-file handling and default to read access.\n\n**Details**\n\n- The read-only `sed` downgrade, where a sed command judged non-mutating is checked as a read rather than a write, is preserved and now inline.\n\n**Evidence**\n\n`sort contents of files from`\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}