Re: [dns-privacy] [internet-drafts@ietf.org: I-D Action: draft-bortzmeyer-dprive-step-2-00.txt]
Hugo Maxwell Connery <hmco@env.dtu.dk> Tue, 19 July 2016 09:29 UTC
Return-Path: <hmco@env.dtu.dk>
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 A918412DFB1 for <dns-privacy@ietfa.amsl.com>; Tue, 19 Jul 2016 02:29:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.187
X-Spam-Level:
X-Spam-Status: No, score=-3.187 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.287] 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 NJQ1zBF_RUvo for <dns-privacy@ietfa.amsl.com>; Tue, 19 Jul 2016 02:29:12 -0700 (PDT)
Received: from spamfilter4.dtu.dk (spamfilter4.dtu.dk [192.38.80.33]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A99412DFBC for <dns-privacy@ietf.org>; Tue, 19 Jul 2016 02:17:42 -0700 (PDT)
Received: from ait-pexedg02.win.dtu.dk (ait-pexedg02.win.dtu.dk [192.38.82.192]) by spamfilter4.dtu.dk with ESMTP id u6J9Hc5j031792-u6J9Hc5l031792 (version=TLSv1.0 cipher=DHE-RSA-AES256-SHA bits=256 verify=CAFAIL); Tue, 19 Jul 2016 11:17:38 +0200
Received: from AIT-PEX01MBX02.win.dtu.dk (192.38.82.182) by ait-pexedg02.win.dtu.dk (192.38.82.192) with Microsoft SMTP Server (TLS) id 14.3.266.1; Tue, 19 Jul 2016 11:17:36 +0200
Received: from ait-pex01mbx01.win.dtu.dk ([169.254.1.55]) by ait-pex01mbx02.win.dtu.dk ([169.254.2.96]) with mapi id 14.03.0266.001; Tue, 19 Jul 2016 11:17:38 +0200
From: Hugo Maxwell Connery <hmco@env.dtu.dk>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>, "dns-privacy@ietf.org" <dns-privacy@ietf.org>
Thread-Topic: [dns-privacy] [internet-drafts@ietf.org: I-D Action: draft-bortzmeyer-dprive-step-2-00.txt]
Thread-Index: AQHR4TL0ODZ0G+7MCEi20iIVmfzrV6Afdcsa
Date: Tue, 19 Jul 2016 09:17:37 +0000
Message-ID: <6CB05D82CE245B4083BBF3B97E2ED470214A0CC7@ait-pex01mbx01.win.dtu.dk>
References: <20160718202546.GA6329@sources.org>
In-Reply-To: <20160718202546.GA6329@sources.org>
Accept-Language: en-AU, da-DK, en-US
Content-Language: en-AU
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.225.73.250]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/Fuzu3jYsduq01_chSN_9XKj38QQ>
Subject: Re: [dns-privacy] [internet-drafts@ietf.org: I-D Action: draft-bortzmeyer-dprive-step-2-00.txt]
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.17
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, 19 Jul 2016 09:29:15 -0000
Hi, Summary: +1 Details: Way back in the early days of DPRIVE I commented that without dealing with the recursive to auth link you end up with a privacy increase that is not quite as good as Tor (but is a big improvement). Remember the goal: to increase the cost of mass surveillance. With what we have, people are joining an anonymity set of those using the recursive resolver. The watchers know what domains the community is interested in by watching the "internet" side of the resolver. To de-anonymise the set the watcher needs to watch the network on "both sides" of the recursive resolver and do timing analysis. With phase 2 in place, even with the above watching and timing analysis all they will know is which auth server a client was interested in, but not what the query was. Thus, to really know what is going on the watchers must compromise the recursive resolver. And that is a cost increase beyond timing correlation. Thanks Stephane for creating "step-2" to describe some of the challenges, particularly authenticating the authoritative resolver ("authing the auth?"). Regards, Hugo
- Re: [dns-privacy] [internet-drafts@ietf.org: I-D … Shane Kerr
- Re: [dns-privacy] [internet-drafts@ietf.org: I-D … Stephane Bortzmeyer
- Re: [dns-privacy] [internet-drafts@ietf.org: I-D … Robert Edmonds
- Re: [dns-privacy] [internet-drafts@ietf.org: I-D … Stephane Bortzmeyer
- Re: [dns-privacy] [internet-drafts@ietf.org: I-D … Bob Harold
- Re: [dns-privacy] [internet-drafts@ietf.org: I-D … Stephane Bortzmeyer
- Re: [dns-privacy] [internet-drafts@ietf.org: I-D … Bob Harold
- Re: [dns-privacy] [internet-drafts@ietf.org: I-D … Warren Kumari
- Re: [dns-privacy] [internet-drafts@ietf.org: I-D … Hugo Maxwell Connery
- Re: [dns-privacy] [internet-drafts@ietf.org: I-D … Shane Kerr
- Re: [dns-privacy] [internet-drafts@ietf.org: I-D … Terry Manderson
- [dns-privacy] [internet-drafts@ietf.org: I-D Acti… Stephane Bortzmeyer
- Re: [dns-privacy] [internet-drafts@ietf.org: I-D … Terry Manderson
- Re: [dns-privacy] [internet-drafts@ietf.org: I-D … Stephane Bortzmeyer
- Re: [dns-privacy] [internet-drafts@ietf.org: I-D … Stephane Bortzmeyer