Re: [DNSOP] DNSSEC as a Best Current Practice

Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> Mon, 21 March 2022 13:23 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 E1EF13A0489 for <dnsop@ietfa.amsl.com>; Mon, 21 Mar 2022 06:23:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 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] 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 w_H-_B8pjFIa for <dnsop@ietfa.amsl.com>; Mon, 21 Mar 2022 06:23:29 -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 9B1D73A0121 for <dnsop@ietf.org>; Mon, 21 Mar 2022 06:23:27 -0700 (PDT)
Received: (qmail 49413 invoked from network); 21 Mar 2022 13:19:37 -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 13:19:37 -0000
Message-ID: <aef8ac55-77b2-5608-72fe-daed7940eaaf@necom830.hpcl.titech.ac.jp>
Date: Mon, 21 Mar 2022 22:23:23 +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: <7aaed092-8877-ec15-9b7b-5d488e383d04@necom830.hpcl.titech.ac.jp> <7C43871E-60AF-485D-8AB3-65E72539F831@nohats.ca> <59fdc791-4482-141b-03b4-bc27e8824f31@necom830.hpcl.titech.ac.jp> <CAPt1N1maPf2zrEkyXL1yqkkNbVOR6sUyLXZv2Lc_r4=iVhVO=w@mail.gmail.com> <3035599f-bcb9-b753-54bc-32f61683a0e5@necom830.hpcl.titech.ac.jp> <CAPt1N1nx78t9or38S-zNbV2bSyYnQNmGnwzQ0FZX+fTvu=DpAQ@mail.gmail.com>
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
In-Reply-To: <CAPt1N1nx78t9or38S-zNbV2bSyYnQNmGnwzQ0FZX+fTvu=DpAQ@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/oHlpTPGjGjxvxNsuJ0fs1g12egw>
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 13:23:33 -0000

Ted Lemon wrote:

> Ohta-san, I think the points you are making in response to what I have said
> are that
> 
> (1) it's easier for a government to fake a DNS delegation than to MiTM an
> IP connection, and
> (2) if it's a government that's faking your DNS, they can jail you for
> noticing.

You miss my point that compromising employees of ISPs or zones by, say,
kidnapping their children.

> I think these are both valid points. However, I don't think they lead to
> the conclusion you are drawing. First, if the government really cares about
> censorship,

Censorship? Fake news are obviously better.

> To the second question, this is also absolutely true, but at the same time,
> as we can see, just because something is illegal doesn't mean that it's not
> useful. E.g., the government in Russia has made it illegal to protest the
> war in Ukraine, and yet we see people protesting in the streets. Their goal
> is pretty clearly to bypass a government restriction on communication.

Be also aware of fake news produced against Russia by some governments.

> Having a watchdog in software that notices when a certificate has been
> replaced by one that isn't valid isn't that hard, and while it might be
> made illegal after the fact, officially making it illegal would be a public
> act that would have to be announced by the government in order to be
> enforceable—otherwise software vendors would have no reason to know they
> were violating the law.

The point is what, if any, can DNSSEC do against it.

> By announcing it, the government in question is
> disclosing the status of your security, which is the whole point.

But, justice defined by the government is the justice for those
who are under control of the government.

 > Absent
 > such a disclosure, citizens can continue to run such software, and
 > continue to detect such attacks.

Though it can be a criminal offense against local justice.


						Masataka Ohta