From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] dns exploits (self-promotion remix)
Date: Sun, 27 Jul 2008 23:48:35 -0400 [thread overview]
Message-ID: <101ce9cb4e14907be1f9cd2519fe158e@quanstro.net> (raw)
In-Reply-To: <488D35A2.5080806@gmail.com>
> > 2. who does recursive queries on external interfaces?
> > i would have considerd this a configuration error and
> > security problem ten years ago.
> >
>
> Tell that to the rest of the internet.
without reasonable configuration, most any machine can
be made trivially vulnerable.
> vectors that are just as predictable because of the
> luxury of web2.0. Recursive queries obviously just
> make this simpler for the attacker.
what is this "web 2.0" of which you speak? i use
plan 9 and unfamilar with such as i presume to be jargon. ☺
to do it from the inside, one requires out-of-balliwick
hints to be cached, right? this should be a big hurdle.
it's dissapointing to note that plan 9 dns does no hint
validation. that is perhaps a larger long-known, and
still-exploitable hole than the one that gets so much press.
i think it would be best if ndb/dns simply did not reply
with answers obtained from glue but rather re-queried
the authorative ns *and* rejected out-of-balliwick
hints.
- erik
next prev parent reply other threads:[~2008-07-28 3:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <261342.6156.qm@web27004.mail.ukl.yahoo.com>
2008-07-27 13:18 ` erik quanstrom
2008-07-27 15:56 ` Russ Cox
2008-07-27 15:57 ` erik quanstrom
2008-07-27 16:19 ` Russ Cox
2008-07-27 22:20 ` don bailey
2008-07-28 1:16 ` erik quanstrom
2008-07-28 2:53 ` a
2008-07-28 2:57 ` don bailey
2008-07-28 3:48 ` erik quanstrom [this message]
2008-07-28 20:53 ` Wes Kussmaul
2008-07-27 22:22 ` don bailey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=101ce9cb4e14907be1f9cd2519fe158e@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).