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:
edgeos



Bugtraq: Re: Comments re ISC's announcement on bind9 security

Re: Comments re ISC's announcement on bind9 security

From: Tim <tim-security_at_sentinelchicken.org>
Date: Thu, 1 Nov 2007 16:50:20 -0400

> It _is_ a 16 bit ID space, and that is not fixable inside the strict
> DNS protocol, but that still leaves us room to do the best job with
> what we have, rather than do nothing at all. Some people appear to be
> on the edge of arguing that we do nothing.

I have to agree with Theo on this. It doesn't help a lot in theory, but
it helps quite a bit in practice. Note that in spoofing responses one
does typically have timing issues involved which makes it tougher than
just guessing one of 65536 values alone.

On another note, why is it that everyone arguing the all-or-nothing case
likes to ignore the other very-usable-now mitigation of randomizing
source ports? I don't use BIND and I don't care to check it's current
behavior, but has the ISC finally gotten around to randomizing the
source ports? If not, why not? The extra few bits of entropy can go a
long way, particularly if a good PRNG is used.

tim
Received on Nov 01 2007

[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]