Re: [DNSOP] DNSSEC as a Best Current Practice

Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> Thu, 21 April 2022 13:40 UTC

Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A1F03A1592 for <dnsop@ietfa.amsl.com>; Thu, 21 Apr 2022 06:40:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
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 B3FvOdwRhC6W for <dnsop@ietfa.amsl.com>; Thu, 21 Apr 2022 06:40:11 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 4F2943A173F for <dnsop@ietf.org>; Thu, 21 Apr 2022 06:40:09 -0700 (PDT)
Received: (qmail 96874 invoked from network); 21 Apr 2022 13:35:47 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 21 Apr 2022 13:35:47 -0000
Message-ID: <05dd183d-7c5f-86a7-d265-c19b459f327f@necom830.hpcl.titech.ac.jp>
Date: Thu, 21 Apr 2022 22:40:06 +0900
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.8.0
Content-Language: en-US
To: Mukund Sivaraman <muks@mukund.org>
Cc: Paul Wouters <paul@nohats.ca>, "dnsop@ietf.org WG" <dnsop@ietf.org>
References: <57f1c37b-497c-e1a0-329c-4b9c8b7e197b@necom830.hpcl.titech.ac.jp> <A9F689C9-4ABF-4947-AA6B-56E2F0C17D13@nohats.ca> <9732682e-78e7-f6bf-84fc-685de22d5e12@necom830.hpcl.titech.ac.jp> <350d8ab8-0477-b656-8b08-56f7561a7fda@necom830.hpcl.titech.ac.jp> <CAH1iCiqkAPHq1QBKdkbh86j8UhimjEMG9DU15O9Tkch4BedBjg@mail.gmail.com> <0e2dffab-6afc-b1b6-9028-175f89f0d29e@necom830.hpcl.titech.ac.jp> <b3bf6748-be6d-a287-27e4-87af36ab10@nohats.ca> <dc4a21ee-cc4c-9cb1-9a56-b4992201378c@necom830.hpcl.titech.ac.jp> <c47227f6-5556-1e75-3a48-8aa6bad498ac@nohats.ca> <61b46811-fa52-5ec0-e16b-eb7e9d9560d4@necom830.hpcl.titech.ac.jp> <YlgtBwre0T/OZh4C@d1>
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
In-Reply-To: <YlgtBwre0T/OZh4C@d1>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/nUHrO973bM16ZsloS1b1YrYdbXM>
Subject: Re: [DNSOP] DNSSEC as a Best Current Practice
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Apr 2022 13:40:16 -0000

Mukund Sivaraman wrote:

>>
>>>> :  Third, all the CAs, including TLDs, pursuing commercial
>>>> :  success have very good appearance using such words as
>>>> :  "HSMs" or "four eyes minimum". That is, you can't
>>>> :  compare actual operational/physical strength from
>>>> :  their formal documents.
>>>
>>> This is an anecdote, that a logical reasoned argument.
>>
>> That's your anecdote to mention "HSMs" or "four eyes minimum"
>> proven to be useless by diginotar.
> 
> (From your posts in this thread, you appear well convinced that
>   cryptography is broken due to operational weaknesses in securing access
>   to signers. So I don't know if this will convince you differently.)

I'm afraid you miss my point that intermediate zones between
the first and the second parties are the third parties having
no knowledge of required security on transactions between the
first and the second parties.

That DNSSEC is not cryptographically or end-to-end secure
means third parties must be absolutely secure, which is,
as was demonstrated by diginoar, impossible.

OTOH, with the end-to-end security where secret information is
shared directly between the first and the second parties, the
parties know the degree of the required security.

> HSMs don't have anything to do with DNSSEC's security guarantee.

If so, feel free to put private keys accesible from general public.

> An operational decision
> leading to weakness doesn't mean that the cryptographic foundation of
> DNSSEC is broken or cannot be secured.

Of course. DNSSEC, certainly, has some components which is
cryptographically secure.

But, as you should know, security of a system depends on the
weakest components of the system.

As such, that some secure components are secure do not
mean the system is secure.

> On the topic of leak of private key or access to signers by rogue
> parties, there have been experiments to use threshold cryptography
> with DNSSEC where the actual private key is not present in any > single form, but distributed as "key shares" among N parties, and
> "signature shares" are generated separately by M out of N parties
 > and combined to make the final signature.

Relying on two or more third parties is no better than relying on
single third party, when all of them are not cryptographically
but physically secure.

As was demonstrated by diginotar, "four eyes minimum" is not
so secure. So are six or more eyes.


							Masataka Ohta