From owner-freebsd-security@FreeBSD.ORG Wed Oct 12 07:12:37 2005 Return-Path: X-Original-To: freebsd-security@freebsd.org Delivered-To: freebsd-security@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2FABA16A420 for ; Wed, 12 Oct 2005 07:12:37 +0000 (GMT) (envelope-from arne_woerner@yahoo.com) Received: from web30302.mail.mud.yahoo.com (web30302.mail.mud.yahoo.com [68.142.200.95]) by mx1.FreeBSD.org (Postfix) with SMTP id 85A9443D53 for ; Wed, 12 Oct 2005 07:12:36 +0000 (GMT) (envelope-from arne_woerner@yahoo.com) Received: (qmail 32918 invoked by uid 60001); 12 Oct 2005 07:12:36 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=xLKHRr4p1cWsgLdXfkDyhVCvlO24N2nrLOWm4tAggCHFw+zCS8zAAqDVnP8q/4iAiOvODUoCfZcqmdzxNzPXL3PKh+wFIbnjIchTGQBO5+EOWuYfhrNp41DhAp8V5L8ISFrLvqF3qevuIsUz5QRpGvv64wZkUYmVEpQy1FbDfqI= ; Message-ID: <20051012071235.32916.qmail@web30302.mail.mud.yahoo.com> Received: from [213.54.70.38] by web30302.mail.mud.yahoo.com via HTTP; Wed, 12 Oct 2005 00:12:35 PDT Date: Wed, 12 Oct 2005 00:12:35 -0700 (PDT) From: Arne "Wörner" To: Colin Percival In-Reply-To: <434C5B02.8030904@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: freebsd-security@freebsd.org Subject: Re: FreeBSD Security Advisory FreeBSD-SA-05:21.openssl X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Oct 2005 07:12:37 -0000 --- Colin Percival wrote: > Andrea Venturoli wrote: > > FreeBSD Security Advisories wrote: > >> Note that any statically linked applications that are not > part of the > >> base system (i.e. from the Ports Collection or other > 3rd-party sources) > >> must be recompiled. > > > > Ok, is there any way to list installed ports which are > statically linked > > against OpenSSL? > > There isn't any particularly good approach, unfortunately. I > think I'd > probably use a combination of find(1), file(1), and fgrep(1) to > find any > executable files (via find) which are statically linked (using > file) and > which contain the string "OpenSSL" (using fgrep). > I would use a combination out of nm(1) and grep(1) instead of fgrep(1). But I do not now right now, which symbol will always be contained in a statically linked executable that might use OpenSSL... Btw: Why should the string "OpenSSL" be contained in each and every executable, that might use OpenSSL? -Arne __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com