From: Valdis.Kletnieks@vt.edu
To: Ranganathan Krishnan <rk@selwastor.com>
Cc: "<ow-tech@eff.org>" <ow-tech@eff.org>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] DNSSEC
Date: Tue, 10 Feb 2015 20:56:54 -0500 [thread overview]
Message-ID: <133804.1423619814@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Tue, 10 Feb 2015 16:57:07 -0800." <C84DD31E-7F6C-48AB-A512-27E6A24663F0@selwastor.com>
[-- Attachment #1: Type: text/plain, Size: 1325 bytes --]
On Tue, 10 Feb 2015 16:57:07 -0800, Ranganathan Krishnan said:
> I am looking into ways to improve DNS on the openwireless router software.
> When I mentioned DNSSEC as one of the items to review, I received this
> response from one of the developers.
>
> http://sockpuppet.org/blog/2015/01/15/against-dnssec/
Right off the bat:
"But it doesn't make those attacks infeasible, so sites still need to adopt
secure transports like TLS. With TLS properly configured, DNSSEC adds nothing."
Which makes the rash assumption that it's appropriate to use TLS for everything.
For starters, consider NTP or any other UDP-based system, or any TCP-based
protocol that uses something other than TLS.
"Had DNSSEC been deployed 5 years ago, Muammar Gaddafi would have controlled
BIT.LY's TLS keys."
Actually, whoever controlled the master for .LY would have controlled BIT.LY,
whether or not DNSSEC was in play. If Gaddafi had control of .LY, he could have
redirected BIT.LY anywhere he wanted without keys, so the situation is no
worse. What DNSSEC does is prevent a Gaddafi that *doesn't* control .LY from
swiping control of your view of .LY (including BIT.LY) out from under you.
Or your view of .COM, which would probably matter just a tad more to you...
I'll let somebody else debunk the rest, I quit reading at that point. :)
[-- Attachment #2: Type: application/pgp-signature, Size: 848 bytes --]
prev parent reply other threads:[~2015-02-11 1:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-11 0:57 Ranganathan Krishnan
[not found] ` <op.xtvb9gnsbgbjo9@work-pc.lan>
2015-02-11 1:51 ` [Cerowrt-devel] [Ow-tech] DNSSEC Dave Taht
2015-02-11 1:56 ` Valdis.Kletnieks [this message]
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=133804.1423619814@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=ow-tech@eff.org \
--cc=rk@selwastor.com \
/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