Peter Thoenen wrote:
Just to verify as not mentioned in the security advisory, if you are
using both the BIND and OPENSSL ports with the REPLACE_BASE directive,
these don't apply correct?
Assuming you've updated to the 9.3.2-P1 version (ports version 9.3.2.1) of
BIND 9, then yes for the BIND
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-06:20.bind Security Advisory
The FreeBSD Project
Topic:
Just to verify as not mentioned in the security advisory, if you are
using both the BIND and OPENSSL ports with the REPLACE_BASE directive,
these don't apply correct?
-Peter
___
freebsd-security@freebsd.org mailing list
On Wed, Sep 06, 2006 at 04:06:42PM -0700, Peter Thoenen wrote:
Just to verify as not mentioned in the security advisory, if you are
using both the BIND and OPENSSL ports with the REPLACE_BASE directive,
these don't apply correct?
The same bugs exist, of course...the fix is to update the port
Peter Thoenen wrote:
Just to verify as not mentioned in the security advisory, if you are
using both the BIND and OPENSSL ports with the REPLACE_BASE directive,
these don't apply correct?
I don't know enough of what the ports do to be certain about the answer
to that question, but here are the
I wrote:
I don't know enough of what the ports do to be certain about the answer
to that question, but here are the files in the FreeBSD 6.x base system
which are affected by these security advisories:
...
If the ports replace all of those files, you should be safe (at least
on FreeBSD 6.x
