From owner-freebsd-security@FreeBSD.ORG Wed Sep 6 23:10:58 2006 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 DFB9A16A4DD for ; Wed, 6 Sep 2006 23:10:58 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id E586E43D81 for ; Wed, 6 Sep 2006 23:10:55 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 6A6871A3C1E; Wed, 6 Sep 2006 16:10:55 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 312C751569; Wed, 6 Sep 2006 19:10:52 -0400 (EDT) Date: Wed, 6 Sep 2006 19:10:51 -0400 From: Kris Kennaway To: Peter Thoenen Message-ID: <20060906231051.GA31247@xor.obsecurity.org> References: <200609062159.k86LxiiM041046@freefall.freebsd.org> <20060906230642.39757.qmail@web51909.mail.yahoo.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="5vNYLRcllDrimb99" Content-Disposition: inline In-Reply-To: <20060906230642.39757.qmail@web51909.mail.yahoo.com> User-Agent: Mutt/1.4.2.2i Cc: freebsd-security@freebsd.org Subject: Re: FreeBSD Security Advisory FreeBSD-SA-06:20.bind 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, 06 Sep 2006 23:10:59 -0000 --5vNYLRcllDrimb99 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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 (making sure that it has already been fixed). Kris --5vNYLRcllDrimb99 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFE/1V7Wry0BWjoQKURAqETAKDxkVXLNFKDCQPPTQIM3Jh7AiOhdgCfXFIr hLzTCmyZ5CHsyAL0kxQlpOk= =LdBk -----END PGP SIGNATURE----- --5vNYLRcllDrimb99--