Re: [Asrg] DNSSEC is NOT secure end to end

Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> Wed, 03 June 2009 00:11 UTC

Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E8F1F3A6C3F for <asrg@core3.amsl.com>; Tue, 2 Jun 2009 17:11:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.553
X-Spam-Level: *
X-Spam-Status: No, score=1.553 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_NJABL_PROXY=1.643]
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 MDam+9Yqi5kk for <asrg@core3.amsl.com>; Tue, 2 Jun 2009 17:11:23 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by core3.amsl.com (Postfix) with SMTP id 749E23A6AEB for <asrg@irtf.org>; Tue, 2 Jun 2009 17:11:23 -0700 (PDT)
Received: (qmail 47315 invoked from network); 3 Jun 2009 01:35:31 -0000
Received: from softbank219001188006.bbtec.net (HELO necom830.hpcl.titech.ac.jp) (219.1.188.6) by necom830.hpcl.titech.ac.jp with SMTP; 3 Jun 2009 01:35:31 -0000
Message-ID: <4A25BE02.5090901@necom830.hpcl.titech.ac.jp>
Date: Wed, 03 Jun 2009 09:04:18 +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: Paul Wouters <paul@xelerance.com>
References: <200905302032.n4UKVxaZ048822@givry.fdupont.fr> <4A21C0CB.8070409@necom830.hpcl.titech.ac.jp> <8EFB68EAE061884A8517F2A755E8B60A1EF83F8661@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com> <4A252B54.6020508@necom830.hpcl.titech.ac.jp> <alpine.LFD.1.10.0906021313240.32260@newtla.xelerance.com>
In-Reply-To: <alpine.LFD.1.10.0906021313240.32260@newtla.xelerance.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 03 Jun 2009 12:09:27 -0700
Cc: "ietf@ietf.org" <ietf@ietf.org>, Anti-Spam Research Group - IRTF <asrg@irtf.org>
Subject: Re: [Asrg] DNSSEC is NOT secure end to end
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Jun 2009 00:11:24 -0000

Paul Wouters wrote:

> I can't preload 50 million keys. I cannot build trust relations
> with 50 millions domains. Just like we could not preload 50
> million nameserver pointers.

That is the essential point of the paper of David Clark:

	These certificates are principal components of essentially
	all public key schemes, except those that are so small in
	scale that the users can communicate their public keys to
	each other one to one, in an ad hoc way that is mutually
	trustworthy.

A credit card brand (VISA, for example) may manage more than
50 million PIN numbers. But, it uses agents to do so. The security
of the system depends on not only (cryptographical) security between
the brand holder and agents but also social security of the agents.

Though 4 digit PIN or 16 bit message ID of DNS is cryptographically
not very secure, it is a cryptographical issue of each hop, having
nothing to do with social security between hops, introduction of
which is inevitable for large infrastructures.

						Masataka Ohta