Previously if setting a Windows terminal to "Windows Console Host", running the client.exe application and connecting to wolfSSHd (also running on Windows) the virtual terminal control sequences were not all handled well. Leading to the cursor jumping around in the terminal. This change makes use of Windows processing of virtual terminal control sequences instead.
I wasn't sure what you meant by "setting a Windows terminal to 'Windows Console Host'", so I ran conhost.exe and used the client from there. Some hand-holding comments in the future would help.
ZD17595
Previously if setting a Windows terminal to "Windows Console Host", running the client.exe application and connecting to wolfSSHd (also running on Windows) the virtual terminal control sequences were not all handled well. Leading to the cursor jumping around in the terminal. This change makes use of Windows processing of virtual terminal control sequences instead.