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

Ron Frederick <[email protected]> writes:=0A=0A>A quick search for that id=
entification string with Google seems to point at a=0A>=93Chilkat sFTP=94 s=
erver=0A=0AYeah, I'd seen that too but saw other info that it used "SSH-2.0=
-=0AChilkat_<version>", and I'm nervous about adding a bugfix for a particu=
lar=0Abroken server that may end up misidentifying non-broken servers, eith=
er ones=0Athat use the same generic string or ones that fixed it at some po=
int but since=0Athe string doesn't include a version you can't tell who's r=
unning the fixed=0Aversion.  From this page:=0A=0Ahttps://www.chilkatsoft.c=
om/refdoc/cssftpref.html=0A=0Ait looks like they disabled stuff like HMAC-M=
D5, RIPEMD-160, and similar only=0Ain the very latest version (April 2024),=
 so perhaps "SSH-2.0-FTP Server ready"=0A=3D broken, "SSH-2.0-Chilkat_<vers=
ion>" =3D non-broken?=0A=0APeter.