Add ability to copy site password

Add the ability to view a site password and/or copy it to the clipboard. In this way the specified site password can be copied and used an another context.

Charles Sorgie wrote:

Add the ability to view a site password and/or copy it to the clipboard. In this way the specified site password can be copied and used an another context.

What do you mean by "view a site password"?

When you use WinSCP scripting you can keep it in %PASSWORD% and use it any where you want in your script.
https://beta.winscp.net/eng/docs/guide_protecting_credentials_for_automation#scripting

For example, following script (example.txt):
can be called from this batch file (“configuration file”):

Charles Sorgie wrote:

Add the ability to view a site password and/or copy it to the clipboard. In this way the specified site password can be copied and used an another context.

See https://beta.winscp.net/eng/docs/faq_password

martin wrote:

Charles Sorgie wrote:

Add the ability to view a site password and/or copy it to the clipboard. In this way the specified site password can be copied and used an another context.

See https://beta.winscp.net/eng/docs/faq_password

I was unaware of (2). Logging > Log Passwords and other sensitive information defeats the changes I made because the HKCU is unencrypted and it can be set maliciously, true?

It seems that /log=<path> overrides the Logging > Log to file path but /loglevel=0 (without the "*") does not override the Log Passwords and other sensitive information preferences setting. How do I prevent the malicious setting of the preference and logging of passwords to a file?

It also seems that I cannot solve the problem by redirecting stdout because the preference specifies a path, true?

I do not understand. If I follow the procedure outlined here:
https://beta.winscp.net/eng/docs/guide_protecting_credentials_for_automation

...then if "Log Passwords and other sensitive information" is set is the password still logged? Is there any way to prevent the logging of passwords even if "Log Passwords and other sensitive information" is set?

It seems that either /loglevel=n without a "*" should suppress password/sensitive logging OR something like /loglevel=n- ought to be supported to suppress it. Do you consider the former not overriding the preferences setting to be a feature or a bug?

A way to ensure in the script that passwords are not logged in the current version regardless of preference settings would be greatly appreciated. Thank you for your help.