From owner-freebsd-security Sat Jun 29 15:38:39 2002 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 BE89F37B400 for ; Sat, 29 Jun 2002 15:38:35 -0700 (PDT) Received: from star.sstec.com (adsl-216-102-148-67.dsl.lsan03.pacbell.net [216.102.148.67]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3ABF643E06 for ; Sat, 29 Jun 2002 15:38:35 -0700 (PDT) (envelope-from fbsd1@sstec.com) Received: from comm.sstec.com (comm.sstec.com [192.168.74.10]) by star.sstec.com (8.12.3/8.12.3) with ESMTP id g5TMcOiO012013 for ; Sat, 29 Jun 2002 15:38:34 -0700 (PDT) (envelope-from fbsd1@sstec.com) Message-Id: <5.1.0.14.2.20020629142257.0221e050@mail.sstec.com> X-Sender: (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Sat, 29 Jun 2002 14:38:29 -0700 To: security@FreeBSD.ORG From: John Long Subject: named 8.3.2-T1B vulnerable? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Running tag=RELENG_4_6 FreeBSD 4.6-RELEASE-p1 #2: Thu Jun 27 23:35:36 PDT 2002 4 boxes, 8 rebuilds, libc now this libbind thing. My named 8.3.2-T1B Thu Jun 27 22:17:53 PDT 2002 appears to be vulnerable. I just cvsuped and no changes other than ports. Any ideas on when/if the new bind will be getting to 4_6 ? I am trying to get way out of any town by July 3rd :-) I hope that this is the last for a few weeks too. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message