From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Maciej Soltysiak <maciej@soltysiak.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] "DNSSEC considered harmful"
Date: Fri, 9 May 2014 10:38:43 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.02.1405091035560.29282@uplift.swm.pp.se> (raw)
In-Reply-To: <CAMZR1YDRXoEwO4su_ZhrzS1Y-zczzmXE8xp4pSSkqrQT2cYy2Q@mail.gmail.com>
On Thu, 8 May 2014, Maciej Soltysiak 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.
The failure mode of encrypted and authenticated communications is
catastrophic failure (=nothing works). There are plenty people who says
the "proceed anyway" option in modern browsers when the certificate
failures occur, is wrong and the user shouldn't be allowed to continue.
This is why security is so hard, because secsurity protects against a
potential and unknown attack, whereas when it doesn't work, you fail
completely and the user just wants things to work so they'd rather turn
security off and proceed anyway.
--
Mikael Abrahamsson email: swmike@swm.pp.se
next prev parent reply other threads:[~2014-05-09 8:38 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 [this message]
2014-05-09 15:15 ` Dave Taht
2014-05-10 1:30 ` David P. Reed
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=alpine.DEB.2.02.1405091035560.29282@uplift.swm.pp.se \
--to=swmike@swm.pp.se \
--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