Re: [DNSOP] DNSSEC as a Best Current Practice

Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> Mon, 21 March 2022 14:30 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 472183A18F0 for <dnsop@ietfa.amsl.com>; Mon, 21 Mar 2022 07:30:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] 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 k7Wu5imNDINL for <dnsop@ietfa.amsl.com>; Mon, 21 Mar 2022 07:30:46 -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 92F073A18BF for <DNSOP@ietf.org>; Mon, 21 Mar 2022 07:30:46 -0700 (PDT)
Received: (qmail 50201 invoked from network); 21 Mar 2022 14:26:56 -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 Mar 2022 14:26:56 -0000
Message-ID: <7eac08b9-9652-dd56-b48b-90514a42ae8d@necom830.hpcl.titech.ac.jp>
Date: Mon, 21 Mar 2022 23:30:42 +0900
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0
Content-Language: en-US
To: DNSOP@ietf.org
References: <6d46abd6-60ca-d896-6408-fe83a83895cf@necom830.hpcl.titech.ac.jp> <6B319F45-B5B6-4CB7-8E74-EA3651296C0E@nohats.ca>
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
In-Reply-To: <6B319F45-B5B6-4CB7-8E74-EA3651296C0E@nohats.ca>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Lss8QiW0kaMQ8mnbpI-fdZxkl3U>
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: Mon, 21 Mar 2022 14:30:51 -0000

Paul Wouters wrote:

> You claim DNS can be secured if we somehow securely know all the IPs
> of all nameservers of parent zones, for which the only source is DNS.
> How do you propose to fulfill your own stated requirement without
> DNSSEC?

Securely configuring IP addresses of root servers, which can
recursively assure data origin security of child servers, is
as easy/difficult as securely configuring root certificates.

So?

>> Are you saying connecting to an IP address secured by DNSSEC is
>> safe even under BGP attacks?
> 
> Yes. Obviously the attacker can deny the actual real DNS content but
> sending their own made up DNS data is ignored due to data origin
> protection.

Wrong.

With BGP attacks, your packet with an DNSSEC secured destination IP
address is delivered elsewhere.

> Please refrain from ad hominem attacks if you wish to continue to
> discuss.

I'm afraid it is you who want to discontinue discussion.

>> Country X legally forcing people to install government provided 
>> root certificates can freely spoof PKI, including DNSSEC, data of
>> country Y.

> No they cannot. I can give you root access to a nameserver for
> nohats.ca and you still can't create a "proof.nohats.ca"

It is trivially easy with root zone certificate recognized by
end users to forge RRs of "nohats.ca" and "proof.nohats.ca".

> If you only handwave your claims,

I'm afraid it is you who is handwaving with such unfounded
statement:

    it just
    indicates that the value of deploying DNSSEC is often considered
    lower than the cost.

						Masataka Ohta