From owner-freebsd-security  Thu Aug 14 08:26:47 1997
Return-Path: <owner-freebsd-security>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id IAA23485
          for security-outgoing; Thu, 14 Aug 1997 08:26:47 -0700 (PDT)
Received: from rover.village.org (rover.village.org [204.144.255.49])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id IAA23415;
          Thu, 14 Aug 1997 08:25:56 -0700 (PDT)
Received: from rover.village.org [127.0.0.1] 
	by rover.village.org with esmtp (Exim 1.60 #1)
	id 0wz1mU-0000Wf-00; Thu, 14 Aug 1997 09:25:46 -0600
To: cschuber@uumail.gov.bc.ca
Subject: Re: CERT Advisory CA-97.22 - BIND - the Berkeley Internet Name Daemon 
Cc: freebsd-security@freebsd.org, security-officer@freebsd.org
In-reply-to: Your message of "Thu, 14 Aug 1997 08:02:46 PDT."
		<199708141502.IAA01825@cwsys.cwent.com> 
References: <199708141502.IAA01825@cwsys.cwent.com>  
Date: Thu, 14 Aug 1997 09:25:46 -0600
From: Warner Losh <imp@rover.village.org>
Message-Id: <E0wz1mU-0000Wf-00@rover.village.org>
Sender: owner-freebsd-security@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In message <199708141502.IAA01825@cwsys.cwent.com> Cy Schubert writes:
: This has been discussed on BUGTRAQ over the last 3-4 months.  We now have a
: CERT advisory discussing this.
: 
: When will BIND-8.1.1 be available in the 2.2 branch?

8.1.1 isn't even in the -current branch yet, so one could conjecture
that it will be a while.  Bind 4.9.6 and Bind 8.1.1 have incompatible
boot file formats, so adding 8.1.1 into the 2.2 branch, or even the
-current banch, is complicated by compatibility concerns.

8.1.1 builds out of the box on a FreeBSD system.  There have been
efforts made to make it a port so it is even easier.

Warner