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
For those of you keeping score, here are the (very unscientific) tallied
repro reports so far on this issue:
OS Yes No
BSDi 4.01
BSD/OS 4.1 1
BSD/OS 4.2 1
Debian 2.2 3
FreeBSD 2.26
Hi,
After two days of recieving comments on my original posting and doing some
testing, here's a summary:
* The 'bug' seems to manifest itself randomly. Named on my machine crashes
maybe 1 in 5 tries. This might explain why relatively few people were able to
reproduce it.
* Running nmap
More repro reports. If no credit is given it is because the report was
emailed to me and not the list, and I don't want to get anybody in
trouble...
---
I have tried nmap -O -sT -p 53 against a few hosts under my thumbs:
the most hosts are Linux 2.2 but one FreeBSD
This appears to not be as big a problem as it might have seemed, based
on the original report.
---
From: Jonas Thambert [EMAIL PROTECTED]
I wasnt able to replicate this error on a
fully patched RH 7.0 with BIND 9.1.0.
More repro reports etc:
From: Stephen Oberther [EMAIL PROTECTED]
Hmmm..it doesn't have the same affect on our machine. i386 with Debian
2.2 running a home compiled BIND-9.1.0 Must be something in the
configuration of the NetBSD package.
