Re: DNSCurve vs. DNSSEC - FIGHT! (was OpenDNS today announced it has adopted DNSCurve to secure DNS)

Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> Thu, 25 February 2010 08:30 UTC

Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F219128C2D2 for <ietf@core3.amsl.com>; Thu, 25 Feb 2010 00:30:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level:
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d8FvH3EkMTrl for <ietf@core3.amsl.com>; Thu, 25 Feb 2010 00:30:25 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by core3.amsl.com (Postfix) with SMTP id E3B6328C189 for <ietf@ietf.org>; Thu, 25 Feb 2010 00:30:24 -0800 (PST)
Received: (qmail 80162 invoked from network); 25 Feb 2010 09:35:18 -0000
Received: from bmdi2189.bmobile.ne.jp (HELO necom830.hpcl.titech.ac.jp) (202.221.174.189) by necom830.hpcl.titech.ac.jp with SMTP; 25 Feb 2010 09:35:18 -0000
Message-ID: <4B863571.40604@necom830.hpcl.titech.ac.jp>
Date: Thu, 25 Feb 2010 17:31:45 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja-JP; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: ja, en
MIME-Version: 1.0
To: Nikos Mavrogiannopoulos <nmav@gnutls.org>
Subject: Re: DNSCurve vs. DNSSEC - FIGHT! (was OpenDNS today announced it has adopted DNSCurve to secure DNS)
References: <874c02a21002231826y613b9f97ya83740ba240f7bf9@mail.gmail.com> <ABE739C5ADAC9A41ACCC72DF366B719D02C29D87@GLKMS2100.GREENLNK.NET> <a123a5d61002240700i4a68367tf901b91265f79da1@mail.gmail.com> <1267039830.9710.11106.camel@shane-asus-laptop> <alpine.LSU.2.00.1002242049510.16971@hermes-2.csi.cam.ac.uk> <p06240819c7ab46c7fbf9@10.20.30.158> <4B859F15.9080106@acm.org> <4B85B7E5.1000104@necom830.hpcl.titech.ac.jp> <201002242347.o1ONlt7L023898@drugs.dv.isc.org> <4B85BF52.7030004@necom830.hpcl.titech.ac.jp> <c331d99a1002241619y47f91f50g4433a7233350dc74@mail.gmail.com> <4B85DBCA.2060407@necom830.hpcl.titech.ac.jp> <4B862D03.7060602@gnutls.org>
In-Reply-To: <4B862D03.7060602@gnutls.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 25 Feb 2010 08:30:26 -0000

Nikos Mavrogiannopoulos wrote:

>>In general, public key cryptography is scure only if public key
>>distribution is secure.

> Well as far as I know ssh works pretty well today

With plain old DNS, yes, ssh works pretty well today.

However, it should be noted that first ssh connection may be
misdirected, if plain old DNS is attacked.

That is, we know plain old DNS works pretty well today.

> and this model can be
> easy made verifiable (i.e. secure as you say) by the administrator
> verifying the keys of upstream.

Verifiability does not scale, which is why DNSSEC, or PKI in general,
is not really secure.

> Being "secure" heavily depends on what your requirements are

Requirements may vary.

However, my point is that DH (or equivalent elliptic curve cryptography)
does not add anything to simple nonce.

> Is a typical bank in europe secure? Can a
> general go with an armory division and take the money? Of course he can,
> but banks don't consider this a threat.

You, as a general, are free to assume typical ISPs in europe not
secure and packet snooping possible, which means you must say
DNSCurve insecure.

Or, you, as an ordinary person, are free to assume typical ISPs in
europe secure and packet snooping impossible, which means you must
say simple nonce secure.

							Masataka Ohta