IETF Logo Mail Archive

Re: [websec] Certificate Pinning via HSTS

Chris Palmer <palmer@google.com> Tue, 13 September 2011 22:00 UTC

Return-Path: <palmer@google.com>
X-Original-To: websec@ietfa.amsl.com
Delivered-To: websec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2802A21F84FD for <websec@ietfa.amsl.com>; Tue, 13 Sep 2011 15:00:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.877
X-Spam-Level:
X-Spam-Status: No, score=-105.877 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_MED=-4, 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 rQZ-iTchit16 for <websec@ietfa.amsl.com>; Tue, 13 Sep 2011 15:00:11 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.67]) by ietfa.amsl.com (Postfix) with ESMTP id 460A121F84FA for <websec@ietf.org>; Tue, 13 Sep 2011 15:00:11 -0700 (PDT)
Received: from hpaq2.eem.corp.google.com (hpaq2.eem.corp.google.com [172.25.149.2]) by smtp-out.google.com with ESMTP id p8DM2HsT016597 for <websec@ietf.org>; Tue, 13 Sep 2011 15:02:17 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1315951337; bh=M/1S0/wXdz+9EQ9A9fQWEQitlWs=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Content-Type:Content-Transfer-Encoding; b=ftC8FjIIj6qTLlCgwI9nYqrElgCatYI1mxaXBykm0hvNlXqmoWrzgrHE1DMb9wtoG OUcp06n6hxhK/mkG6OdTA==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=dkim-signature:mime-version:in-reply-to:references:date: message-id:subject:from:to:content-type: content-transfer-encoding:x-system-of-record; b=CwtFOi8utQWzMIWePZqFBqEU6jzIfaxurtwYAjCOiI3ilTubuZuy4XFKlexjbpCOg SewCBgeFv1uq9Ik2AxQ5Q==
Received: from wwi36 (wwi36.prod.google.com [10.241.243.36]) by hpaq2.eem.corp.google.com with ESMTP id p8DM1rEv016136 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <websec@ietf.org>; Tue, 13 Sep 2011 15:02:16 -0700
Received: by wwi36 with SMTP id 36so1066096wwi.14 for <websec@ietf.org>; Tue, 13 Sep 2011 15:02:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=hSpwn3Gkfj8fUKBBBb48vqumQci8YbJMA/+9lotb+OI=; b=MjEKkOuY1Dy5MmRnzsEYIUkvqZfSZQI3Z9RM9RxZAho1AmBtKo9Lrp/QojX8PRFN+r DGpOm1IOYTMdGDQaKi3g==
Received: by 10.216.209.223 with SMTP id s73mr1054194weo.34.1315951336739; Tue, 13 Sep 2011 15:02:16 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.216.209.223 with SMTP id s73mr1054187weo.34.1315951336594; Tue, 13 Sep 2011 15:02:16 -0700 (PDT)
Received: by 10.216.61.16 with HTTP; Tue, 13 Sep 2011 15:02:16 -0700 (PDT)
In-Reply-To: <4E6F62EE.2070409@cisco.com>
References: <CAOuvq22p2qNnXRsK=PS=mxknnq4MrCWt0Np-N8su-iHXaWHqpg@mail.gmail.com> <CA+cU71=7tM9tS6bAddiLDtOBTX_DH3cebEd5dM=1DSMKXUMdjw@mail.gmail.com> <4E6F62EE.2070409@cisco.com>
Date: Tue, 13 Sep 2011 15:02:16 -0700
Message-ID: <CAOuvq22f3e-wFjnKG2Xdb7ZUOJmHSKFb3dtcrnbtJMBDj9dOsA@mail.gmail.com>
From: Chris Palmer <palmer@google.com>
To: Philip Gladstone <pgladsto@cisco.com>, websec@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-System-Of-Record: true
Subject: Re: [websec] Certificate Pinning via HSTS
X-BeenThere: websec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Web Application Security Minus Authentication and Transport <websec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 13 Sep 2011 22:00:12 -0000

On Tue, Sep 13, 2011 at 7:04 AM, Philip Gladstone <pgladsto@cisco.com> wrote:

[ snip questions about revocation — I'm trying to think about and
clarify that stuff next ]

> Does this proposal also support self-signed certificates? I.e. if you
> connect to a site, accept the self-signed certificate, can that site then
> pin itself using that self-signed cert? I.e. can the validation of the cert
> chain stop as soon as there is a pin match?

This specification is agnostic on that issue. If your client lets you
accept self-signed certificates, then there's no reason it can't also
note it as a Known Pinned HSTS Host pinned to your self--signed public
key.

v2.23.0 | Report a Bug | By Email