Thank you for your response.In our scenario, we are transmitting the file to a Unix server using Rebex sFTP private key/public key authentication.
Below is a snippet of how we are connecting and transmitting files to the target unix server:
We have now copied the public key to a new Unix server. We are not using any of the server fingerprint/ public key verification commands which you have listed in the previous comment.
So when the file is transmitted to the new Unix server , technically, the transmission should work without any issues correct?
In the security page, it is mentioned that "Server verification is done by checking the server's public key and its signature.
The signature is validated by Rebex SFTP automatically but it's up to you to check the server's public key (or fingerprint)"
Will this Rebex sFTP signature validation detect that the connection is being established with a new Unix server (Eventhough the public key is available on the new server and the server hostname is unchanged) and stop the transmission?