Re: [therightkey] Basically, it's about keeping the CAs honest

Tom Ritter <tom@ritter.vg> Thu, 16 February 2012 19:25 UTC

Return-Path: <tom@ritter.vg>
X-Original-To: therightkey@ietfa.amsl.com
Delivered-To: therightkey@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B70321F87A1 for <therightkey@ietfa.amsl.com>; Thu, 16 Feb 2012 11:25:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.812
X-Spam-Level:
X-Spam-Status: No, score=-2.812 tagged_above=-999 required=5 tests=[AWL=0.165, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
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 rzZfAf0HKHAm for <therightkey@ietfa.amsl.com>; Thu, 16 Feb 2012 11:25:09 -0800 (PST)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 382C521E8081 for <therightkey@ietf.org>; Thu, 16 Feb 2012 11:25:09 -0800 (PST)
Received: by lahl5 with SMTP id l5so3249594lah.31 for <therightkey@ietf.org>; Thu, 16 Feb 2012 11:25:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ritter.vg; s=vg; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=9iOBHd6w59PCEpt6erpzf2RIAIW0YaOIrvpbObRJVI0=; b=1fgrUh5ix6fPm4zzQciWzHca+G3uvqHNexGFvERqyg0RA/KclOOsS6sm3fq9X8VxnQ ZdE72BY/WfHQ08FhQhbnjzdB/+hvFsOJMrbBQ8T/X9Og/EV1KtcEbWl/c4a7g1eGOJkr WXCnAKS6ntgrEbXOJplUrFlmgjlioY73hDk04=
Received: by 10.152.114.74 with SMTP id je10mr2999287lab.40.1329420308089; Thu, 16 Feb 2012 11:25:08 -0800 (PST)
MIME-Version: 1.0
Received: by 10.112.38.4 with HTTP; Thu, 16 Feb 2012 11:24:48 -0800 (PST)
In-Reply-To: <CAMm+LwhrxnznFUTf_TJERjt0rNo+Offs2aUnKLPP2JBR8SYVSA@mail.gmail.com>
References: <gym9r33x3m8ydl4xwbjezwJv4X.penango@mail.gmail.com> <201202160524.q1G5ON2p003570@fs4113.wdf.sap.corp> <CA+cU71n1HeQ3nK_FjM67dO8U7=HmDBG3q0_4cvH9CY6Y0_=9BQ@mail.gmail.com> <CAMm+LwiQdXo6bmYmtyR7aw1S=A889edFdSU5aAJVgN4ZMwNrFw@mail.gmail.com> <4F3D481E.40001@fifthhorseman.net> <CAMm+LwhrxnznFUTf_TJERjt0rNo+Offs2aUnKLPP2JBR8SYVSA@mail.gmail.com>
From: Tom Ritter <tom@ritter.vg>
Date: Thu, 16 Feb 2012 14:24:48 -0500
Message-ID: <CA+cU71kvQ4b2QsowgtjfM6qG0UWAMG5jvPPZTtD9KgqA01DaiA@mail.gmail.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
X-Gm-Message-State: ALoCoQliVJ//2POXT3FGTf+e1H6NIalSmAXaCHptOoTF/NjM740BxM3G+sbvj4FlwLJ9YO6Kde8K
Cc: therightkey@ietf.org, Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Subject: Re: [therightkey] Basically, it's about keeping the CAs honest
X-BeenThere: therightkey@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <therightkey.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/therightkey>, <mailto:therightkey-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/therightkey>
List-Post: <mailto:therightkey@ietf.org>
List-Help: <mailto:therightkey-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/therightkey>, <mailto:therightkey-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2012 19:25:14 -0000

On 16 February 2012 13:41, Phillip Hallam-Baker <hallam@gmail.com> wrote:
> Further, if DANE was deployed or any of the proposals made here was
> deployed they would stop the MITM enabling root authority from
> working. So we are proposing to break the escape hole you are
> proposing they use.
>
> Now breaking that escape hole might be a good thing. But we should
> certainly think about the consequences and it should be a deliberate
> decision to break it and not provide an alternative.

We just had this same discussion on DANE:
http://www.ietf.org/mail-archive/web/dane/current/msg04306.html I
raised the same point about local policy enabling an override, and the
consensus seemed to be: "That's a good point, and mandating what
clients do is not the spec's problem. Let's propose good solutions for
browsers offline/out of the WG."

A nice side effect was that a locally configured trust anchor
overriding a TLSA enables valid corporate MITM, while a
non-transparent, shady-trustwave-style-subca would not be overridden
by local policy, and the TLSA would cause a hard fail.

I'd also like to go on the record that I think a visual indicator to
the user that shows a cert is valid only under local policy is a
fantastic idea and I support it wholeheartedly.  Of course UI is hard,
especially with this opaque a topic to an average user, but I still
think giving it a shot is a good idea.

-tom