From owner-freebsd-security  Wed Jan 31 15:42:54 2001
Delivered-To: freebsd-security@freebsd.org
Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67])
	by hub.freebsd.org (Postfix) with ESMTP id 490DE37B67D
	for <freebsd-security@FreeBSD.ORG>; Wed, 31 Jan 2001 15:42:37 -0800 (PST)
Received: (from dillon@localhost)
	by earth.backplane.com (8.11.1/8.9.3) id f0VNgUm20557;
	Wed, 31 Jan 2001 15:42:30 -0800 (PST)
	(envelope-from dillon)
Date: Wed, 31 Jan 2001 15:42:30 -0800 (PST)
From: Matt Dillon <dillon@earth.backplane.com>
Message-Id: <200101312342.f0VNgUm20557@earth.backplane.com>
To: Mike Silbersack <silby@silby.com>
Cc: Alfred Perlstein <bright@wintelcom.net>,
	Brian Behlendorf <brian@collab.net>,
	Roman Shterenzon <roman@xpert.com>, <freebsd-security@FreeBSD.ORG>
Subject: Re: FreeBSD Security Advisory: FreeBSD-SA-01:18.bind
References:  <Pine.BSF.4.31.0101311721500.563-100000@achilles.silby.com>
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

: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

    Hmm.  maybe Paul fixed it the close/reopen of the sockets.  Or I could
    be full of it... ah, wait, I remember.  The interface rescanning is
    broken when you run in a sandbox (it can't bind to new sockets from the
    sandbox).   If your interfaces don't change out from under you, you
    should be ok.

						-Matt


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