On 2026-07-06 14:54:34 +0100, Chris Green wrote: > Well here's one post that I found in a few seconds:- > > > https://linuxvox.com/blog/ssh-on-linux-disabling-host-key-checking-for-hosts-on-local-subnet-known-hosts/
"In *trusted local networks*" but by doing a DNS resolution, you did *not* ensure the use of your local networks. > Yes, it relates to having lots of local ssh hosts on a LAN, that's > basically my situation except for a couple of remote systems. Things can be automatized. But... Also note that by default, ssh does not complain when the host key is not present in the known_hosts file, just when the key has apparently changed (which usually means something bad, unless the machine has been reinstalled). So one needs to be careful only for the first connection to some host. There are also some places where all hosts on the LAN are set up with the same host key (I don't know whether this can be a bad thing), so that strict host checking can easily be enabled by default. -- Vincent Lefèvre <[email protected]> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / Pascaline project (LIP, ENS-Lyon)
