We cannot hard code passwords into our powershell scripts (that's a security risk).

And why do you think that storing them to WinSCP site is more secure?
Please read this:
https://winscp.net/eng/docs/security_credentials
https://winscp.net/eng/docs/guide_protecting_credentials_for_automation

martin wrote:

Please do, what the message suggests.

Can you give us an example? We cannot hard code passwords into our powershell scripts (that's a security risk). Here is how we do it (example below from our scripts)

$winscpXCmds = ("option echo on","option batch on","option confirm off","option transfer binary","lcd $InputFilePath","open Acct713@sftphost.com","cd $OMNIStmtPath",$("get "+"FINCANCEFILE.gz"),"dir","bye")
$winscpXCmds
$winscpXCmds | winscp.com

Please do, what the message suggests.

Hi,
We need to remove this response (below) from sftp output during our transfers from version 5.13.5, please.

What parameter or patch can do this?

Reason: This output advice-message response is causing confusion when reviewing logs with our auditors when running our jobs.
Your help is appreciate.
Thanks
-Keith

Example output:
In scripting you should not rely on saved sites, use this command instead:
open sftp://mdlive:***@sftp-uat.gbophb.org/ -hostkey="ssh-rsa 1536 QB7AnCdt