From owner-freebsd-security Thu Feb 22 5:58:20 2001 Delivered-To: freebsd-security@freebsd.org Received: from awww.jeah.net (awww.jeah.net [216.111.239.130]) by hub.freebsd.org (Postfix) with ESMTP id 353B337B67D for ; Thu, 22 Feb 2001 05:58:10 -0800 (PST) (envelope-from chris@jeah.net) Received: from localhost (chris@localhost) by awww.jeah.net (8.11.1/8.11.0) with ESMTP id f1MDuFM92669; Thu, 22 Feb 2001 07:56:15 -0600 (CST) (envelope-from chris@jeah.net) Date: Thu, 22 Feb 2001 07:56:14 -0600 (CST) From: Chris Byrnes To: Michael Richards Cc: Subject: Re: Bind problems In-Reply-To: <3A947710.000009.60978@frodo.searchcanada.ca> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Anything before -REL is succeptable to the vulns. I was running 8.2.3-T6B as well, and assumed because the 8.2.3 was there that I was fine. Then I did some further reading and found out "oops". -cb On Wed, 21 Feb 2001, Michael Richards wrote: > Since the big BIND vulnerability, I checked all my versions of BIND > to make sure they weren't the 8.2.2 variety. None were. > > Most returned: named 8.2.3-T6B Thu Nov 23 19:00:06 EST 2000 > Which is not supposed to be vulnerable. > > Not too long after the exploit became publically widespread, I > noticed that my bind was randomly crashing. This machine had run for > months without any sort of bind problem. I should kept the core files > but I did notice that they segfaulted at location 0x41414141. > > This looked a little suspicious to me so I immediately cvsuped. The > new version is: named 8.2.3-REL Sun Feb 18 11:47:44 EST 2001 and has > not crashed since the 18th when I compiled it. Before it was crashing > daily. > > Any ideas if named 8.2.3-T6B in 4.2-RELEASE has problems? > > -Michael > _________________________________________________________________ > http://fastmail.ca/ - Fast Free Web Email for Canadians To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message