From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Are we ready for DNSSEC ?
Date: Sun, 24 Jan 2010 17:20:22 -0500 [thread overview]
Message-ID: <9c691e6f5046087ab913668e1b42f8c8@ladd.quanstro.net> (raw)
In-Reply-To: <Pine.BSI.4.64.1001241211570.5454@malasada.lava.net>
On Sun Jan 24 17:15:17 EST 2010, newsham@lava.net wrote:
> > you are changing the topic.
> >
> > your original mail claimed to be worried
> > about man-in-the-middle attacks. that means
> > the attacker can respond to arbitrary traffic;
> > the fact that you can verify the dns response
> > is irrelevant if when you try to connect to the
> > correct ip address the attacker handles it
> > and you don't take advantage of ssl certificates
> > to catch that.
>
> True, unless DNS provides a certificate that is bound
> to the session in some way.
if one misdirects the original connection via dns and
then uses the renegotiation bug, is this not a
mitm attack?
- erik
next prev parent reply other threads:[~2010-01-24 22:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-20 13:26 maht
2010-01-20 13:42 ` erik quanstrom
2010-01-20 15:14 ` Patrick Kelly
2010-01-20 15:33 ` erik quanstrom
2010-01-20 16:39 ` Patrick Kelly
2010-01-20 16:49 ` erik quanstrom
2010-01-20 17:29 ` Patrick Kelly
2010-01-20 17:47 ` Russ Cox
2010-01-20 18:17 ` erik quanstrom
2010-01-20 20:11 ` Russ Cox
2010-01-20 19:13 ` Patrick Kelly
2010-01-23 23:59 ` John Barham
2010-01-24 0:42 ` erik quanstrom
2010-01-24 0:52 ` Russ Cox
2010-01-24 1:01 ` erik quanstrom
2010-01-24 1:11 ` Russ Cox
2010-01-24 1:18 ` erik quanstrom
2010-01-24 13:19 ` hiro
2010-01-24 14:57 ` erik quanstrom
2010-01-24 21:49 ` Russ Cox
2010-01-24 22:12 ` Tim Newsham
2010-01-24 22:20 ` erik quanstrom [this message]
2010-01-24 18:14 ` Tim Newsham
2010-01-25 20:45 ` Wes Kussmaul
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=9c691e6f5046087ab913668e1b42f8c8@ladd.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).