IETF Logo Mail Archive

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

"John Levine" <johnl@taugh.com> Tue, 05 November 2019 02:40 UTC

Return-Path: <johnl@iecc.com>
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 06670120073 for <dns-privacy@ietfa.amsl.com>; Mon, 4 Nov 2019 18:40:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level:
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=CM953qMC; dkim=pass (1536-bit key) header.d=taugh.com header.b=SuTH/1pi
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 Ut60EcINUxbn for <dns-privacy@ietfa.amsl.com>; Mon, 4 Nov 2019 18:40:48 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 994E112006F for <dns-privacy@ietf.org>; Mon, 4 Nov 2019 18:40:48 -0800 (PST)
Received: (qmail 49682 invoked from network); 5 Nov 2019 02:40:45 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=c210.5dc0e12d.k1911; i=printer-iecc.com@submit.iecc.com; bh=XOgGByokiSvrIvyzoytmPwvuylc38DelyjKOjlpqkr0=; b=CM953qMCgJWt3ShWChjH3YQb6ewHV6K3AahLMnFCENXX3QER+aVvNoOKRW0u4zwNSZsUQZ5uEN19Rq1bH1wiOyUXnV6F7l217XzU32Y+OFyeVFqSyTqH6kz+Jj20sBJjkdXN/equz0OPdsNDgo8Xku8YpPJHaPSOtKlGaBSy00Wuerx24ECsl8dbCnP/vx5p7a9vbVhYX+SiBcYUAJJZIwe6dSnKNBrQVgDvG7H8WzY/QxZ2XclnA23lFYdNmMLa
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=c210.5dc0e12d.k1911; olt=printer-iecc.com@submit.iecc.com; bh=XOgGByokiSvrIvyzoytmPwvuylc38DelyjKOjlpqkr0=; b=SuTH/1pil47kpS3NwvzLJLRZxPBG4qt0+vNRV/o93jTd5ZaM0NKST6tf7KP3aVGKrTQ/Z6ObPpdClqFW2MtJusdbgDy55+EK5JKrmnzgE1NRB1dsrcIUFQXVbPyTTe206Y5YT9eXpNsLYgZaIPzMTMuRUBpQZLAnuJOxU/0+NQnKixgANFG33LBAWQJDJjCpH35K5rUJzXsRg3w8BGxY1wPtfGt/jNB0qgDCEItY5pTf7A/K04KPFMeYQffcGbb8
Received: from ary.local ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPSA (TLS1.2 ECDHE-RSA AES-256-GCM AEAD, printer@iecc.com) via TCP6; 05 Nov 2019 02:40:45 -0000
Received: by ary.local (Postfix, from userid 501) id 90472E5CBF5; Mon, 4 Nov 2019 21:40:42 -0500 (EST)
Date: Mon, 04 Nov 2019 21:40:42 -0500
Message-Id: <20191105024044.90472E5CBF5@ary.local>
From: John Levine <johnl@taugh.com>
To: dns-privacy@ietf.org
In-Reply-To: <CAH1iCiq3VjuFYaXho6+3Miu=5BAfze+Vk8qwGx+W_Hw5AiD8tg@mail.gmail.com>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/L11nV9wklu-3wcqWhUyPJstZbw8>
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: Tue, 05 Nov 2019 02:40:50 -0000

In article <CAH1iCiq3VjuFYaXho6+3Miu=5BAfze+Vk8qwGx+W_Hw5AiD8tg@mail.gmail.com> you write:
>> Again, that would be russian roulette. If I get an NS RRset with 3
>> nameservers, and only one of these has a TLSA record, what should I
>> do ?

Dunno about you, but I'd make a note not to hire that provider to run my DNS.

People can set up any sort of DNS badly, and experience has repeatedly
shown that attempts to idiot-proof systems merely brings out more
ingenious idiots.  The more useful question is how hard it is for a
sensible person to set something up sensibly, and in this case the
answer is not very hard.

R's,
John

v2.23.0 | Report a Bug | By Email