Differences

This shows you the differences between the selected revisions of the page.

2016-01-20 2016-01-21
5.8.1 Moving SSH-1-only options to less prominent positions on Advanced Site Settings dialog and removing SSH-2-only designations of session options. (martin) sshbug_hmac2 anchor (martin)
Line 27: Line 27:
It has been known for some %%SSH%% servers to get confused by this message in one way or another – because it has a long name, or because they can't cope with unrecognized request names even to the extent of sending back the correct failure response, or because they handle it sensibly but fill up the server's log file with pointless spam, or whatever. WinSCP therefore supports this bug-compatibility flag: if it believes the server has this bug, it will never send its ''winadj@putty.projects.tartarus.org'' request, and will make do without its timing data. It has been known for some %%SSH%% servers to get confused by this message in one way or another – because it has a long name, or because they can't cope with unrecognized request names even to the extent of sending back the correct failure response, or because they handle it sensibly but fill up the server's log file with pointless spam, or whatever. WinSCP therefore supports this bug-compatibility flag: if it believes the server has this bug, it will never send its ''winadj@putty.projects.tartarus.org'' request, and will make do without its timing data.
-===== Miscomputes SSH-2 HMAC keys =====+===== [[sshbug_hmac2]] Miscomputes SSH-2 HMAC keys =====
Versions 2.3.0 and below of the SSH server software from ssh.com compute the keys for their HMAC message authentication codes incorrectly. A typical symptom of this problem is that WinSCP dies unexpectedly at the beginning of the session, saying "Incorrect MAC received on packet". Versions 2.3.0 and below of the SSH server software from ssh.com compute the keys for their HMAC message authentication codes incorrectly. A typical symptom of this problem is that WinSCP dies unexpectedly at the beginning of the session, saying "Incorrect MAC received on packet".

Last modified: by martin