Date: Wed, 12 Oct 2005 11:14:57 +0300 From: Vladimir Terziev <vladimir.terziev@sun-fish.com> To: freebsd-security@freebsd.org Subject: Re: FreeBSD Security Advisory FreeBSD-SA-05:21.openssl Message-ID: <20051012111457.17eacc99.vlady@sun-fish.com> In-Reply-To: <434C427D.40501@netfence.it> References: <200510111202.j9BC2obf081876@freefall.freebsd.org> <434C427D.40501@netfence.it>
next in thread | previous in thread | raw e-mail | index | archive | help
Ok, i think the FreeBSD team should isolate all statically linked applications which are part of the operating system and which depend on OpenSSL. They must be re-build (not the whole operating system) in order OpenSSL changes to be applyed to them. Statically linked ports are responsibility of the person who installed them. Vladimir On Wed, 12 Oct 2005 00:53:49 +0200 Andrea Venturoli <ml@netfence.it> 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? > > bye & Thanks > av. > _______________________________________________ > freebsd-security@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-security > To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051012111457.17eacc99.vlady>