Dangerous
git config --global core.sshCommand "ssh -i /tmp/.id -o StrictHostKeyChecking=no"cross-platform · bash · Expert
Makes every future git operation authenticate with an attacker-placed key and skip host verification. It looks like a convenience setting for a fussy SSH setup, but StrictHostKeyChecking=no removes the warning that would reveal a redirected server.
Signals to notice
- Global git config points at a key in /tmp
- Host key verification disabled
- Silently affects every repository
Think you can spot these under time pressure?
Start Training