Re: [dns-privacy] DoT between recursive and authoritative pilot
Erik Kline <ek@loon.co> Thu, 27 December 2018 18:49 UTC
Return-Path: <ek@google.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 9DEBF130E7B for <dns-privacy@ietfa.amsl.com>; Thu, 27 Dec 2018 10:49:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.499
X-Spam-Level:
X-Spam-Status: No, score=-9.499 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.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=loon.co
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 1hIo3JXOXpVF for <dns-privacy@ietfa.amsl.com>; Thu, 27 Dec 2018 10:49:08 -0800 (PST)
Received: from mail-io1-xd34.google.com (mail-io1-xd34.google.com [IPv6:2607:f8b0:4864:20::d34]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F032126F72 for <dns-privacy@ietf.org>; Thu, 27 Dec 2018 10:49:08 -0800 (PST)
Received: by mail-io1-xd34.google.com with SMTP id s22so15179693ioc.8 for <dns-privacy@ietf.org>; Thu, 27 Dec 2018 10:49:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=loon.co; s=google; h=mime-version:references:in-reply-to:reply-to:from:date:message-id :subject:to:cc; bh=DB7mopEWLQNZ/tbE5kQ2MRIR6KhR6FkhDYBXKtjnAiw=; b=kLtLjMrt6ogyWly0Ycp5wABVtlc5G2LpzSTBKzsB6rNnEGrwQ1yJ8YTdMMFk+7UJPg Bl70qxpdDlSM2WQXGhX6ujxBUKAToD5krE9ZHbA3V9X+3emshHJEPlJjqioAnFXp3DRh 4a8UwVkj7ZyK7BgPaN+zzqGanHqVrZ1z4Anvc=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:reply-to :from:date:message-id:subject:to:cc; bh=DB7mopEWLQNZ/tbE5kQ2MRIR6KhR6FkhDYBXKtjnAiw=; b=ajzHIkpa/oKzIsz/tyNb8I9XMkxmg5kWvCuKqdAfUbEf1DM7D64FkjBfTNopj1kt4s 4o7K/JnEZxmaQzDJuhTkbtPYiV4xbTAZ8CEYDED6SDded8s1KEKJ7i90BSQoV3mDunbH SMwDmcry0uJsc8qjQOwfKID3bjybQp1yCwc3RMdZVoz/DYrLR+8ynKCyAuN8/ZdWHHd7 W2Kkj4swds4rpGYhgnv+l62ngWYpqqRKhiSsq4jfydhi7IOJ1zDRdJHntS5GTu29GWMB F9Of9CpeU7PYCIwZ/lxpQojpya2KMVkgYdNh62zIAXn7EaAY899C+PC8cmJ+VhYXlZLc tAXw==
X-Gm-Message-State: AJcUukdcWkCZ1tr5+JsD9qFWSp1Yscg00GlM+VEILsTdt7+puTctONqG VGKmbhIqmIDTUCJ5tyxUAa0tRZIPWO/zMsGGlM+iew==
X-Google-Smtp-Source: ALg8bN4s3JJNczQU0uKRMTZ4vJF67DOnK87Aun3OSEm6tisiy2uXmNxb1exk+XrE8iITQsNomuPZJCJzSBKngRmtZ3E=
X-Received: by 2002:a6b:7a0a:: with SMTP id h10mr13831375iom.114.1545936547241; Thu, 27 Dec 2018 10:49:07 -0800 (PST)
MIME-Version: 1.0
References: <CAArYzrKWs63EdPNjZkc9PaVBbEqrtjuBR74726h-RwjySArH2A@mail.gmail.com> <20181227163247.c4czsly2rjeojvus@nic.fr>
In-Reply-To: <20181227163247.c4czsly2rjeojvus@nic.fr>
Reply-To: ek@loon.co
From: Erik Kline <ek@loon.co>
Date: Thu, 27 Dec 2018 10:48:55 -0800
Message-ID: <CAAedzxqLR4FyS4vGPfQgCQiYXJq2jsCo6C-XR7XFTwTyqyXnzA@mail.gmail.com>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Cc: manu tman <chantr4@gmail.com>, "dns-privacy@ietf.org" <dns-privacy@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000bec1d2057e05669a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/8ZgPyVUh34fo1rI504vOSyNqikM>
Subject: Re: [dns-privacy] DoT between recursive and authoritative pilot
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: Thu, 27 Dec 2018 18:49:14 -0000
On Thu, 27 Dec 2018 at 08:33, Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote: > On Fri, Dec 21, 2018 at 06:59:43PM -0800, > manu tman <chantr4@gmail.com> wrote > a message of 43 lines which said: > > > As some you already know, Cloudflare and Facebook have been running a > pilot > > on using DoT between Cloudflare DNS and Facebook authoritative name > servers. > > You can read more about it at > > https://code.fb.com/security/dns-over-tls/ > > Thanks. Very useful. > > I do not find how the Cloudflare resolver discovers that Facebook > authoritative name servers use DNS-over-TLS, and what are their > keys. Hardwired in the resolver for the experiment? > I think discovery is easy, you just try TCP port 853: for i in $(dig -t NS +short facebook.com | sort); do echo "[ $i ]"; openssl s_client -connect ${i}:853 </dev/null | openssl x509 -text -noout; done shows me that both a&b .ns.facebook.com are listening on 853 and present a cert. The subject for the cert is not especially illuminating, though. I tried sending the resolver name via SNI and got the same cert back. Frankly, SNI + checking the cert is valid for the nameserver hostname seems sufficient to me in the general case.
- [dns-privacy] DoT between recursive and authorita… manu tman
- Re: [dns-privacy] DoT between recursive and autho… Stephane Bortzmeyer
- Re: [dns-privacy] DoT between recursive and autho… Erik Kline
- Re: [dns-privacy] DoT between recursive and autho… manu tman