From owner-freebsd-security@FreeBSD.ORG Mon Aug 4 14:46:18 2003 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 93FBD37B401 for ; Mon, 4 Aug 2003 14:46:18 -0700 (PDT) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id CEF9B43F75 for ; Mon, 4 Aug 2003 14:46:15 -0700 (PDT) (envelope-from freebsd-security-local@be-well.no-ip.com) Received: from be-well.ilk.org (be-well.no-ip.com[66.30.200.37]) by comcast.net (rwcrmhc13) with ESMTP id <2003080421461501500e745ue>; Mon, 4 Aug 2003 21:46:15 +0000 Received: from be-well.ilk.org (lowellg.ne.client2.attbi.com [66.30.200.37] (may be forged)) by be-well.ilk.org (8.12.9/8.12.9) with ESMTP id h74LkAKS004729 for ; Mon, 4 Aug 2003 17:46:10 -0400 (EDT) (envelope-from freebsd-security-local@be-well.no-ip.com) Received: (from lowell@localhost) by be-well.ilk.org (8.12.9/8.12.6/Submit) id h74LkAG2004726; Mon, 4 Aug 2003 17:46:10 -0400 (EDT) X-Authentication-Warning: be-well.ilk.org: lowell set sender to freebsd-security-local@be-well.ilk.org using -f Sender: lowell@be-well.no-ip.com To: freebsd-security@freebsd.org References: <200308040004.h7404VVL030671@freefall.freebsd.org> <20030804101130.GA51954@cirb503493.alcatel.com.au> <200308040004.h7404VVL030671@freefall.freebsd.org> <3F2E1B42.8BDE2215@grosbein.pp.ru> <20030804085018.GA24017@rz-ewok.rz.uni-karlsruhe.de> <200308040004.h7404VVL030671@freefall.freebsd.org> <3F2E1B42.8BDE2215@grosbein.pp.ru> <20030804210016.GB10339@madman.celabo.org> From: Lowell Gilbert Date: 04 Aug 2003 17:46:10 -0400 In-Reply-To: <20030804210016.GB10339@madman.celabo.org> Message-ID: <44smohjdul.fsf@be-well.ilk.org> Lines: 16 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: FreeBSD Security Advisory FreeBSD-SA-03:08.realpath X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Security issues [members-only posting] List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Aug 2003 21:46:18 -0000 "Jacques A. Vidrine" writes: > Thank you for the suggestion. Would you care to post _exactly_ what > wording you think would be better? I cannot think of a way to do so > without being redundant or misleading. I have no desire to add a > ``Not affected:'' line. Especially at times when we have two -STABLE > branches (as we will soon for 4.x and 5.x), it will be common that > there is a bug in one release but not another higher-numbered one. I suppose you could include the file versions for which the bug no longer affected -STABLE. It's not always easy to determine, but it certainly was in this case. It only took me 5 minutes to work it out on my own, so I'm not convinced of the value, but I suppose it meets what some others were asking for, and I don't *think* it makes the advisory more confusing.