From owner-freebsd-security Wed Jun 26 17:36:25 2002 Delivered-To: freebsd-security@freebsd.org Received: from lariat.org (lariat.org [63.229.157.2]) by hub.freebsd.org (Postfix) with ESMTP id 038C737BFCC; Wed, 26 Jun 2002 16:27:45 -0700 (PDT) Received: from mustang.lariat.org (IDENT:ppp1000.lariat.org@lariat.org [63.229.157.2]) by lariat.org (8.9.3/8.9.3) with ESMTP id RAA17176; Wed, 26 Jun 2002 17:27:34 -0600 (MDT) X-message-flag: Warning! Use of Microsoft Outlook is dangerous and makes your system susceptible to Internet worms. Message-Id: <4.3.2.7.2.20020626172629.038ea900@localhost> X-Sender: brett@localhost X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 26 Jun 2002 17:27:06 -0600 To: Brian Behlendorf , Robert Watson From: Brett Glass Subject: Re: FreeBSD Security Advisory FreeBSD-SA-02:28.resolv Cc: freebsd-security@FreeBSD.ORG In-Reply-To: <20020626152851.Q310-100000@yez.hyperreal.org> References: 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 At 04:29 PM 6/26/2002, Brian Behlendorf wrote: >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... I suppose you could brute force this by grepping the binaries. Ugly, but it'd work. --Brett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message