FreeBSD 7.1 and BIND exploit

[Paul Schmehl]

--On Tuesday, July 22, 2008 10:27:42 -0700 Doug Barton <dougb at FreeBSD.org> 
wrote:

> Matthew Seaman wrote:
>
>> Are there any plans to enable DNSSEC capability in the resolver built
>> into FreeBSD?
>
> The server is already capable of it. I'm seriously considering enabling the
> define to make the CLI tools (dig/host/nslookup) capable as well (there is
> already an OPTION for this in ports).
>
> The problem is that _using_ DNSSEC requires configuration changes in
> named.conf, and more importantly, configuration of "trust anchors" (even for
> the command line stuff) since the root is not signed. It's not hard to do
> that with the DLV system that ISC has in place, and I would be willing to
> create a conf file that shows how to do that for users to include if they
> choose to. I am not comfortable enabling it by default (not yet anyway), it's
> too big of a POLA issue.
>

I just played around with it recently.  It's not that easy to understand 
initially *and* the trust anchors thing is a royal PITA.

Once you implement DNSSEC you *must* generate keys every 30 days.  So, I think, 
if you're going to enable it by default, there needs to be a script in periodic 
that will do all the magic to change keys every 30 days.  Maybe put vars in 
/etc/rc.conf to override the default key lengths and other portions of the 
commands that could change per installation.

If I were to implement it, I'd write a shell script to turn the keys over and 
cron it because doing it manually every 30 days ain't gonna happen.  Too many 
ways to forget to do it.  (I did the same for the root servers so that named.ca 
gets updated automagically every month.)

But until root is signed, it's not worth it for those of us who don't have 
dedicated staff doing dns only.

-- 
Paul Schmehl
As if it wasn't already obvious,
my opinions are my own and not
those of my employer.