Re: SSH Vulnerability

From: Nico Kadel-Garcia (nkadel@bellatlantic.net)
Date: 02/25/02 

From: "Nico Kadel-Garcia" <nkadel@bellatlantic.net>
Date: Mon, 25 Feb 2002 00:06:01 GMT

"Markus Friedl" <msfriedl@cip.informatik.uni-erlangen.de> wrote in message
news:a5b64n$rtb$1@rznews2.rrze.uni-erlangen.de...
> In <3C78F9D1.F5452310@123.net> William Webb <wwebb@123.net> writes:
>
> >Aside from switching to SSH2 to avoid the SSH1 vulnerability --
> >http://www.kb.cert.org/vuls/id/945216 I have noticed that since I
>
> generally, switching protocols does not solve problems.
>
> it's better to upgrade broken software.

Yeah. Almost all reports of "the SSH1 vulnerability" are traceable back to
the buffer overflow, which is not an SSH1 protocol problem but a software
mistake, that was corrected in OpenSSH many, many moons ago. There is *no*
proof that SSH2 doesn't have similar errors, and all published versions of
SSH servers corrected it some time ago as well.

Now, ssh.com is happy to get people off of SSH1. SSH2 was created for a
number of reasons, partly to address some SSH1 missing software features but
primarily, IMHO, to get away from the patented RSA protocol. Well, the RSA
patent has expired: The main reason now to use SSH2 is because someone you
work with likes it, or you like the sftp software. I don't: any "ftp" server
that can't handle "ls -lR" or "mget *.c" needs to be renamed the
"Only_Useful_With_A_GUI_Secure_FTP_", or OUWAGUISFTP for short. If you can
spell it, you can use it....

Relevant Pages

  • FreeBSD Security Advisory FreeBSD-SA-01:24.ssh
    ... OpenSSH is an implementation of the SSH1 and SSH2 secure shell ... An SSH1 client/server from ssh.com is included in the ports ... mistake in code intended to work around a protocol flaw in the SSH1 ... of the ssh port prior to ssh-1.2.27_3 are vulnerable to these attacks. ...
    (FreeBSD-Security)
  • Re: SSH 1.0 vs. 2.0
    ... SSH2 was a total rewite of the protocol. ... SSH limited www.ssh.com He also wrote the SSH2 specs. ... In a nutshell SSH1 ... support if your business does not depend upon it. ...
    (comp.os.linux.security)
  • Re: SSH 1.0 vs. 2.0
    ... SSH1 was written by Tatu H from ... SSH2 is a more robust protocol. ... SSH2's primary *business* motivation was to avoid RSA, ...
    (comp.os.linux.security)
  • Re: [SOLVED] Help please: how to enable SSH password authentication under FreeBSD 6.2? Solved -
    ... Is this what you tried too, or did you use SSH2 (i.e. key authentication, instead of password authentication)? ... SSH1 versus SSH2 is *nothing* to do with keys versus passwords. ... The difference is that SSH1 an older protocol and is *insecure* and no-one should still be using it unless they have some legacy app which really cannot be updated. ...
    (freebsd-questions)
  • Re: Request for Comments: Getting OpenSSH to work with ssh.com and itself
    ... All the titles involving mixed protocol versions ... "To be clear, the two protocol versions SSH1 and SSH2 do not interoperate, ... Leaving your keys around inside an ssh-agent indefinitely means ... > assume what you mean is connecting an SSH2 client to an OpenSSH server, ...
    (comp.security.ssh)