My own solution to this is to store the server key fingerprints in a public Git repository, which can then be pulled from on all devices that need to be able to

My own solution to this is to store the server key fingerprints in a public Git repository, which can then be pulled from on all devices that need to be able to connect. This works nicely for my own personal setup with a few servers. It may be possible to scale this to a larger environment with multiple users too. Then main benefit is that whenever a server is rebuilt (which can be quite regularly when using infra-as-code/infra automation), I don't have to go and manually update every single client that needs to be able to connect. https://www.jamieweb.net/blog/managing-your-ssh-known_hosts-using-git/ https://www.jamieweb.net/blog/managing-your-ssh-known_hosts-...