From owner-freebsd-security Wed Dec 15 9:48: 8 1999 Delivered-To: freebsd-security@freebsd.org Received: from quaggy.ursine.com (lambda.blueneptune.com [209.133.45.179]) by hub.freebsd.org (Postfix) with ESMTP id 0D3D5152E9 for ; Wed, 15 Dec 1999 09:48:05 -0800 (PST) (envelope-from fbsd-security@ursine.com) Received: from michael (lambda.ursine.com [209.133.45.69]) by quaggy.ursine.com (8.9.3/8.9.3) with ESMTP id JAA55933 for ; Wed, 15 Dec 1999 09:48:04 -0800 (PST) Message-ID: <199912150948040350.0CA353DD@quaggy.ursine.com> In-Reply-To: <19991215050149.A3602@palomine.net> References: <4.2.2.19991214112940.01c3d5b8@mail.myable.com> <19991215050149.A3602@palomine.net> X-Mailer: Calypso Version 3.00.00.13 (2) Date: Wed, 15 Dec 1999 09:48:04 -0800 From: "Michael Bryan" To: freebsd-security@FreeBSD.ORG Subject: Re: CERT released RSAREF bulletin Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 12/15/99 at 5:01 AM Chris Johnson wrote: > >Of these, I'm using OpenSSH, openssl, and pipsecd. It seems to me that all= of >these link rsaref dynamically, and that therefore I should need only to= rebuild >rsaref to ensure my safety. Can someone say definitively whether this is= the >case? If they link rsaref dynamically, yes, you just need to rebuild the library. Use "ldd" on any executable to see what libraries it loads dynamically. >And if so, why do I keep seeing these messages telling me I need to >rebuild anything that depends on the rsaref port? Also, was the fix that= was >applied to the ssh port also applied to the OpenSSH port? The fix applied to the ssh port did not need to be applied to OpenSSH. The same problem did not exist in OpenSSH. Michael Bryan fbsd-security@ursine.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message