I'm getting the same issue and am using WingFTP server version 6.4.0
to push files to it using WinSCP version 5.17.6
and a script that has the WingFTP SSH Key hard coded into the script and an "Open" command like so:
- Code: Select all
open sftp://username:firstname.lastname@example.org/" -hostkey="ssh-rsa 2048 OurWingFTPKey"
when the script runs...WinSCP will produce the following error in the Log File:
7/21/2020 7:05:57 AM Host key fingerprint is:
7/21/2020 7:05:57 AM ssh-rsa 1024 ADifferentFTPKey
7/21/2020 7:05:57 AM Host key does not
match cached key
7/21/2020 7:05:57 AM Host key does not match configured key fingerprint ssh-rsa 2048
7/21/2020 7:05:57 AM Host key fingerprint is ssh-rsa 1024 ADifferentFTPKey
What would cause WingFTP to return an ssh-rsa 1024
key, when what's being sent to connect to WingFTP, is a ssh-rsa 2048
key? This makes no sense.
So specifically, under what circumstances would a connection made to WingFTP that explicitly specifies the key to use, would WingFTP reply and say that the key is now different? This makes no sense, given that the device we're connecting TO the WingFTP server...always comes in on the exact same port and IP.
What makes WingFTP give out a new SSH key that's less strong in this case (1024) than what was sent/requested in the connection that's attempted by WinSCP? For example, could a firewall rule actually be suppressing the higher encryption, which then forces WingFTP to issue a less strong key instead...which then produces the "Host key does not match configured key fingerprint" error?
Looking for some knowledge on this topic. It seems really strange to have this be the case. Thanks!