Re: [dns-privacy] draft-mayrhofer-edns0-padding

Daniel Kahn Gillmor <dkg@fifthhorseman.net> Thu, 23 July 2015 23:19 UTC

Return-Path: <dkg@fifthhorseman.net>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 650691A0097; Thu, 23 Jul 2015 16:19:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 z9N0BqVIWtDk; Thu, 23 Jul 2015 16:19:57 -0700 (PDT)
Received: from che.mayfirst.org (che.mayfirst.org [209.234.253.108]) by ietfa.amsl.com (Postfix) with ESMTP id 867721A0022; Thu, 23 Jul 2015 16:19:57 -0700 (PDT)
Received: from fifthhorseman.net (7.208.broadband18.iol.cz [109.81.208.7]) by che.mayfirst.org (Postfix) with ESMTPSA id 0A893F984; Thu, 23 Jul 2015 19:19:54 -0400 (EDT)
Received: by fifthhorseman.net (Postfix, from userid 1000) id 71369200E6; Fri, 24 Jul 2015 01:19:53 +0200 (CEST)
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Alexander Mayrhofer <alexander.mayrhofer@nic.at>, "dns-privacy@ietf.org" <dns-privacy@ietf.org>
In-Reply-To: <19F54F2956911544A32543B8A9BDE0754689AF17@NICS-EXCH2.sbg.nic.at>
References: <19F54F2956911544A32543B8A9BDE0754689AF17@NICS-EXCH2.sbg.nic.at>
User-Agent: Notmuch/0.20.2 (http://notmuchmail.org) Emacs/24.5.1 (x86_64-pc-linux-gnu)
Date: Fri, 24 Jul 2015 01:19:53 +0200
Message-ID: <87a8umihra.fsf@alice.fifthhorseman.net>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <http://mailarchive.ietf.org/arch/msg/dns-privacy/e0m-V4QNGbMUEnWkRxeFZMQGkaI>
Cc: "dnsop@ietf.org" <dnsop@ietf.org>
Subject: Re: [dns-privacy] draft-mayrhofer-edns0-padding
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.15
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, 23 Jul 2015 23:19:59 -0000

On Thu 2015-07-23 18:50:14 +0200, Alexander Mayrhofer wrote:

> I had a discussion with Daniel Khan Gillmor today, and we talked about
> his proposal to specify a padding option in TLS so that message-size
> based correlation attacks on encrypted DNS packets could be
> prevented. We continued discussing other options (such as "artificial"
> RRs in the additional section), and I floated the idea that we could
> use EDNS0 to include padding in DNS packets.
>
> So, I've created a quick-and-dirty strawman proposal draft for this
> idea, and i'm happy to discuss this during tomorrow's DPRIVE session
> if we have time:
>
> https://www.ietf.org/id/draft-mayrhofer-edns0-padding-00.txt

wow, thanks for the incredibly quick writeup!

I think this draft could have an informative reference to Haya Shulman's
research on difficulties in DNS encryption, which won the recent ANRP:

  https://irtf.org/anrp
  https://www.ietf.org/mail-archive/web/dns-privacy/current/pdfWqAIUmEl47.pdf

Section 3.2.2 shows that her mechanism for inferring the contents of
queries becomes *even more effective* by including the size of the
packets in her analysis.  (Everyone working on dprive should read this
paper to get a sense of some of the massive difficulties we need to
consider because of the structure of DNS traffic analysis; just
encrypting the traffic is insufficient for several reasons)

I also note that draft-mayrhofer-edns0-padding curently suggests that
the minimum padding size is 1 octet.  Is there any reason to avoid a
padding size of 0? 

        --dkg