Re: https at ietf.org

Ted Lemon <ted.lemon@nominum.com> Mon, 25 November 2013 23:58 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF8291AE0BA for <ietf@ietfa.amsl.com>; Mon, 25 Nov 2013 15:58:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PWQ4mEgqjRXl for <ietf@ietfa.amsl.com>; Mon, 25 Nov 2013 15:58:17 -0800 (PST)
Received: from exprod7og124.obsmtp.com (exprod7og124.obsmtp.com [64.18.2.26]) by ietfa.amsl.com (Postfix) with ESMTP id 694A31AE07F for <ietf@ietf.org>; Mon, 25 Nov 2013 15:58:17 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob124.postini.com ([64.18.6.12]) with SMTP ID DSNKUpPkGXjjmi/tZUlJfTMF7X6bblB0LNQG@postini.com; Mon, 25 Nov 2013 15:58:17 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 7E9341B822B for <ietf@ietf.org>; Mon, 25 Nov 2013 15:58:17 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 6681D19005C for <ietf@ietf.org>; Mon, 25 Nov 2013 15:58:17 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 25 Nov 2013 15:58:17 -0800
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
Subject: Re: https at ietf.org
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <alpine.BSF.2.00.1311251833400.57383@joyce.lan>
Date: Mon, 25 Nov 2013 18:58:14 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <DCC0C5E5-A69E-4FBD-B666-BD6E58F0979D@nominum.com>
References: <20131125180608.55454.qmail@joyce.lan> <E5836934-317D-4E73-80CC-B8847047852A@virtualized.org> <alpine.BSF.2.00.1311251833400.57383@joyce.lan>
To: IETF-Discussion Discussion <ietf@ietf.org>
X-Mailer: Apple Mail (2.1822)
X-Originating-IP: [192.168.1.10]
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Nov 2013 23:58:18 -0000

(1) I'm not trying to impugn the good work that was done in securing the root key.   It was good work, and I think it was very cool.   I am just asking if, despite that good work, an NSL could get around it.   It's a fair question.   The answer may be "no," or "not without it becoming public," or "with great difficulty."   I doubt it's "easily."   But it's worth asking.   When you did the root signing, we were certainly thinking about this threat model, but it was a bit more academic then than it is now.   I think we still had some illusions that the U.S. government at least would choose a more constrained attack than taking the key to everything; we now know that the government feels no such burden of restraint—they apparently feel that they can be trusted with that key, and we should be willing to provide it.

(2) This attack is actually easier on TLDs than on the root, so I really asked the wrong question.   Although taking the root would be useful, it would be less useful than taking .COM and .ORG and .EDU.   With any of those keys, your chances of doing a mass attack on a single DANE-secured domain are much better.

(3) So, are they all as secure as the root?