A 499eb494c6 fix(security): use StrictHostKeyChecking=accept-new in all SSH connections (#3037) ... Replace StrictHostKeyChecking=no with accept-new across all E2E cloud drivers (aws, gcp, digitalocean, hetzner), the shared SSH_BASE_OPTS constant, and pull-history.ts. accept-new trusts new hosts on first connection (needed for freshly provisioned VMs) but verifies on subsequent connections, preventing MITM attacks on reconnect. Fixes #3031 Agent: style-reviewer Co-authored-by: B <6723574+louisgv@users.noreply.github.com> Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>		2026-03-26 18:04:40 -07:00
..
cli	fix(security): use StrictHostKeyChecking=accept-new in all SSH connections (#3037)	2026-03-26 18:04:40 -07:00
shared	fix: rethrow normalized Error in tryCatchIf/asyncTryCatchIf (#2930)	2026-03-23 19:33:05 -07:00