Thanks for the advice. What happens is gcp appends a new entry to my known_hosts file (which already has the hostname and key I use) with a very strange looking one, and then fails to connect after doing it once successfully. I am happy to get it right, but at this point, I just don't understand the rewrite and subsequent behavior.
On Tue, Apr 9, 2019 at 10:45 AM vince <[email protected]> wrote: > On Tuesday, April 9, 2019 at 1:57:25 AM UTC-7, Tom Mitchell wrote: >> >> Thanks @gary for the followup. I turned off stricthostkeychecking in the >> .ssh/config file which resolved it. I don't know exactly this cloud server >> does this, but it works and I am not going to dig too deep on it. >> >> >> > That's usually a really bad idea. Strict host checking tries to make sure > that you're not connecting to an imposter computer using the same ip > address as the one you're trying to connect to. What rsync is doing is > saying "hey - I don't know who that remote system is, is this ok?" and > asking for verification. Very normal ssh behavior. > > If you're building a docker container to run weewx, you could have your > container build proces create its ~/.ssh/known_hosts file with the host key > for the system you typically connect to, if you have stable host keys on > the system you're rsync'ing to (which is usually the case). That's a far > more secure way of doing things. > > > > -- > You received this message because you are subscribed to a topic in the > Google Groups "weewx-user" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/weewx-user/qbvL3PX1vDg/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
