dynamic DNS, keys, and timeouts

I am scripting a file transfer solution that needs to be very robust. It will be implemented at several customer sites in a region where communications are very poor, and will run 24x7.

After some research I have selected WinSCP on the client side, WinSSHD on the server side, and SFTP. I have been doing some testing and scripting and so far I am quite pleased with the results.

I am concerned about two possibilities though, that I cannot easily test:

1. Suppose the SSH server has a dynamic IP address and uses dynamic DNS. So WinSCP will connect using a hostname, but in fact the server's public IP address will change (its private IP address will NOT change). When the server's public IP address changes, will the keys become invalid?

2. Can I assume that with default settings, WinSCP will timeout and give up after a reasonable amount of time if (a) it can't establish the connection, or (b) the connection is dropped during a transfer?

Any other suggestions would also be very welcome.

Thank you!

Lee Allen

Anonymous wrote:

1. Suppose the SSH server has a dynamic IP address and uses dynamic DNS. So WinSCP will connect using a hostname, but in fact the server's public IP address will change (its private IP address will NOT change). When the server's public IP address changes, will the keys become invalid?

Do you mean hostkey fingerprint validation?
WinSCP validates the hostkey against the hostname, if possible. So not.
Anyway, you can always specify explicit hostkey fingerprint on command-line:
https://winscp.net/eng/docs/scripting#hostkey

2. Can I assume that with default settings, WinSCP will timeout and give up after a reasonable amount of time if (a) it can't establish the connection, or (b) the connection is dropped during a transfer?

Yes.