From owner-freebsd-security  Wed Jan 31 15:26:39 2001
Delivered-To: freebsd-security@freebsd.org
Received: from silby.com (cb34181-c.mdsn1.wi.home.com [24.183.3.139])
	by hub.freebsd.org (Postfix) with ESMTP id ED2D837B65D
	for <freebsd-security@FreeBSD.ORG>; Wed, 31 Jan 2001 15:26:21 -0800 (PST)
Received: (qmail 769 invoked by uid 1000); 31 Jan 2001 23:26:19 -0000
Received: from localhost (sendmail-bs@127.0.0.1)
  by localhost with SMTP; 31 Jan 2001 23:26:19 -0000
Date: Wed, 31 Jan 2001 17:26:19 -0600 (CST)
From: Mike Silbersack <silby@silby.com>
To: Alfred Perlstein <bright@wintelcom.net>
Cc: Matt Dillon <dillon@earth.backplane.com>,
	Brian Behlendorf <brian@collab.net>,
	Roman Shterenzon <roman@xpert.com>, <freebsd-security@FreeBSD.ORG>
Subject: Re: FreeBSD Security Advisory: FreeBSD-SA-01:18.bind
In-Reply-To: <20010131151531.I26076@fw.wintelcom.net>
Message-ID: <Pine.BSF.4.31.0101311721500.563-100000@achilles.silby.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


On Wed, 31 Jan 2001, Alfred Perlstein wrote:

> If it breaks HUP, then not really. :)
>
> I'm not sure how bind handles restarts, but even if it exec(2)s over
> itself it can track the fd open for its socket and shouldn't have to
> rebind it.

I don't see any complaints from 8.2.3 running -u bind -g bind when I HUP
it here.

(Well, ok, I see the can't create pidfile junk, but that's not critical
IMHO.)

Mike "Silby" Silbersack



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