From: "David P. Reed" <dpreed@reed.com>
To: Maciej Soltysiak <maciej@soltysiak.com>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] "DNSSEC considered harmful"
Date: Fri, 09 May 2014 21:30:58 -0400 [thread overview]
Message-ID: <fabd397c-0e85-45df-a410-49826d73af9b@katmail.1gravity.com> (raw)
In-Reply-To: <CAMZR1YDRXoEwO4su_ZhrzS1Y-zczzmXE8xp4pSSkqrQT2cYy2Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1150 bytes --]
Reading a lot of this stuff suggests at most that DNSSEC is being overhyped and poorly implemented.
As a reason to abandon work on deploying DNSSEC so that it's easier to instantiate man in the middle attacks I find it unconvincing.
Is there an alternative?
On May 8, 2014, Maciej Soltysiak <maciej@soltysiak.com> wrote:
>Hi,
>
>I read a twitter conversation last night where somebody said DNSSEC is
>harmful. I asked why and I got this littany of issues:
>http://ianix.com/pub/dnssec-outages.html
>
>I was blown away not only by the sheer evidence of outages, but
>especially
>by the quotes in last sections: Miscellaneous and What a mess.
>
>I don't know, have a look, I just wanted to share as I wasn't aware of
>things that didn't go well with DNSSEC. I'm not suggesting anything re
>Cerowrt here.
>
>Best regards,
>Maciej
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Cerowrt-devel mailing list
>Cerowrt-devel@lists.bufferbloat.net
>https://lists.bufferbloat.net/listinfo/cerowrt-devel
-- Sent from my Android device with K-@ Mail. Please excuse my brevity.
[-- Attachment #2: Type: text/html, Size: 1416 bytes --]
next prev parent reply other threads:[~2014-05-10 1:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-08 9:32 Maciej Soltysiak
2014-05-09 8:38 ` Mikael Abrahamsson
2014-05-09 15:15 ` Dave Taht
2014-05-10 1:30 ` David P. Reed [this message]
2014-05-11 13:43 ` Török Edwin
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=fabd397c-0e85-45df-a410-49826d73af9b@katmail.1gravity.com \
--to=dpreed@reed.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=maciej@soltysiak.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