From owner-freebsd-security  Mon Jan 29 16:38:42 2001
Delivered-To: freebsd-security@freebsd.org
Received: from horsey.gshapiro.net (horsey.gshapiro.net [209.220.147.178])
	by hub.freebsd.org (Postfix) with ESMTP id 55D9F37B404
	for <security@FreeBSD.ORG>; Mon, 29 Jan 2001 16:38:22 -0800 (PST)
Received: (from gshapiro@localhost)
	by horsey.gshapiro.net (8.12.0.Beta0/8.12.0.Beta0) id f0U0cKTs006954;
	Mon, 29 Jan 2001 16:38:20 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14966.3324.107528.104198@horsey.gshapiro.net>
Date: Mon, 29 Jan 2001 16:38:20 -0800
From: Gregory Neil Shapiro <gshapiro@FreeBSD.ORG>
To: Alfred Perlstein <bright@wintelcom.net>
Cc: Kris Kennaway <kris@obsecurity.org>, security@FreeBSD.ORG
Subject: Re: BIND 8.2.3 upgrade available
In-Reply-To: <20010129153144.H26076@fw.wintelcom.net>
References: <20010129143300.A38419@xor.obsecurity.org>
	<20010129153144.H26076@fw.wintelcom.net>
X-Mailer: VM 6.90 under 21.2  (beta41) "Polyhymnia" XEmacs Lucid
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

bright> Is there any chance that the bind and sendmail people could backport
bright> -DNO_SENDMAIL and -DNO_NAMED to 3.x (and maybe 2.x)?

What does the BIND bug have to do with sendmail?


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