Re: [wpkops] I-D Action: draft-ietf-wpkops-trustmodel-02.txt

"Horne, Rob" <rob.horne@trustis.com> Thu, 05 June 2014 14:55 UTC

Return-Path: <rob.horne@trustis.com>
X-Original-To: wpkops@ietfa.amsl.com
Delivered-To: wpkops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FFB21A0241 for <wpkops@ietfa.amsl.com>; Thu, 5 Jun 2014 07:55:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 461lwvKFnMKv for <wpkops@ietfa.amsl.com>; Thu, 5 Jun 2014 07:55:17 -0700 (PDT)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.168]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 96AA21A0179 for <wpkops@ietf.org>; Thu, 5 Jun 2014 07:54:56 -0700 (PDT)
Received: from [85.158.137.67:43521] by server-8.bemta-3.messagelabs.com id 22/AF-21547-8B480935; Thu, 05 Jun 2014 14:54:48 +0000
X-Env-Sender: rob.horne@trustis.com
X-Msg-Ref: server-12.tower-139.messagelabs.com!1401980088!6062464!2
X-Originating-IP: [217.28.140.9]
X-StarScan-Received:
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 28649 invoked from network); 5 Jun 2014 14:54:48 -0000
Received: from smtp.hs20.net (HELO outlook.hs20.net) (217.28.140.9) by server-12.tower-139.messagelabs.com with AES256-SHA encrypted SMTP; 5 Jun 2014 14:54:48 -0000
Received: from THHSTE15D1BE5.hs20.net (192.168.251.26) by THHSTE15D1BE1.hs20.net (192.168.251.21) with Microsoft SMTP Server (TLS) id 15.0.847.32; Thu, 5 Jun 2014 15:54:14 +0100
Received: from THHSTE15D1BE5.hs20.net ([fe80::4064:274f:d635:873e]) by THHSTE15D1BE5.hs20.net ([fe80::4064:274f:d635:873e%15]) with mapi id 15.00.0847.030; Thu, 5 Jun 2014 15:54:14 +0100
From: "Horne, Rob" <rob.horne@trustis.com>
To: "wpkops@ietf.org" <wpkops@ietf.org>
Thread-Topic: [wpkops] I-D Action: draft-ietf-wpkops-trustmodel-02.txt
Thread-Index: AQHPeyZFDyYFwnLMcUy7s1i6Lj94AJtipRxA
Date: Thu, 05 Jun 2014 14:54:13 +0000
Message-ID: <8bb8a25e698a450988b79c058705f1cb@THHSTE15D1BE5.hs20.net>
References: <20140529101033.15865.72439.idtracker@ietfa.amsl.com>
In-Reply-To: <20140529101033.15865.72439.idtracker@ietfa.amsl.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [62.6.167.196]
x-exclaimer-md-config: 266e7a57-cddd-49fd-bdea-19bca6d40303
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/wpkops/e-NN-o2CiV-yvIS3GIQHNhcQ5lg
Subject: Re: [wpkops] I-D Action: draft-ietf-wpkops-trustmodel-02.txt
X-BeenThere: wpkops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <wpkops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wpkops>, <mailto:wpkops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wpkops/>
List-Post: <mailto:wpkops@ietf.org>
List-Help: <mailto:wpkops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wpkops>, <mailto:wpkops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jun 2014 14:55:21 -0000

Hi, I've taken a look at this and have a few comments.

Although the security issues are addressed in section 5, I think it could benefit from a little more detail and clarification in sections 2 and 3.

2.1 Root store provider

Does the audit reporting and updating method described conform to any standard? I've seen auditors follow their own procedures which do not match this description.

3.2.1. One root CA cross-certifies another root CA

Is there a defined and agreed way for older CAs to cross certify newer CAs particularly if they're not owned by the same organisation? For example if the criterion for cross certification is less than that required by the root store for the original CA there could be some interesting issues. 3.2.2 refers to adherence to the root store policy so should that also be in 3.2.1?

3.2.5 to 3.2.7

I'd have expected more emphasis on technically constraining third party and subscriber RAs and CAs. For one thing legal contracts may be subject to non-disclosure which could make it difficult to audit properly but if they're not technically constrained that will be what's required.

5.3. Root CA compromise

The last sentence is incomplete ;-)


A further thought: although potentially contentious should the scope be expanded to include other applications which use https but are not, in the traditional sense, web browsers? I'm thinking in particular of applications that utilise the protocol but don't have or use any form of trusted root store. To my mind this is a much bigger security issue than is covered in the draft as it stands. Of course this gets us into a discussion of how synonymous "web" is with "http/s".

Regards, Rob




-----Original Message-----
From: wpkops [mailto:wpkops-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org
Sent: 29 May 2014 11:11
To: i-d-announce@ietf.org
Cc: wpkops@ietf.org
Subject: [wpkops] I-D Action: draft-ietf-wpkops-trustmodel-02.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Web PKI OPS Working Group of the IETF.

        Title           : Trust models of the Web PKI
        Authors         : Inigo Barreira
                          Bruce Morton
        Filename        : draft-ietf-wpkops-trustmodel-02.txt
        Pages           : 11
        Date            : 2014-05-29

Abstract:
   This is one of a set of documents to define the operation of the Web
   PKI.  It describes the currently deployed Web PKI trust.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-wpkops-trustmodel/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-wpkops-trustmodel-02

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-wpkops-trustmodel-02


Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
wpkops mailing list
wpkops@ietf.org
https://www.ietf.org/mailman/listinfo/wpkops