If the master password cannot be supplied on the command line, and a master password has to be supplied to secure the GUI configuration, then don't you end up having to supply the passwords on the open in the script anyway?

Yes. But what's an advantage of encrypting a password with a master password, that you would have to openly supply in the script anyway?

I will consider the DAPI solution.

martin wrote:

In general, we discourage using stored site settings in scripting.
https://winscp.net/eng/docs/scripting#configuration
This would go clearly against that recommendation.

If the master password cannot be supplied on the command line, and a master password has to be supplied to secure the GUI configuration, then don't you end up having to supply the passwords on the open in the script anyway? Either way you can use the technique I described here [https://winscp.net/forum/viewtopic.php?t=24266] it is just whether or not you have to supply it once as the master password or for every site in the URL.

In general, we discourage using stored site settings in scripting.
https://winscp.net/eng/docs/scripting#configuration
This would go clearly against that recommendation.

Add a Master Password switch to the winscp.exe command line so the master password can be specified in scripts.