From: Ranganathan Krishnan <rk@selwastor.com>
To: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
"<ow-tech@eff.org>" <ow-tech@eff.org>
Subject: [Cerowrt-devel] DNSSEC
Date: Tue, 10 Feb 2015 16:57:07 -0800 [thread overview]
Message-ID: <C84DD31E-7F6C-48AB-A512-27E6A24663F0@selwastor.com> (raw)
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/
CeroWRT put in work to include DNSSEC so there must be folks on the CeroWRT
list who don't see it that way. I would appreciate any pointers to discussions refuting
the points made in the blog post above. If the points made in the blog post stand
there would not be any reason to include DNSSEC in the openwireless router. So,
I am looking for counterpoints that might establish that DNSSEC could have value.
Thanks,
Ranga
next reply other threads:[~2015-02-11 0:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-11 0:57 Ranganathan Krishnan [this message]
[not found] ` <op.xtvb9gnsbgbjo9@work-pc.lan>
2015-02-11 1:51 ` [Cerowrt-devel] [Ow-tech] DNSSEC Dave Taht
2015-02-11 1:56 ` [Cerowrt-devel] DNSSEC Valdis.Kletnieks
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=C84DD31E-7F6C-48AB-A512-27E6A24663F0@selwastor.com \
--to=rk@selwastor.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=ow-tech@eff.org \
/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