From owner-freebsd-security Thu Feb 1 15:37: 4 2001 Delivered-To: freebsd-security@freebsd.org Received: from juice.shallow.net (node16229.a2000.nl [24.132.98.41]) by hub.freebsd.org (Postfix) with ESMTP id D146537B6AB for ; Thu, 1 Feb 2001 15:36:46 -0800 (PST) Received: from localhost (joshua@localhost) by juice.shallow.net (8.11.1/8.11.1) with ESMTP id f11NaeP79814; Fri, 2 Feb 2001 00:36:40 +0100 (CET) (envelope-from joshua@roughtrade.net) Date: Fri, 2 Feb 2001 00:36:40 +0100 (CET) From: Joshua Goodall To: Dag-Erling Smorgrav Cc: Alfred Perlstein , Subject: Re: FreeBSD Security Advisory: FreeBSD-SA-01:18.bind In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 1 Feb 2001, Dag-Erling Smorgrav wrote: > Does anybody read this list, or do you all just post to it without > reading anything anyone else is posting? I posted detailed > instructions for a) upgrading a vulnerable system without making > world, and b) setting up BIND in chroot and jail sandboxes, including > how to deal with ndc and log sockets, just a few days ago. If you mean that begins with: > RELENG_3 has been fixed, please follow the procedure below if you're > running 2.2.x or 3.x (tested on 3.5-STABLE, should work on 2.2.x but > no guarantees): ... then I confess that I read that paragraph and skipped the rest since I'm on 4.2-STABLE and I was wading through too many emails on the subject. Although, yes, having gone back, it is certainly relevant and useful for RELENG_4 trackers. j -- Joshua Goodall A friend of mine works for a medium-sized telco. He has no phone, because (and I quote) "the lady who provisions phones is on holiday" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message