From owner-freebsd-questions@FreeBSD.ORG Wed Jul 25 00:26:46 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7E0B016A417 for ; Wed, 25 Jul 2007 00:26:46 +0000 (UTC) (envelope-from simon@benji.nitro.dk) Received: from mx.nitro.dk (zarniwoop.nitro.dk [83.92.207.38]) by mx1.freebsd.org (Postfix) with ESMTP id 3608A13C457 for ; Wed, 25 Jul 2007 00:26:46 +0000 (UTC) (envelope-from simon@benji.nitro.dk) Received: from benji.nitro.dk (unknown [192.168.3.39]) by mx.nitro.dk (Postfix) with ESMTP id 53F2A2DE284; Tue, 24 Jul 2007 23:46:19 +0000 (UTC) Received: by benji.nitro.dk (Postfix, from userid 2000) id E63BAFD9F; Wed, 25 Jul 2007 01:46:36 +0200 (CEST) Date: Wed, 25 Jul 2007 01:46:36 +0200 From: "Simon L. Nielsen" To: FreeBSD Questions , freebsd-security@FreeBSD.org Message-ID: <20070724234636.GA6738@zaphod.nitro.dk> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="CE+1k2dSO48ffgeK" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.16 (2007-06-09) Cc: FreeBSD Security Team , Jeffrey Goldberg Subject: Re: Waiting for BIND security announcement X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Simon L. Nielsen" , freebsd-security@FreeBSD.org, FreeBSD Security Team List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jul 2007 00:26:46 -0000 --CE+1k2dSO48ffgeK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable [freebsd-security@ CC'ed to avoid answering the same there again shorly :) - if following up, please drop either freebsd-questions or freebsd-securiy to avoid "spamming" both lists] On 2007.07.24 18:15:43 -0500, Jeffrey Goldberg wrote: > As I'm sure many people know there is a newly discovered BIND vulnerabili= ty=20 > allowing cache injection (pharming). See >=20 > http://www.isc.org/index.pl?/sw/bind/bind-security.php >=20 > for details. >=20 > The version of bind on 6.2, 9.3.3, looks like it is vulnerable (along wit= h=20 > many other versions). It's not particularly an issue for me since my nam= e=20 > servers aren't publicly queryable, but I am curios about how things like= =20 > security problems in > src/contrib get handled in FreeBSD. Yes, the FreeBSD Security Team and the FreeBSD BIND maintainer are aware of the issue and are working on fixing it in FreeBSD as soon as possible. More details about the issue can be found at: http://www.isc.org/sw/bind/bind-security.php . Our general security handling policies can be found at: http://security.FreeBSD.org/ . --=20 Simon L. Nielsen FreeBSD Deputy Security Officer --CE+1k2dSO48ffgeK Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGpo9cBJx0gP90kKsRAmOJAJ9Z5JepxUgI7J71CSp5ujQPVPNjTQCdGl3T yHN5mMu1zKojJwDDzGSV9Bw= =sEQS -----END PGP SIGNATURE----- --CE+1k2dSO48ffgeK--