The following lines were added (+) and removed (-):
== Disable SSH Host Key Checking ==Do you get tired of... The authenticity of host '192.168.0.10 (192.168.0.10)' can't be established. ECDSA key fingerprint is SHA256:Ncv99ABCdeF/GhIJKlMnOPQ6Abcde0FgHijklMnOp9c. Are you sure you want to continue connecting (yes/no)? Yes it is a security feature to ensure you are not being redirected to a false host in an attempt to steal your password or otherwise invade security. However, sometimes it is, or, often, it is not necessary. On a private LAN, for example, where hosts are not Internet accessible and users are trusted the prompt is more annoying than useful. It also breaks some automation. There are other automation related resolutions but here we will discuss a way to completely disable this security feature. ssh -o "StrictHostKeyChecking=no" 192.168.0.10 ssh -o "UserKnownHostsFile=/dev/null" -o "StrictHostKeyChecking=no" 192.168.0.10If you dont want to have to type it on the command line each time you can make it the default for your user vi ~/.ssh/configadd the following: Host * StrictHostKeyChecking no UserKnownHostsFile=/dev/nullThe file probably doesn't exist. Just create it and add the lines.You can tell it to ignore checking for your lan but still check for other hosts. Host 192.168.0.* StrictHostKeyChecking no UserKnownHostsFile=/dev/nullresource: ShellHacks Blog: [https://www.shellhacks.com/disable-ssh-host-key-checking/ HowTo: Disable SSH Host Key Checking]