{"version":"2.1.232","anchor":"sandbox-binary-paths-now-re-prompt-for-consent-when-changed","canonical_anchor":"sandbox-binary-paths-now-re-prompt-for-consent-when-changed","heading":"Sandbox binary paths now re-prompt for consent when changed","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/sandbox-binary-paths-now-re-prompt-for-consent-when-changed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Sandbox binary paths now re-prompt for consent when changed\n\nChanging sandbox binary paths now re-prompts for approval, like status line and hook commands already did.\n\n**What**\n\nThe three sandbox binary paths in settings, `bwrapPath`, `ripgrep` and `socatPath`, are now treated as dangerous settings. Changing any of them invalidates your earlier approval and prompts again, the same as `statusLine`, `processWrapper` and hook commands already did.\n\n**Details**\n\n- The values are read out of the `sandbox` settings object and folded into the payload whose hash the consent check compares against, recorded as `sandbox.bwrapPath` and so on.\n- Effect: a settings file edited by something other than you cannot silently repoint the sandbox helper binaries.\n\n**Evidence**\n\n`bwrapPath`\n\n- Area: Permissions\n- Names: `bwrapPath`, `socatPath`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}