From owner-freebsd-security Wed Jun 26 13:48:15 2002 Delivered-To: freebsd-security@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 84E0237B679 for ; Wed, 26 Jun 2002 13:22:18 -0700 (PDT) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.12.3/8.12.3) with SMTP id g5QKMGw6016670; Wed, 26 Jun 2002 16:22:16 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Wed, 26 Jun 2002 16:22:15 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: "H. Wade Minter" Cc: freebsd-security@freebsd.org Subject: Re: FreeBSD Security Advisory FreeBSD-SA-02:28.resolv In-Reply-To: <20020626152504.Q45972-100000@bunning.skiltech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, 26 Jun 2002, H. Wade Minter wrote: > So am I correct in assuming that this fix requires a complete system > rebuild (make buildworld) as opposed to just rebuilding a particular > module? You will catch most applications simply by rebuilding libc and reinstalling. Unfortunately, some applications are statically linked, and they must be individually relinked against the new libc and reinstalled. Since there are a moderate number of statically linked applications that use DNS, the easiest directions simply involved rebuilding the entire system (especially given modern system speed). Once the binary updates are available, there will be a list of the affect binaries if you want to take a more selective approach. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message