SANS: DNS Bug Now Public?
jmamodio at gmail.com
Wed Jul 23 11:16:26 CDT 2008
Let me add that folks need to understand that the "patch" is not a fix to a
problem that has been there for long time and
it is just a workaround to reduce the chances for a potential
attack, and it must be combined with best practices and
recommendations to implent a more robust DNS setup.
There are plenty of documents out there (check cert.org for example) that
can provide some guidance.
Perhaps this situation will help move things on the DNSSEC front, as far as
I remember there are some IETF drafts on
the standards track addressing these issues.
On Wed, Jul 23, 2008 at 2:31 AM, Steven M. Bellovin <smb at cs.columbia.edu>
> On Tue, 22 Jul 2008 08:00:51 -0500
> "Jorge Amodio" <jmamodio at gmail.com> wrote:
> > It has been public for a while now. Even on the print media, there
> > are some articles about it on the latest Computerworld mag without
> > giving too much detail about how to exploit it.
> > ie PATCH NOW !!!
> Kaminsky's blog says "Patch. Today. Now. Yes, stay late."
> --Steve Bellovin, http://www.cs.columbia.edu/~smb
More information about the NANOG