Date: Wed, 1 Nov 2000 15:39:40 -0800 From: Brooks Davis <brooks@one-eyed-alien.net> To: Mitch Collinsworth <mitch@ccmr.cornell.edu> Cc: freebsd-security@FreeBSD.ORG Subject: Re: FreeBSD Security Advisory: FreeBSD-SA-00:62.top Message-ID: <20001101153940.A25149@Odin.AC.HMC.Edu> In-Reply-To: <Pine.LNX.4.10.10011011833020.11146-100000@khitomer.msc.cornell.edu>; from mitch@ccmr.cornell.edu on Wed, Nov 01, 2000 at 06:34:09PM -0500 References: <20001101225954.E5B2C37B479@hub.freebsd.org> <Pine.LNX.4.10.10011011833020.11146-100000@khitomer.msc.cornell.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Nov 01, 2000 at 06:34:09PM -0500, Mitch Collinsworth wrote: > On Wed, 1 Nov 2000, FreeBSD Security Advisories wrote: > > > All released versions of FreeBSD prior to the correction date > > including 4.0, 4.1, 4.1.1 and 3.5.1 are vulnerable to this problem, > > but it was fixed in the 4.1.1-STABLE branch prior to the release of > > FreeBSD 4.2-RELEASE. > > There's a 4.2-RELEASE ?? It's in beta. I think the idea here was to indicate the first release which does not have this bug. I think that's a good policy (especialy close to a release date) since it lets people who only run releases know which one to run. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. 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?20001101153940.A25149>