Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Bash PermissionsArea: what it touches
Internal ChangesKind: in v2.1.268,
Internal ChangesSection of the release
Unclear The finding does not explain what a 'bare assignment' command pattern looks like in practice or which specific commands this affects.
What
The 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.
Why
This narrows when a bare-assignment-style permission rule is allowed to match, tightening how such rules are applied to bash commands.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe finding does not explain what a 'bare assignment' command pattern looks like in practice or which specific commands this affects.