Re: [websec] Decouple HSTS's two orthogonal effects?

Adam Barth <ietf@adambarth.com> Tue, 29 March 2011 22:38 UTC

Return-Path: <ietf@adambarth.com>
X-Original-To: websec@core3.amsl.com
Delivered-To: websec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 789CA3A6AD6 for <websec@core3.amsl.com>; Tue, 29 Mar 2011 15:38:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.792
X-Spam-Level:
X-Spam-Status: No, score=-2.792 tagged_above=-999 required=5 tests=[AWL=0.185, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gwoymQHDTsZH for <websec@core3.amsl.com>; Tue, 29 Mar 2011 15:38:41 -0700 (PDT)
Received: from mail-yi0-f44.google.com (mail-yi0-f44.google.com [209.85.218.44]) by core3.amsl.com (Postfix) with ESMTP id 3FC3C3A6AD7 for <websec@ietf.org>; Tue, 29 Mar 2011 15:38:40 -0700 (PDT)
Received: by yic13 with SMTP id 13so316100yic.31 for <websec@ietf.org>; Tue, 29 Mar 2011 15:40:18 -0700 (PDT)
Received: by 10.151.116.2 with SMTP id t2mr733283ybm.268.1301438418346; Tue, 29 Mar 2011 15:40:18 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by mx.google.com with ESMTPS id t16sm5583201ybe.19.2011.03.29.15.40.17 (version=SSLv3 cipher=OTHER); Tue, 29 Mar 2011 15:40:17 -0700 (PDT)
Received: by iwn39 with SMTP id 39so690290iwn.31 for <websec@ietf.org>; Tue, 29 Mar 2011 15:40:16 -0700 (PDT)
Received: by 10.43.55.84 with SMTP id vx20mr108749icb.49.1301438416166; Tue, 29 Mar 2011 15:40:16 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.43.133.200 with HTTP; Tue, 29 Mar 2011 15:39:46 -0700 (PDT)
In-Reply-To: <4D925C55.1070900@fifthhorseman.net>
References: <4D92317B.6020804@fifthhorseman.net> <BANLkTinGEt42DM1NqbrjOfdqTqLUjnQ5KQ@mail.gmail.com> <4D925C55.1070900@fifthhorseman.net>
From: Adam Barth <ietf@adambarth.com>
Date: Tue, 29 Mar 2011 15:39:46 -0700
Message-ID: <AANLkTim9O3kPQyirWctaFK=JyNrEHYwsJ1QEWjty=ye0@mail.gmail.com>
To: websec@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [websec] Decouple HSTS's two orthogonal effects?
X-BeenThere: websec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Web Application Security Minus Authentication and Transport <websec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/websec>, <mailto:websec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/websec>
List-Post: <mailto:websec@ietf.org>
List-Help: <mailto:websec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/websec>, <mailto:websec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Mar 2011 22:38:42 -0000

On Tue, Mar 29, 2011 at 3:25 PM, Daniel Kahn Gillmor
<dkg@fifthhorseman.net> wrote:
> On 03/29/2011 04:58 PM, Adam Barth wrote:
>> There's no coupling between HSTS and the particular algorithm a UA
>> uses to verify certificates.  The UA is free to use whatever
>> verification mechanism it desires.  You can remove whatever CAs you
>> consider sloppy from the list of trusted certificate authorities and
>> add in whatever other verification mechanism you like.
>>
>> For example, if/when certificate verification through DNSSEC becomes
>> widespread, we won't need to change anything about the HSTS spec.  Of
>> course, we'll need to change our implementations, but that's true
>> regardless of what the HSTS spec says.
>
> I hear what you're saying; however, i'm unaware of any HSTS-compliant
> User Agent that implements anything but the standard weakest-link X.509
> certificate pool of trusted authorities.
>
> Perhaps an explicit mention that says HSTS is not intended to be
> incompatible with alternative certificate verification mechanisms would
> provide useful guidance to browser vendors?

I don't think we need that guidance, but thanks.

Adam