{"version":"2.1.265","anchor":"bash-command-permission-checks-thread-through-an-extra-conte","canonical_anchor":"bash-command-permission-checks-thread-through-an-extra-conte","heading":"Bash command permission checks thread through an extra context value","tier":"internal","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/bash-command-permission-checks-thread-through-an-extra-conte","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Bash command permission checks thread through an extra context value\n\nBash command permission checks now receive an extra piece of context when deciding whether to allow a command\n\n**Unclear.** What the added argument (`k(o)`) represents and how it changes permission outcomes is not specified.\n\n**What**\n\nThe internal functions that match a bash (shell) command against permission rules now take an additional context value alongside the command, working directory, and other options they already received.\n\n**Why**\n\nThe finding doesn't specify what the new value carries, so it's not clear what new information now factors into bash permission decisions.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}