From owner-freebsd-security Wed Nov 1 15:39:48 2000 Delivered-To: freebsd-security@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id E94C637B4D7 for ; Wed, 1 Nov 2000 15:39:43 -0800 (PST) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id eA1NdeD25276; Wed, 1 Nov 2000 15:39:40 -0800 Date: Wed, 1 Nov 2000 15:39:40 -0800 From: Brooks Davis To: Mitch Collinsworth Cc: freebsd-security@FreeBSD.ORG Subject: Re: FreeBSD Security Advisory: FreeBSD-SA-00:62.top Message-ID: <20001101153940.A25149@Odin.AC.HMC.Edu> References: <20001101225954.E5B2C37B479@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from mitch@ccmr.cornell.edu on Wed, Nov 01, 2000 at 06:34:09PM -0500 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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