Date: Wed, 12 Oct 2005 00:12:35 -0700 (PDT) From: Arne "Wörner" <arne_woerner@yahoo.com> To: Colin Percival <cperciva@freebsd.org> Cc: freebsd-security@freebsd.org Subject: Re: FreeBSD Security Advisory FreeBSD-SA-05:21.openssl Message-ID: <20051012071235.32916.qmail@web30302.mail.mud.yahoo.com> In-Reply-To: <434C5B02.8030904@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--- Colin Percival <cperciva@freebsd.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051012071235.32916.qmail>