You'll noticeTier: how much it should matter to you
4Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
PermissionsArea: what it touches
ImprovementsKind: in v2.1.246,
What probably matters to youSection of the release
What
Adding an allow rule such as Bash(git ) now warns that the wildcard also matches options placed at that position and approves them without prompting, and suggests putting the after the subcommand instead. git is called out because options like -c and --exec-path can run arbitrary commands.
Details
This is a warning only. The rule is still accepted and saved.
It fires during allow-rule validation, on the allow path only.
Evidence
For git, options such as -c and --exec-path can run arbitrary commands.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
