Date: Thu, 27 Jun 2002 01:21:50 +0200 From: Erik Trulsson <ertr1013@student.uu.se> To: Brian Behlendorf <brian@hyperreal.org> Cc: freebsd-security@freebsd.org Subject: Re: FreeBSD Security Advisory FreeBSD-SA-02:28.resolv Message-ID: <20020626232150.GA2052@falcon.midgard.homeip.net> In-Reply-To: <20020626152851.Q310-100000@yez.hyperreal.org> References: <Pine.NEB.3.96L.1020626162041.16603B-100000@fledge.watson.org> <20020626152851.Q310-100000@yez.hyperreal.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jun 26, 2002 at 03:29:45PM -0700, Brian Behlendorf wrote: > 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... file(1) should do the trick. Normally everything in /bin and /sbin is statically linked while executables in /usr/bin and /usr/sbin are dynamically linked. Most executables from ports are also dynamically linked. -- <Insert your favourite quote here.> Erik Trulsson ertr1013@student.uu.se To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020626232150.GA2052>