Re: [perpass] DNS confidentiality

Stephen Farrell <stephen.farrell@cs.tcd.ie> Wed, 25 September 2013 12:36 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: perpass@ietfa.amsl.com
Delivered-To: perpass@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49A5211E8102 for <perpass@ietfa.amsl.com>; Wed, 25 Sep 2013 05:36:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0G+bkyrWJzBw for <perpass@ietfa.amsl.com>; Wed, 25 Sep 2013 05:35:56 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id B35E211E810A for <perpass@ietf.org>; Wed, 25 Sep 2013 05:35:54 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 21678BE51; Wed, 25 Sep 2013 13:35:54 +0100 (IST)
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JBwPcd+IIudD; Wed, 25 Sep 2013 13:35:54 +0100 (IST)
Received: from [134.226.36.180] (stephen-think.dsg.cs.tcd.ie [134.226.36.180]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id F1F84BE2F; Wed, 25 Sep 2013 13:35:53 +0100 (IST)
Message-ID: <5242D8AA.4040108@cs.tcd.ie>
Date: Wed, 25 Sep 2013 13:35:54 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>, Andy Wilson <andrewgwilson@gmail.com>
References: <524150C7.2020602@cs.tcd.ie> <CAL2p+8S_GCDQC3GtxdFZ+T-hXxo8FHUfFumKN425-2kHs=Ts=w@mail.gmail.com> <20130925121521.GA31952@nic.fr>
In-Reply-To: <20130925121521.GA31952@nic.fr>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: perpass <perpass@ietf.org>
Subject: Re: [perpass] DNS confidentiality
X-BeenThere: perpass@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "The perpass list is for discussion of the privacy properties of IETF protocols and concrete ways in which those could be improved. " <perpass.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/perpass>, <mailto:perpass-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/perpass>
List-Post: <mailto:perpass@ietf.org>
List-Help: <mailto:perpass-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/perpass>, <mailto:perpass-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Sep 2013 12:36:01 -0000

Hi Stephane,

On 09/25/2013 01:15 PM, Stephane Bortzmeyer wrote:
> On Tue, Sep 24, 2013 at 11:31:10PM +1200,
>  Andy Wilson <andrewgwilson@gmail.com> wrote 
>  a message of 104 lines which said:
> 
>> Have you seen DNSCurve? http://dnscurve.org/
> 
> Channel-security solutions like the non-standard and poorly documented

Non-standard we can fix and we do our best to help with
poorly documented as well:-)

> DNScurve provide confidentiality against a passive third-party
> observer. Not against the operators of the authoritative name servers
> who see a lot of traffic and can share it with others. (For instance,
> several of the root name servers are managed by the US army or a US
> government agency.)
> 
> Not to mention the resolvers of the ISP or the big open resolvers like
> OpenDNS or Google Public DNS, both based in PRISMland. (They see even
> more since the caching does not "protect" against them.)
> 
> To summary, modify DNS to ensure confidentiality is highly
> non-trivial.

Right, I agree its non-trivial and that some servers somewhere
will see the queries and responses and could be part of a
monitoring network via collusion or coercion or as a result of
being hacked.

I guess I'm wondering though if its worthwhile and if there are
folks who'd be willing and able to do the work. Or at least some
initial work - I don't think this is one where I'd expect its
likely somoene can just write a nice short draft and be finished
very quickly.

S.


> 
> _______________________________________________
> perpass mailing list
> perpass@ietf.org
> https://www.ietf.org/mailman/listinfo/perpass
> 
>