User manipulation of tty mode opcodes / IUTF8 incompatibilities
Darren Tucker
dtucker at dtucker.net
Mon Feb 12 18:27:50 AEDT 2018
On 12 February 2018 at 17:50, Nathan Anderson <nathan at anderson-net.com> wrote:
> The IUTF8 tty mode support added to the client in 7.3 unfortunately
> appears to have broken interop with a handful of noncompliant server
> implementations that immediately close the connection when they are
> sent an opcode that they know nothing about, rather than ignore it.
> Setting the value to 0 is not enough: its mere presence regardless of
> value is enough to cause the server to bomb out.
Sigh. If you could provide the server's identity string (eg from "ssh
-v yourthing") we could add a bug bit to stop it from being sent.
--
Darren Tucker (dtucker at dtucker.net)
GPG key 11EAA6FA / A86E 3E07 5B19 5880 E860 37F4 9357 ECEF 11EA A6FA (new)
Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.
More information about the openssh-unix-dev
mailing list