From: Valdis.Kletnieks@vt.edu
To: Anders Kaseorg <andersk@mit.edu>
Cc: cerowrt-devel@lists.bufferbloat.net, dnsmasq-discuss@thekelleys.org.uk
Subject: Re: [Cerowrt-devel] Problems with DNSsec on Comcast, with Cero 3.10.38-1/DNSmasq 4-26-2014
Date: Fri, 03 Oct 2014 13:28:05 -0400 [thread overview]
Message-ID: <47625.1412357285@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Fri, 03 Oct 2014 05:28:35 -0400." <542E6C43.9030002@mit.edu>
[-- Attachment #1: Type: text/plain, Size: 473 bytes --]
On Fri, 03 Oct 2014 05:28:35 -0400, Anders Kaseorg said:
> This bottom-up algorithm also seems to have a security problem that’s
> just as bad as one with the top-down algorithm that you rejected below.
> Consider the same department.campus.university.edu example, where
> campus and edu are signed zones, and university is not a zone.
This issue is why trust anchors were devised so people could start deploying
DNSSEC before stuff like .COM got signed.
[-- Attachment #2: Type: application/pgp-signature, Size: 848 bytes --]
next prev parent reply other threads:[~2014-10-03 17:28 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 16:55 Jim Gettys
2014-04-28 17:03 ` Dave Taht
2014-04-28 18:37 ` Dave Taht
2014-04-28 18:56 ` Dave Taht
2014-04-28 19:32 ` [Cerowrt-devel] [Dnsmasq-discuss] " Simon Kelley
2014-04-28 19:45 ` Aaron Wood
2014-04-28 23:24 ` Phil Pennock
2014-04-29 13:22 ` Simon Kelley
2014-04-29 20:57 ` Phil Pennock
2014-04-30 17:26 ` Dave Taht
2014-05-01 18:37 ` Simon Kelley
2014-05-01 20:26 ` Rich Brown
2014-05-01 22:27 ` Dave Taht
2014-05-02 14:30 ` Sebastian Moeller
2014-05-01 18:35 ` Simon Kelley
2014-05-02 16:40 ` James Cloos
2014-10-03 9:28 ` [Cerowrt-devel] " Anders Kaseorg
2014-10-03 17:28 ` Valdis.Kletnieks [this message]
2014-10-03 21:35 ` Anders Kaseorg
2014-10-04 21:45 ` Anders Kaseorg
2015-01-08 16:34 ` Simon Kelley
2015-01-08 17:44 ` Dave Taht
2015-01-08 18:07 ` Simon Kelley
2015-01-08 19:52 ` Dave Taht
2015-01-09 8:52 ` Dave Taht
2015-01-09 15:36 ` Simon Kelley
2015-01-09 16:49 ` Simon Kelley
2015-01-09 21:34 ` Dave Taht
2015-01-10 15:37 ` Simon Kelley
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=47625.1412357285@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=andersk@mit.edu \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dnsmasq-discuss@thekelleys.org.uk \
/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