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 statica
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
> [EMAIL PROTECTED] wrote:
> > Quoting FreeBSD Security Advisories <[EMAIL PROTECTED]>:
> >
> >
>
>>=
> >>FreeBSD-SA-05:21.opensslSecurity
> Advisory
> >>
Ian G wrote:
> FreeBSD Security Advisories wrote:
>> Applications which do not support SSLv2, have been configured to not
>> permit the use of SSLv2, or do not use the SSL_OP_MSIE_SSLV2_RSA_PADDING
>> or SSL_OP_ALL options are not affected.
>>
>> IV. Workaround
>>
>> No workaround is available.
>
I would be interested in the answer too. An unofficial freebsd
tripwire file posted somewhere + a forum to discuss changes would be
also interesting.
On 9/28/05, Bret Walker <[EMAIL PROTECTED]> wrote:
> Hello all.
>
> I am just setting up my first 5.X box, and I'm in the process of fine
> tuning m
unfortunately, this is the dark side of FreeBSD security patch
management :) and I think also the main reason FreeBSD isn't so widely
deployed into enterprise environments. It's ok for hacking or managing
few boxes but try to imagine how to manage security on hundreds of them
this way. :(
on
Quoting FreeBSD Security Advisories <[EMAIL PROTECTED]>:
> =
> FreeBSD-SA-05:21.opensslSecurity Advisory
> The FreeBSD Project
[
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-05:21.opensslSecurity Advisory
The FreeBSD Project
Topic: P
