I have been attempting to get our automated script to connect to our site hosted.datascope.reuters.com.
When I test the connection with the client, CoreFTP, I AM successful using
Pass: xxxxxx (obscured) and no private key
I am NOT successful if I use the Client WinSCP
OR my automated script.
What I get back as a return value from your server is as follows:
“<?xml version="1.0"?><FTPResults xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><Success>false</Success><Msg>Connection has been unexpectedly closed. Server sent command exit status 0.
Authentication log (see session log for details):
Using username "r9025260".
Authentication failed.</Msg><FileInfo><string xsi:nil="true" /></FileInfo></FTPResults>"
Can you please have someone look at the log for this user and see if it reveals why one way works and the other doesn’t? Each method should be presenting the same public key.
I have tried with latest WinSCP and have been able to connect both FTP and SFTP.
Like OpenSSL, WinSCP uses its own certificate store and prompted me to accept the new certificate - the first time I connected.
I would recommend that you update to the latest version and clear your old cached certificates.
Also, you can refer to this DSS ftp user guide.
Here is the same thing with CURL. You will need to manually import the RSA certificate into the OpenSSL trusted certificates list to avoid using the -k (insecure) switch.
>>>curl -k "sftp://hosted.datascope.reuters.com" --user "r999999:password" drwxr-s--- 6 109011672 30000 6 Mar 23 2017 . drwxr-s--- 6 109011672 30000 6 Mar 23 2017 .. drwxrws--- 2 101 30000 58 Sep 15 10:20 reports drwxr-s--- 3 101 30000 3 Sep 17 2018 feeds drwx------ 2 109011672 30000 2 Mar 23 2017 .ssh drwxrws--- 3 101 30000 3 Mar 23 2017 incoming