Re: [dns-privacy] [Ext] Threat Model

Paul Wouters <paul@nohats.ca> Fri, 08 November 2019 23:11 UTC

Return-Path: <paul@nohats.ca>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DAB81200D5 for <dns-privacy@ietfa.amsl.com>; Fri, 8 Nov 2019 15:11:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
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 VEWvKPdrH9xq for <dns-privacy@ietfa.amsl.com>; Fri, 8 Nov 2019 15:11:50 -0800 (PST)
Received: from mx.nohats.ca (mx.nohats.ca [IPv6:2a03:6000:1004:1::68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6EEF2120026 for <dns-privacy@ietf.org>; Fri, 8 Nov 2019 15:11:23 -0800 (PST)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 478wxh0dSdzFkH; Sat, 9 Nov 2019 00:11:20 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1573254680; bh=scRvt0l7MqLjlbfkhByVGjQ6JOllDBXXCj1y7C17bJ8=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=c6h76rLeRd8g4lyjf1BzPNY/IrsAtXYDnTZ644HC114XJlpOJ1oK0Kasr3ZEFzDkN dyKcmvHX6m2o7mH0HrUQzwefA6eZGEgL4I1tVut62/4csw57AtsKLsr0zULGtHxtjx 5fQmLm+ea227L91bMXFnlAtXidX93+zm3PudzUX4=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id UXp7SD_Kcu45; Sat, 9 Nov 2019 00:11:18 +0100 (CET)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Sat, 9 Nov 2019 00:11:18 +0100 (CET)
Received: from [193.111.228.74] (unknown [193.111.228.74]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bofh.nohats.ca (Postfix) with ESMTPSA id A4FFE607C99F; Fri, 8 Nov 2019 18:11:17 -0500 (EST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (1.0)
From: Paul Wouters <paul@nohats.ca>
X-Mailer: iPhone Mail (16G102)
In-Reply-To: <CA+nkc8D1uvc9+TRcyOY=jg3MmC33QjtVNPkLyo1bnE_syVp=2A@mail.gmail.com>
Date: Fri, 08 Nov 2019 18:11:01 -0500
Cc: Paul Hoffman <paul.hoffman@icann.org>, "dns-privacy@ietf.org" <dns-privacy@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <B969DDFB-1680-4D76-80F1-1EC04DC8926A@nohats.ca>
References: <CABcZeBMQEJ=LE8ATQYnJj59srsK47hf4HT3BMMg3X2crVfSUXQ@mail.gmail.com> <CAHw9_i+e8veeAz+KYXjvchmjKJz6OZHX1pEYx_Tvs8n5xnfBnQ@mail.gmail.com> <6D6233DC-4D7C-45BC-9D4E-08E6E882C1A5@nohats.ca> <alpine.DEB.2.20.1911042035571.29247@grey.csi.cam.ac.uk> <CAH1iCioH86q1CX7A+F8ON4uzpGqipUy8m3iczyNqSKirAsYBQg@mail.gmail.com> <alpine.LRH.2.21.1911041652450.5093@bofh.nohats.ca> <CABcZeBOtY3saJe5DWTu=Jqy5guqdoKPKSR+XYddbvxwxKsxmig@mail.gmail.com> <CAHw9_iKaeT0VEjZfoCi9Nddc+VBBj0JHWDHv+=g3xzvb6L+Nvg@mail.gmail.com> <alpine.LRH.2.21.1911050941090.30046@bofh.nohats.ca> <CAHw9_i+MxMCd7dDO7N0-hc1SDjvBeoLoUvbg4JWDzXyjR0u4xQ@mail.gmail.com> <CAHw9_iKhaA9Nb+eH92YfzdepU90_DgLyS-ZDaMAehKOFO0ksEA@mail.gmail.com> <FC51D8EC-5ADC-4415-82EB-C6C6E4E8D84A@fl1ger.de> <F0DD4028-2404-4232-90F8-E9937877C261@nohats.ca> <b7108cff-0e50-d168-aa49-2626eb83ee22@cs.tcd.ie> <d465d9e5-5a9f-8968-8f73-1493ec5f2c36@icann.org> <alpine.LRH.2.21.1911081633490.9092@bofh.nohats.ca> <CA+nkc8D1uvc9+TRcyOY=jg3MmC33QjtVNPkLyo1bnE _syVp=2A@mail.gmail.com>
To: Bob Harold <rharolde@umich.edu>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/b_khIvBBrEUjZEtjKdHivdoM1W0>
Subject: Re: [dns-privacy] [Ext] Threat Model
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Nov 2019 23:11:52 -0000

> On Nov 8, 2019, at 17:06, Bob Harold <rharolde@umich.edu> wrote:
> 
> 
> I hate to admit it, and this is a little off topic, but my resolvers are not (yet) validating.

Then your resolvers’ configuration is years out of date. All resolvers these days ship with validation enabled.

> Is there a setting that will attempt to validate, and log if it fails, but still answer the users?

At that point, everyone using 8.8.8.8 or 9.9.9.9 or 1.1.1.1 or any other non-opendns resolver would not be able to access that domain. Why would you want to override that?

> I hear that there are occasional sites that fail validation, and would like to know what will break if and when I begin to validate.

Nothing that the vast majority of users would already not be able to see.


> I will also need to monitor the added load on the servers, although I don't expect it to be a problem.

That’s not an issue.

> I realize that not everyone agrees with this level of caution/fear/lack-of-backbone (I am sure there are other descriptions people would prefer).

It’s far too late for that level of concern by you.

Paul