From owner-freebsd-security Wed Jun 26 16: 0: 7 2002 Delivered-To: freebsd-security@freebsd.org Received: from hyperreal.org (taz3.hyperreal.org [209.133.83.22]) by hub.freebsd.org (Postfix) with SMTP id 2789837B4D6 for ; Wed, 26 Jun 2002 15:54:22 -0700 (PDT) Received: (qmail 8875 invoked from network); 26 Jun 2002 22:27:40 -0000 Received: from localhost.hyperreal.org (HELO yez.hyperreal.org) (127.0.0.1) by localhost.hyperreal.org with SMTP; 26 Jun 2002 22:27:40 -0000 Received: (qmail 24701 invoked by uid 1000); 26 Jun 2002 22:29:45 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 26 Jun 2002 22:29:45 -0000 Date: Wed, 26 Jun 2002 15:29:45 -0700 (PDT) From: Brian Behlendorf To: Robert Watson Cc: freebsd-security@freebsd.org Subject: Re: FreeBSD Security Advisory FreeBSD-SA-02:28.resolv In-Reply-To: Message-ID: <20020626152851.Q310-100000@yez.hyperreal.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: localhost.hyperreal.org 1.6.2 900/1000/N 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, Robert Watson wrote: > 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. Sorry for the newbie question here, but is there a way to programmatically determine which binaries on a system static-linked libc? I tried "nm" but that needs non-stripped executables... Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message