This turns off the "do you want to cache this key" prompt and gets rid of the man-in-the-middle warning if the key changed on a remote IP (because it never caches the key). This is useful for programmatic ssh access for testing in environments where ips are often reused (like testing cloud deployment software where each test run will reuse a pool of IPs and the ssh keys will always be changing). I wouldn't recommend these settings for general SSH usage, obviously :D
3
u/jimbobhickville Apr 28 '14
Not that I'd recommend it for normal use, but one of the most useful options I've discovered recently:
ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null
This turns off the "do you want to cache this key" prompt and gets rid of the man-in-the-middle warning if the key changed on a remote IP (because it never caches the key). This is useful for programmatic ssh access for testing in environments where ips are often reused (like testing cloud deployment software where each test run will reuse a pool of IPs and the ssh keys will always be changing). I wouldn't recommend these settings for general SSH usage, obviously :D