Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 26 Jun 2002 20:56:51 -0400 (EDT)
From:      Robert Watson <rwatson@FreeBSD.ORG>
To:        Mark Hartley <mark@work.drapple.com>
Cc:        freebsd-security@FreeBSD.ORG, "H. Wade Minter" <minter@lunenburg.org>
Subject:   Re: FreeBSD Security Advisory FreeBSD-SA-02:28.resolv
Message-ID:  <Pine.NEB.3.96L.1020626205448.17483C-100000@fledge.watson.org>
In-Reply-To: <XFMail.020626151359.mark@work.drapple.com>

next in thread | previous in thread | raw e-mail | index | archive | help

On Wed, 26 Jun 2002, Mark Hartley wrote:

> Are there other common applications (not rebuilt by the world) that many
> of us are likely to be running which are going to need to be rebuilt
> (i.e. Apache, pop3 servers, db servers, etc)? 
> 
> I'm not really sure how to even know if an application would be
> statically linked against libc.  Maybe someone with a clue could post
> some instructions on how to check out if an app is statically linked
> against libc, then we could test our own apps and rebuild as needed. 
> Anyone have an easy way that we can tell? 

I just sent out some instructions in another mail, but the basic gist is
that you run the 'file' command on the binaries you're worried about, and
make sure they are dynamically linked.  If the binary is statically
linked, or it's dynamically linked against an older libc, it will need to
be rebuilt. 

Assuming they dynamically link against the current (fixed) version of the
libc library, then restarting the application without rebuilding should be
sufficient.  Note that if the daemon is actually *running* when you
replace libc, you'll need to restart it so it picks up the new library
version.  It does no good to replace the daemon on disk, but have the
running version be the old one.

Let me know if you have any questions.

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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1020626205448.17483C-100000>