Re: [dane] Behavior in the face of no answer?

Eric Rescorla <ekr@rtfm.com> Fri, 04 May 2012 13:49 UTC

Return-Path: <ekr@rtfm.com>
X-Original-To: dane@ietfa.amsl.com
Delivered-To: dane@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF00A21F86D3 for <dane@ietfa.amsl.com>; Fri, 4 May 2012 06:49:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.863
X-Spam-Level:
X-Spam-Status: No, score=-102.863 tagged_above=-999 required=5 tests=[AWL=0.114, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, 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 OMF98E6VOPiI for <dane@ietfa.amsl.com>; Fri, 4 May 2012 06:49:02 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 01ECC21F8645 for <dane@ietf.org>; Fri, 4 May 2012 06:49:01 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so2437302vbb.31 for <dane@ietf.org>; Fri, 04 May 2012 06:49:01 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding :x-gm-message-state; bh=u6YabKFwUs6c2//7r9dlc6JPq4PztBbZekWiY+B8FPU=; b=TMMVyzCZ+3T/Qe6Fjfn/imJ1mg9IHrY3nessbVS4xFrXd557mhGMBtaF77mBuHpY8x crMX3dd2BYR0F/guhg0/FWIzekLaD3t8LMOyd6mWTtrdPNgva73pwUfIXOcI9zp5LN2N QemDwCHnLTEEnfwZtm6lZqkw/9HBKBHWiUrWeAhRfVD/y8knuWPr79xGRIY22VwcN5yD eUZ9Jo2BZaPQO5FGdCTOZ8jSOLrdQ7QBc0e/SHVar1wZ21pY2MHRRo4Gvpl24V4erna3 xzUteSEfQYPQxVifBjuePCwfpdSjDS95UW7vngjGYJGJMwTeVxh4poemb+Zm48mYVSx2 jB4A==
Received: by 10.220.141.79 with SMTP id l15mr3916754vcu.48.1336139341409; Fri, 04 May 2012 06:49:01 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.19.233 with HTTP; Fri, 4 May 2012 06:48:20 -0700 (PDT)
X-Originating-IP: [74.95.2.169]
In-Reply-To: <20120504112922.GB4929@mail.yitter.info>
References: <CABcZeBMY26xrfvAx=UsYN2XnuONZ2vPy9tNwHQALudd=yQDvgA@mail.gmail.com> <0526D60A-3F1B-4C55-9796-256BC2556AAB@vpnc.org> <20120503223745.GC1804@mail.yitter.info> <CABcZeBMFV8oiZJfAY1fZ_0bBQWa=q6aBL65AS+W5gBuKmPnwOg@mail.gmail.com> <20120504021044.GB4560@mail.yitter.info> <B25C977F-6B4E-458C-879D-A36EDB94DA75@icsi.berkeley.edu> <20120504023602.GA4683@mail.yitter.info> <CABcZeBO93n_C5detefBcOjAoswe2inGKDj65gQPDQmREyGnhAw@mail.gmail.com> <20120504112922.GB4929@mail.yitter.info>
From: Eric Rescorla <ekr@rtfm.com>
Date: Fri, 4 May 2012 06:48:20 -0700
Message-ID: <CABcZeBPTTa07iUHo9XL5WrHGMYHwaQzs6xYtiF25O4Jek8E3RQ@mail.gmail.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQkspsfsHI5Fi75qO2BJyqgkyndPgzoVERX0pbJcSQto+ZRhbhI5lwsetLznHH9gHajLqOcA
Cc: dane@ietf.org
Subject: Re: [dane] Behavior in the face of no answer?
X-BeenThere: dane@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: DNS-based Authentication of Named Entities <dane.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dane>, <mailto:dane-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dane>
List-Post: <mailto:dane@ietf.org>
List-Help: <mailto:dane-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dane>, <mailto:dane-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 May 2012 13:49:03 -0000

On Fri, May 4, 2012 at 4:29 AM, Andrew Sullivan <ajs@anvilwalrusden.com> wrote:
> On Thu, May 03, 2012 at 08:18:41PM -0700, Eric Rescorla wrote:
>>
>> While I understand that these operational constraints, I'm having
>> trouble understanding what security benefit DANE offers if one behaves
>> as you suggest, since it seems the attacker can simply force you to
>> ignore any records that DANE provides.
>
> As a client, you could be making a decision about what is more likely:
>
>    1.  The attacker is able to undermine some CA.
>
>    2.  The attacker is actually on-path and going to undermine my
>    connection.

I'm confused by this answer: DANE (for the two constraints modes)
only offers security value if *both* of these things are true. If the
first is not true, then a PKIX certificate is sufficient to distinguish
between valid users and attackers and in the second is not true,
then even an attacker with an invalid certificate cannot get
your packts.

> In many cases, one might decide that (1) is more likely than (2), and
> therefore decide that TLSA is a better thing to rely on.  During
> deployment, however, one might be willing to think that (1) is less
> likely than, "I am in a coffee shop, and these people bought crappy
> infrastructure."  In that case, one might want to be able to fall back
> to the way we actually do this today.

Again, this is logical, but as far as I can tell it obviates the security
provided by DANE. I'd like to repeat the question I asked in my
previous message: can you describe a set of attacker capabilities
which would be sufficient for an attacker to mount a successful
attack on TLS pre-DANE but would not post-DANE, provided
that clients react to TLSA non-response by falling back to pre-DANE
behavior?

Thanks,
-Ekr