From owner-freebsd-current  Tue Nov 16  8:17:22 1999
Delivered-To: freebsd-current@freebsd.org
Received: from forrie.net (forrie.net [216.67.12.69])
	by hub.freebsd.org (Postfix) with ESMTP id 39846152E6
	for <freebsd-current@FreeBSD.ORG>; Tue, 16 Nov 1999 08:17:07 -0800 (PST)
	(envelope-from forrie@forrie.com)
Received: from Forrest (getbent@forrie.ne.mediaone.net [24.128.72.15])
	by forrie.net (8.9.3/8.9.3) with ESMTP id LAA18861;
	Tue, 16 Nov 1999 11:16:40 -0500 (EST)
Message-Id: <4.2.1.19991116111228.00a96790@216.67.12.69>
X-Sender: forrie@216.67.12.69
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.1 
Date: Tue, 16 Nov 1999 11:12:51 -0500
To: Peter Wemm <peter@netplex.com.au>, Ben Rosengart <ben@skunk.org>
From: Forrest Aldrich <forrie@forrie.com>
Subject: Re: BIND update 
Cc: freebsd-current@FreeBSD.ORG
In-Reply-To: <19991116064646.58E361CA0@overcee.netplex.com.au>
References: <Your message of "Mon, 15 Nov 1999 22:12:28 EST." <Pine.BSF.4.20.9911152211490.36980-100000@penelope.skunk.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

So wouldn't be the impact if a server was compromized in the absence
of an available fix :)


At 02:46 PM 11/16/99 +0800, Peter Wemm wrote:
>Ben Rosengart wrote:
> > On Mon, 15 Nov 1999, Forrest Aldrich wrote:
> >
> > > Will we be updating 4.0-current to the latest BIND-8.22-P5?
> >
> > Or -stable for that matter?  I believe these changes are eminently
> > qualified, being bugfixes.
>
>The changes are most definately not "just" bugfixes.  The impact is rather
>large.
>
>Cheers,
>-Peter
>--
>Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message