Re: Identifying a buggy SFTP server found at an archaeological dig

Peter Gutmann <[email protected]> Sun, 12 May 2024 10:08:57 +0000
Newsgroups gmane.ietf.secsh
Message-ID <ME0P300MB0713E557B08C4A1E965D7E06EEE12@ME0P300MB0713.AUSP300.PROD.OUTLOOK.COM>
Ron Frederick <[email protected]> writes:=0A=0A>Alternately, you could try=
 and work around this by having your client not=0A>advertise any of the gro=
up-exchange kex algorithms (anything starting with=0A>"diffie-hellman-group=
-exchange-=93).=0A=0AThat's somewhat overkill, I don't want to remove any G=
EX capability just to=0Adeal with one broken server.  I think:=0A=0A"SSH-2.=
0-FTP Server ready" -> SSH_MSG_KEY_DH_GEX_REQUEST_OLD=0A"SSH-2.0-Chilkat_<v=
ersion>" -> SSH_MSG_KEY_DH_GEX_REQUEST=0A=0Awill do for now, since it fixes=
 the problem with the broken implementation and=0Adoesn't affect any other =
implementations (I've already got code paths in there=0Afor other implement=
atons that need this, it's just that the behaviour of this=0Aparticular Chi=
lkat server was a new one for me).  I'll report back if this=0Acauses any p=
roblems in case the info is of use to others.=0A=0APeter.