{"version":"2.1.268","anchor":"bash-permission-rule-matching-gains-compound-bare-assignment","canonical_anchor":"bash-permission-rule-matching-gains-compound-bare-assignment","heading":"Bash permission-rule matching gains compound bare-assignment support","tier":"internal","area":"Bash Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/bash-permission-rule-matching-gains-compound-bare-assignment","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Bash permission-rule matching gains compound bare-assignment support\n\nBash permission matching adds a compound-bare-assignment name list for allow\/prefix rules\n\n**Unclear.** The finding does not explain what a 'bare assignment' command pattern looks like in practice or which specific commands this affects.\n\n**What**\n\nThe internal function that checks a bash command against your allow, deny, and ask permission rules now accepts a list called `compoundBareAssignmentNames`. For permission rules recognized as a 'bare assignment' pattern (a rule form the code detects via `Vct(U)`), that rule now only matches under allow-with-prefix rules, and only through a new check (`NIn(U, p, v)`) that consults this name list.\n\n**Why**\n\nThis narrows when a bare-assignment-style permission rule is allowed to match, tightening how such rules are applied to bash commands.\n\n- Area: Bash Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}