Nmap Security Scanner
*Intro
*Ref Guide
*Install Guide
*Download
*Changelog
*Book
*Docs
Security Lists
*Nmap Hackers
*Nmap Dev
*Bugtraq
*Full Disclosure
*Pen Test
*Basics
*More
Security Tools
*Pass crackers
*Sniffers
*Vuln Scanners
*Web scanners
*Wireless
*Exploitation
*Packet crafters
*More
Site News
Site Search:
Exploit World
Advertising
About/Contact
Credits
Sponsors:




bugtraq logo Bugtraq mailing list archives

Re: Bug in Bind 9.1.0?
From: Maarten de Vries <Maarten.de.Vries () netraam com>
Date: Fri, 9 Feb 2001 14:04:22 +0100

On Wednesday, February 07, 2001, 11:15:48 PM, I wrote:

I believe ISC is still investigating this. Haven't heard from the
FreeBSD people yet, altough they were the first I reported this to...

In  the  meantime, I was informed by Doug Barton (who maintains the Bind
port  in  FreeBSD)  that  "the  FreeBSD  team is currently investigating
solutions  to  the  problems  brought to light by version 9.1.0 of BIND.
Meanwhile,  our  port  of  BIND  9  has been updated to use BIND version
9.1.1rc1  which, in addition to significant bug fixes contains code that
turns those failure modes into logged warnings".

Those warnings look like this:

Feb  9 13:56:04 tel named[88689]: socket.c:1673: unexpected error:
Feb  9 13:56:04 tel named[88689]: socket.c:1673: unexpected error:
Feb  9 13:56:04 tel named[88689]: internal_accept(): accept() returned peer address family 0 (expected 2)
Feb  9 13:56:04 tel named[88689]: internal_accept(): accept() returned peer address family 0 (expected 2)

It doesn't indeed crash anymore.
Upgrading time, then :-)

--
Maarten


  By Date           By Thread  

Current thread:
  • Re: Bug in Bind 9.1.0? Maarten de Vries (Feb 10)
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]