Date: Fri, 30 Nov 2001 00:49:10 -0800 From: Greg White <gregw-freebsd-security@greg.cex.ca> To: freebsd-security@freebsd.org Subject: Re: sshd exploit Message-ID: <20011130004910.A9082@greg.cex.ca> In-Reply-To: <Pine.BSF.4.10.10111300105070.99377-100000@madeline.boneyard.lawrence.ks.us>; from bsd-sec@boneyard.lawrence.ks.us on Fri, Nov 30, 2001 at 01:30:57AM -0600 References: <20011129012235.U6446-100000@achilles.silby.com> <Pine.BSF.4.10.10111300105070.99377-100000@madeline.boneyard.lawrence.ks.us>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri Nov 11/30/01, 2001 at 01:30:57AM -0600, bsd-sec@boneyard.lawrence.ks.us wrote: > On Thu, 29 Nov 2001, Mike Silbersack wrote: > > > > > The CRC bug was fixed in 2.3.0, which was merged into -stable before the > > release of freebsd 4.3. If 3.0.1's giving you any enhanced immunity, it's > > to a bug which has not yet been announced. > > > > If there _is_ a new bug, and it follows the decription in the url posted > > earlier in the thread, it's probably also SSHv1 related, and can be > [...] > > Perhaps so. However, at the univeristy department where I work, RH Linux lab > machines running both 2.5.x and 2.9.x versions of OpenSSH were indeed > compromised while running ssh version 1. The only other services with > externally available ports were portmap and syslogd. Am I the only one who sees portmap and syslogd as more likely to exploit than ssh? I mean, come on, look at the security histories, here... -- Greg White To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011130004910.A9082>