Re: [dns-privacy] Alternative signalling propsals

Mark Andrews <marka@isc.org> Sat, 15 December 2018 02:26 UTC

Return-Path: <marka@isc.org>
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 0B2A3128CE4 for <dns-privacy@ietfa.amsl.com>; Fri, 14 Dec 2018 18:26:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level:
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-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 K4bHjV0nRz2Z for <dns-privacy@ietfa.amsl.com>; Fri, 14 Dec 2018 18:26:26 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (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 A0DCC1200D7 for <dns-privacy@ietf.org>; Fri, 14 Dec 2018 18:26:26 -0800 (PST)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 7FC533AB03F; Sat, 15 Dec 2018 02:26:24 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 3E689160055; Sat, 15 Dec 2018 02:26:24 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 1C849160064; Sat, 15 Dec 2018 02:26:24 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id sUo4EPpXYPwV; Sat, 15 Dec 2018 02:26:24 +0000 (UTC)
Received: from [172.30.42.67] (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id D76D7160055; Sat, 15 Dec 2018 02:26:22 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Mark Andrews <marka@isc.org>
In-Reply-To: <87sgyz1v82.fsf@fifthhorseman.net>
Date: Sat, 15 Dec 2018 13:26:20 +1100
Cc: Stephen Farrell <stephen.farrell@cs.tcd.ie>, "Reed, Jon" <jreed@akamai.com>, "dns-privacy@ietf.org" <dns-privacy@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <176DA961-232B-4557-982B-75B05D152D37@isc.org>
References: <74C380A3-C69F-4340-A723-B134F052953E@akamai.com> <f8e17058-f769-ff2d-95f6-9b8850f5fbaa@cs.tcd.ie> <87sgyz1v82.fsf@fifthhorseman.net>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/BYutqNwHiYB20vtLEifFZDUw5f4>
Subject: Re: [dns-privacy] Alternative signalling propsals
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: Sat, 15 Dec 2018 02:26:29 -0000


> On 15 Dec 2018, at 11:37 am, Daniel Kahn Gillmor <dkg@fifthhorseman.net> wrote:
> 
> On Fri 2018-12-14 22:58:09 +0000, Stephen Farrell wrote:
> 
>> I'm probably exposing my lack of DNS-clue, but I wonder if it
>> is/isn't possible to embed a "like/want/offer privacy" signal
>> in the DNS protocol, rather than in the data carried by the
>> protocol? (Regardless of whether the latter might be done via
>> funny names or new/additional RRs.).
> 
> i think you're suggesting some sort of "starttls"-like mechanism --
> start a DNS connection to an authoritative server, and then the server
> lets you know "hey you might also want to try me in the future via
> private channels"
> 
> is that what you're proposing?
> 
> if so, it has the unsatisfying aspect common to all starttls-like
> proposals: it can be trivially stripped.

Not if the zone is signed.

> it is also unsatisfying in the DNS world because there typically isn't
> a handshake -- the first packet contains the sensitive data that you
> might want to keep private.

I you can’t hide that you are talking to a nameserver.  Asking for the
nameserver’s TLSA record isn’t exposing much that is already exposed.

> It could certainly help over the longer term against a passive monitor
> -- the initial privacy leak could be amortized over many future
> communications between the resolver and the authoritative -- but it
> still leaves the first connection to that server unprotected even
> against passive attack, which is something that signalling in the name
> could potentially avoid.
> 
>      --dkg
> _______________________________________________
> dns-privacy mailing list
> dns-privacy@ietf.org
> https://www.ietf.org/mailman/listinfo/dns-privacy

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742              INTERNET: marka@isc.org