WinSCP however, garbles these error messages reporting all sorts of nonsense, e.g.
* "Incoming packet was garbled on decryption"
* "Error decoding SFTP packet (0, 1, 0)"
It is evident from the logs that the real error message is there and testing with the terminal client propagates these errors just fine without any of these obscure error messages.
Is there a way we can tell our users can see the errors without getting mangled (without digging into the logs) or is it possible to patch WinSCP so thaterrors are propagated properly to the end user?