Hello, I have a question on the use of WinSCP through the winscp.exe command-line / winscp.com method (if anyone has run into / looked into this).
I have created scripts that wrap this type of command (not yet jumping into the .Net Assembly method, although have looked at it, my background perl / C) with the option, open, ftp put / get, other items into a dynamically built Winscp.com script file (which works well).
One of the options we use with this method, is to obtain the SSH connection public key fingerprint ahead of time (my long-term background also includes Linux / Unix and scripting ssh directly), and feed this to WinSCP.com on a Windows platform into the "-hostkey" command parameter.
Recently I had reason to work with a platform sftp server that was load-balanced, and was getting various results for the fingerprint value of SSH, based on the server I was connecting. Looked into possibly coding some logic with "open" to look at various keys (does winscp.com / winscp.exe have a rc?), but found that if I removed the -hostkey , or even more blatantly replaced it's string with "THISISWRONG"..., it still connects, with no warning, even if I turn option "echo on". Version of Winscp
I see the .Net assembly method seems to have an option to enforce the -hostkey --
Does winscp.com / winscp.exe default to this? GiveUpSecurityAndAcceptAnySshHostKey
Can it be set to enforce at least looking / reporting on different hostkey value it finds (if not the same as what's in -hostkey?)