Re: [pkix] New draft-ietf-pkix-rfc2560bis-06

"Miller, Timothy J." <tmiller@mitre.org> Tue, 30 October 2012 12:41 UTC

Return-Path: <tmiller@mitre.org>
X-Original-To: pkix@ietfa.amsl.com
Delivered-To: pkix@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AAE0221F852C for <pkix@ietfa.amsl.com>; Tue, 30 Oct 2012 05:41:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zl3HIOBv+WVo for <pkix@ietfa.amsl.com>; Tue, 30 Oct 2012 05:41:02 -0700 (PDT)
Received: from smtpksrv1.mitre.org (smtpksrv1.mitre.org [198.49.146.77]) by ietfa.amsl.com (Postfix) with ESMTP id 3256221F8523 for <pkix@ietf.org>; Tue, 30 Oct 2012 05:41:02 -0700 (PDT)
Received: from smtpksrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 66C6D1F0AED; Tue, 30 Oct 2012 08:41:01 -0400 (EDT)
Received: from IMCCAS03.MITRE.ORG (imccas03.mitre.org [129.83.29.80]) by smtpksrv1.mitre.org (Postfix) with ESMTP id 286AC1F0AE5; Tue, 30 Oct 2012 08:41:01 -0400 (EDT)
Received: from IMCMBX01.MITRE.ORG ([169.254.1.132]) by IMCCAS03.MITRE.ORG ([129.83.29.80]) with mapi id 14.02.0318.004; Tue, 30 Oct 2012 08:41:00 -0400
From: "Miller, Timothy J." <tmiller@mitre.org>
To: "mrex@sap.com" <mrex@sap.com>, Piyush Jain <piyush@ditenity.com>
Thread-Topic: [pkix] New draft-ietf-pkix-rfc2560bis-06
Thread-Index: AQHNrgV0CIAuT0FuokKp0o24TaVmN5fBJu8AgACTr4CAAOEpAIABk0sAgAAe6wCAAAW7AIABaDuAgAAG8ICAAAydAIAAVs6AgACatwCAAAbOgIAALqKAgAAFooCAAAz5gIAAJh+AgABTegCAAYn9AIAAJQwAgAAlmICAAALHgIACt4kAgACvZoCAACsxAIAEU58AgACWuLQ=
Date: Tue, 30 Oct 2012 12:40:59 +0000
Message-ID: <195DB2510AAA004391F58E28FCE21200066E1E15@IMCMBX01.MITRE.ORG>
References: <001201cdb402$98ab4d70$ca01e850$@ditenity.com>, <20121029232328.BF5D91A309@ld9781.wdf.sap.corp>
In-Reply-To: <20121029232328.BF5D91A309@ld9781.wdf.sap.corp>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [129.83.31.52]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "pkix@ietf.org" <pkix@ietf.org>, 'Stefan Santesson' <stefan@aaa-sec.com>
Subject: Re: [pkix] New draft-ietf-pkix-rfc2560bis-06
X-BeenThere: pkix@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PKIX Working Group <pkix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pkix>, <mailto:pkix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pkix>
List-Post: <mailto:pkix@ietf.org>
List-Help: <mailto:pkix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pkix>, <mailto:pkix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Oct 2012 12:41:03 -0000

> X.509/PKIX is defective because it breaks badly already on fraudulent
> cert issuance (a weaker form of CA compromise) and can not cope at all
> with CA key compromise.

Do you have an alternative to the technology, because AFAICT, no PKI standards recover well from a breach of trust.  Even the web of trust has issues; if a well-connected introducer is compromised, all descendent keys become suspect--which can potentially encompass all nodes in the graph.  This can be as devestating as a CA compromise, and would likewise require a re-execution of a large number of signing ceremonies.

> The flaw with CRLs and OCSP is that it tries to infer, from a lack
> of a revocation, that a certificate has been properly issued and is valid.
> Evidently, this turned out to be a logical fallacy with respect to
> real world usage scenarios.

Absent a trusted observer, there is no positive statement that can be issued by a CA that positively identifies only "valid" certificates.  Given a trusted observer, why not make him the CA and be done with it?

-- T