However, I decided to write an answer. Since there's a question about the log. I wanted to avoid any doubts.
My router is a firewall. Leaf Bering-uClibc (
https://bering-uclibc.zetam.org/wiki/Main_Page and
https://sourceforge.net/projects/leaf/files/Bering-uClibc/)
It has two network cards. For masquerading. I don't want to publish IP addresses from my local network.
So xxx.yyy.zzz.fw is the IP of its network card connected to the local network. And xxx.yyy.zzz.loc1 is the IP number of the computer from which I ran WinSCP.
There were still parts of the log file I didn't understand. Maybe encrypted. Maybe not. Now I entered xxxxxxxxxxxxxxxxxxxxxxxx there. Just in case.
When the firewall starts a communication session, it first asks for a login and password.
Then it launches an application that allows you to change the configuration. You must select something or cancel (q - exit) the changes.
This is the standard solution for this firewall. The same is true when starting a session from a Windows computer using PuTTY.
A login, password, and application waiting for selection. The screenshot taken by this application is in the attached PuTTY.png.
WinSCP also starts a session. He logs in and waits for the application to finish. And the application waits for his selection.
Screenshots of WinSCP are attached: WinSCPstart.jpg, WinSCPstarted.jpg, and WinSCPended.jpg. This last one is how WinSCP lost its patience.
And the WinSCP log is in the attached root@xxx.yyy.zzz.fw.log. And it would be nice if WinSCP chose "q" as, for example, the second (?) password.