Date: Wed, 26 Jun 2002 17:11:44 -0600 From: "David G . Andersen" <danderse@cs.utah.edu> To: Brian Behlendorf <brian@hyperreal.org> Cc: Robert Watson <rwatson@FreeBSD.ORG>, freebsd-security@FreeBSD.ORG Subject: Re: FreeBSD Security Advisory FreeBSD-SA-02:28.resolv Message-ID: <20020626171144.A27616@cs.utah.edu> In-Reply-To: <20020626152851.Q310-100000@yez.hyperreal.org>; from brian@hyperreal.org on Wed, Jun 26, 2002 at 03:29:45PM -0700 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
If it's statically linked, the odds are great that it uses libc.
Use 'file' to see how it's linked:
261 eep:ron/data> file /bin/sh
/bin/sh: ELF 32-bit LSB executable, Intel 80386,
version 1 (FreeBSD), statically linked, stripped
262 eep:ron/data> file /usr/bin/true
/usr/bin/true: ELF 32-bit LSB executable, Intel 80386,
version 1 (FreeBSD), dynamically linked (uses shared libs), stripped
-Dave
Brian Behlendorf just mooed:
> 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
--
work: dga@lcs.mit.edu me: dga@pobox.com
MIT Laboratory for Computer Science http://www.angio.net/
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?20020626171144.A27616>