Date: Wed, 01 Aug 2007 12:13:35 -0700 From: Doug Barton <dougb@FreeBSD.org> To: Jeffrey Goldberg <jeffrey@goldmark.org> Cc: Zbigniew Szalbot <zbigniew@szalbot.homedns.org>, "A.G. Russell IV" <arussell@bifrost.hos.net>, Freebsd questions <freebsd-questions@freebsd.org> Subject: Re: Waiting for BIND security announcement Message-ID: <46B0DB5F.4020401@FreeBSD.org> In-Reply-To: <426DE541-FB51-44FF-B7F4-B34E0F9A7861@goldmark.org> References: <499c70c0707260136hea82f27s87dfa53432d0e409@mail.gmail.com> <94c6ae7ae570814564d364bfe9aad8ea@szalbot.homedns.org> <20070801030504.GA3773@bifrost.agrussell.com> <426DE541-FB51-44FF-B7F4-B34E0F9A7861@goldmark.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Jeffrey Goldberg wrote:
> It appears that BIND has only been fixed in -STABLE and -CURRENT, but
> not in -RELEASE. Does anyone know if there are plans to get this
> patched in 6.2?
>
> For me it makes little difference since I am not (yet) running named in
> a publicly accessible way. But my medium term plans for my DNS do
> involve me running a public nameserver on the latest RELEASE with all
> patches.
>
> It does worry me if this kind of thing doesn't get patched in the latest
> RELEASE.
Um, it doesn't work that way. "6.2-RELEASE" is just a symbolic name
that is related to the files that have the RELENG_6_2_0_RELEASE flag.
If you want to stay as close as possible to 6.2-RELEASE but also
include the fixes that the security officer deems important enough to
release widely, use the tag RELENG_6_2 (usually in your supfile for
cvsup or csup). If you want the latest code for 6-stable, which will
eventually become 6.3-RELEASE, use just RELENG_6.
When it comes to BIND stuff in particular, I always update the ports
first, so anyone with a mission critical DNS operation can get fixes
ASAP. There is even an option in the port to overwrite the base BIND
if you so desire.
hth,
Doug
--
This .signature sanitized for your protection
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46B0DB5F.4020401>