{"version":"2.1.317","anchor":"sshscprsyncsftp-command-checks-extended","canonical_anchor":"sshscprsyncsftp-command-checks-extended","heading":"Stricter permission checks for ssh, scp, rsync and sftp commands","tier":"notice","area":"Permissions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/sshscprsyncsftp-command-checks-extended","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Stricter permission checks for ssh, scp, rsync and sftp commands\n\nClaude Code now checks more options and host names in ssh, scp, rsync, rcp and sftp commands before allowing them without asking\n\n**What**\n\nBefore running a shell command without asking you, Claude Code checks whether it is safe. Before, for `ssh` it checked only a few `-o` options: those setting the host name, the user, or a command to run. Now the checks go further:\n\n- `ssh`: all `-o` option values and config keys are checked, and so is the host name.\n\n- `rsync`, `scp`, `rcp` and `sftp`: the options `-e`, `--rsh`, `-o`, `-S`, `-D`, `-F` and `-J` are checked.\n\nA command is refused if one of these options or host names looks suspicious.\n\n**Why**\n\nMore of these remote-access commands are now refused or need your approval instead of running automatically.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}