Re: [websec] Certificate Pinning via HSTS (.txt version)
Marsh Ray <marsh@extendedsubset.com> Tue, 13 September 2011 20:56 UTC
Return-Path: <marsh@extendedsubset.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 668D611E80ED for <websec@ietfa.amsl.com>; Tue, 13 Sep 2011 13:56:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.574
X-Spam-Level:
X-Spam-Status: No, score=-2.574 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599]
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 dRB6EbPvfUFp for <websec@ietfa.amsl.com>; Tue, 13 Sep 2011 13:56:09 -0700 (PDT)
Received: from mho-01-ewr.mailhop.org (mho-03-ewr.mailhop.org [204.13.248.66]) by ietfa.amsl.com (Postfix) with ESMTP id D704111E80E5 for <websec@ietf.org>; Tue, 13 Sep 2011 13:56:09 -0700 (PDT)
Received: from xs01.extendedsubset.com ([69.164.193.58]) by mho-01-ewr.mailhop.org with esmtpa (Exim 4.72) (envelope-from <marsh@extendedsubset.com>) id 1R3a3c-000E2y-Pd; Tue, 13 Sep 2011 20:58:16 +0000
Received: from [192.168.1.15] (localhost [127.0.0.1]) by xs01.extendedsubset.com (Postfix) with ESMTP id 91ED86067; Tue, 13 Sep 2011 20:58:14 +0000 (UTC)
X-Mail-Handler: MailHop Outbound by DynDNS
X-Originating-IP: 69.164.193.58
X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/mailhop/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX19kD/C3gGqEZp3cLGwwRmq5WKc/hVmiyoQ=
Message-ID: <4E6FC3E8.8040201@extendedsubset.com>
Date: Tue, 13 Sep 2011 15:58:16 -0500
From: Marsh Ray <marsh@extendedsubset.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.21) Gecko/20110831 Thunderbird/3.1.13
MIME-Version: 1.0
To: Gervase Markham <gerv@mozilla.org>
References: <4E6E9B77.1020802@KingsMountain.com> <4E6F9DC6.2080006@stpeter.im> <FA8A58ED-DD2B-446B-9F01-9D1D25140569@checkpoint.com> <4E6FB7CB.3020309@extendedsubset.com> <4E6FBF5D.9040509@mozilla.org>
In-Reply-To: <4E6FBF5D.9040509@mozilla.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: IETF WebSec WG <websec@ietf.org>
Subject: Re: [websec] Certificate Pinning via HSTS (.txt version)
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 20:56:10 -0000
On 09/13/2011 03:38 PM, Gervase Markham wrote: > On 13/09/11 13:06, Marsh Ray wrote: >> Or not, like the Dutch government, have the pull to convince Mozilla to >> hesitate for a few days to revoke your pwned CA. > > That is rather unfair. You make it sound like they asked, and we > complied. In truth, we relied on an assessment of the situation from > GovCERT, the Dutch CERT - who have a decent reputation. When their > assessment changed, we changed our position; whether they should have > made their initial assessment the way they did is a good question, and > one which concerned parties should ask them. > > It is certainly not an obvious truth, even more so in the heat of the > moment, that a compromise of one part of a certificate hierarchy at a CA > necessarily means that an entirely different one is also compromised. It > may, it may not - that depends on the arrangement and interlinking or > otherwise of the issuance systems. > > Anyway, regardless, the situation is more complex than your allegation > of back-room influence. Yes, I believe that and apologize if I characterized it unfairly. That was just the impression I was left with reading the various explanations and interpretations of what was going on over those few days. I'm sure they weren't very accurate. I can only imagine how hectic that process was for the parties involved and how complex a decision it must have been. Please understand that folks like me are looking it at all through a somewhat obscured window. Sorry again. - Marsh
- Re: [websec] Certificate Pinning via HSTS (.txt v… =JeffH
- Re: [websec] Certificate Pinning via HSTS (.txt v… Chris Palmer
- Re: [websec] Certificate Pinning via HSTS (.txt v… Peter Saint-Andre
- Re: [websec] Certificate Pinning via HSTS (.txt v… =JeffH
- Re: [websec] Certificate Pinning via HSTS (.txt v… Yoav Nir
- Re: [websec] Certificate Pinning via HSTS (.txt v… Daniel Kahn Gillmor
- Re: [websec] Certificate Pinning via HSTS (.txt v… Marsh Ray
- Re: [websec] Certificate Pinning via HSTS (.txt v… Chris Palmer
- Re: [websec] Certificate Pinning via HSTS (.txt v… Chris Palmer
- Re: [websec] Certificate Pinning via HSTS (.txt v… Gervase Markham
- Re: [websec] Certificate Pinning via HSTS (.txt v… Steingruebl, Andy
- Re: [websec] Certificate Pinning via HSTS (.txt v… Marsh Ray
- Re: [websec] Certificate Pinning via HSTS (.txt v… Chris Palmer
- Re: [websec] Certificate Pinning via HSTS (.txt v… Phillip Hallam-Baker
- Re: [websec] Certificate Pinning via HSTS (.txt v… davidillsley
- Re: [websec] Certificate Pinning via HSTS (.txt v… Marsh Ray
- Re: [websec] Certificate Pinning via HSTS (.txt v… Phillip Hallam-Baker
- Re: [websec] Certificate Pinning via HSTS (.txt v… davidillsley
- Re: [websec] Certificate Pinning via HSTS (.txt v… SM
- Re: [websec] Certificate Pinning via HSTS (.txt v… Chris Palmer
- Re: [websec] Certificate Pinning via HSTS (.txt v… Yoav Nir
- Re: [websec] Certificate Pinning via HSTS (.txt v… Phillip Hallam-Baker