From owner-freebsd-questions@FreeBSD.ORG Thu Dec 18 19:21:41 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 732CB16A4CE for ; Thu, 18 Dec 2003 19:21:41 -0800 (PST) Received: from obsecurity.dyndns.org (adsl-63-207-60-234.dsl.lsan03.pacbell.net [63.207.60.234]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1303643D1F for ; Thu, 18 Dec 2003 19:21:40 -0800 (PST) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 9985866BAA; Thu, 18 Dec 2003 19:21:39 -0800 (PST) Date: Thu, 18 Dec 2003 19:21:39 -0800 From: Kris Kennaway To: Miguel Mendez Message-ID: <20031219032139.GD55360@xor.obsecurity.org> References: <20031216191701.M14568@Robert-Eckardt.de> <20031217042810.GA31507@xor.obsecurity.org> <20031218102846.M37848@Robert-Eckardt.de> <20031218142522.GC48442@xor.obsecurity.org> <20031218162618.2b6a08ce.flynn@energyhq.es.eu.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="SO98HVl1bnMOfKZd" Content-Disposition: inline In-Reply-To: <20031218162618.2b6a08ce.flynn@energyhq.es.eu.org> User-Agent: Mutt/1.4.1i cc: questions@FreeBSD.org cc: Robert.Eckardt@Robert-Eckardt.de cc: Kris Kennaway Subject: Re: DOS of named X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Dec 2003 03:21:41 -0000 --SO98HVl1bnMOfKZd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Dec 18, 2003 at 04:26:18PM +0100, Miguel Mendez wrote: > ./Kris Kennaway wrote: >=20 > > I was; if you're complaining about bugs in old versions of the > > software, then the first thing to do is check whether those bugs have > > been fixed in later versions. Not all bug fixes are properly > > documented. >=20 > See > ftp://ftp.netbsd.org/pub/NetBSD/security/advisories/NetBSD-SA2003-018.txt= .asc >=20 > Apparently, the NetBSD security team does fix those bugs, so I assume > the FreeBSD people can as well. Sorry, what was your point? This bug was fixed in FreeBSD too, as you could have discovered by spending 10 seconds to look at the advisories. But we weren't talking about this one, because the OP claimed to have checked the BIND ChangeLogs and found that his problem had not been referenced. > > OK, so you've done some further research about this (or just omitted > > this from the original message). The BIND mailing list may still be > > your best bet for discussion of this issue, despite previous lack of > > solution there. >=20 > FreeBSD is the vendor in this case, as bind is part of base, so it's > FreeBSD people the ones to ask about the product they ship. He's welcome to ask, but my advice was that BIND experts are lower on the ground here than on the BIND support list. Kris --SO98HVl1bnMOfKZd Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/4m7DWry0BWjoQKURAoisAJ9LR9AHBDA/eQMW5Aehy4vxZSjqwQCg35UW 9D0iDBBndGWCDThEnwreNN8= =icEL -----END PGP SIGNATURE----- --SO98HVl1bnMOfKZd--