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

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

On 26-Jun-02 Robert Watson wrote:
> 
> On Wed, 26 Jun 2002, H. Wade Minter wrote:
> 
>> So am I correct in assuming that this fix requires a complete system
>> rebuild (make buildworld) as opposed to just rebuilding a particular
>> module? 
> 
> 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. 
> Since there are a moderate number of statically linked applications that
> use DNS, the easiest directions simply involved rebuilding the entire
> system (especially given modern system speed).  Once the binary updates
> are available, there will be a list of the affect binaries if you want to
> take a more selective approach.
> 
> Robert N M Watson             FreeBSD Core Team, TrustedBSD Projects
> robert@fledge.watson.org      Network Associates Laboratories
> 
> 

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?

Thanks.

Mark.

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?XFMail.020626151359.mark>