AClement wrote:

I tried unsuccessfuly to replicate the problem again and learned that after highlighting a stored session name in WinSCP, you must also click the Edit command or the protocol displayed under the SSH tab will revert to the default.

Unless your click Edit all options keep their default value. Not only options on SSH tab.

I tried unsuccessfuly to replicate the problem again and learned that after highlighting a stored session name in WinSCP, you must also click the Edit command or the protocol displayed under the SSH tab will revert to the default.

Clicking the stored session name followed by the Edit command will show the protocol stored with the session. Since there is no problem with WinSCP per se, my logon difficulties were on the host end. However, it might be helpful in future versions for WinSCP to display stored session settings accurately regardless of whether the Edit command has been invoked.

Also can you post a log file?

I'm not able to reproduce this.

What I did:

Start WinSCP
Stored sessions tab shows
Click New
Type in Host name, User name and Password
Select SSH tab
Select 3DES cipher
Press Up twice to get 3DES to the top
Click Save..., type in session name
Login
After login select Commands > Server/protocol Information
"3des" encryption algorithm shows
Exit WinSCP
Start WinSCP
Select previously saved stored session
Click Edit
Select SSH tab
3DES is on the top
Click Login
After login select Commands > Server/protocol Information
"3des" encryption algorithm shows

WinSCP Version 4.1.8 Build 415
When I change encryption policy to 3DES and store the session information, I can log onto my host. However, when I exit WinSCP and start a new session, WinSCP reverts back to the default AES, as a consequence of which my host apparently does not recognize my login information and denies me access.

This is very frustrating. Here's hoping you will fix.