Date: Wed, 26 Jun 2002 20:54:34 -0400 (EDT) From: Robert Watson <rwatson@freebsd.org> To: Henk Wevers <henk@wevers.org> Cc: freebsd-security@freebsd.org Subject: Re: FreeBSD Security Advisory FreeBSD-SA-02:28.resolv Message-ID: <Pine.NEB.3.96L.1020626205223.17483B-100000@fledge.watson.org> In-Reply-To: <3D1A3153.6000704@wevers.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 26 Jun 2002, Henk Wevers wrote: > Does this mean that if you just build OpenSSH 3.4.p1, you must build > this again with the new world? If the OpenSSH binaries are dynamically linked against the version of libc you are replacing, you don't need to rebuild OpenSSH, since it will just automatically pick up the change. Do make sure you restart the sshd process after the upgrade, however, or it could use a cached copy of the library in memory (as with any other binary). While you can do all this without reboots, the best way the guarantee the instances of the library have been replaced is to reboot. Yeah, I know that's the evil windows thing, but it will work. The other way to do this is to track down any executing binary that might have linked/dynamically linked against the old version of the library, and make sure it's restarted using a rebuilt version of the application. 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.1020626205223.17483B-100000>