IETF Logo Mail Archive

Re: [pkix] Self-issued certificates

mrex@sap.com (Martin Rex) Thu, 16 July 2015 15:44 UTC

Return-Path: <mrex@sap.com>
X-Original-To: pkix@ietfa.amsl.com
Delivered-To: pkix@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBCE21A8825 for <pkix@ietfa.amsl.com>; Thu, 16 Jul 2015 08:44:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.951
X-Spam-Level:
X-Spam-Status: No, score=-5.951 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, J_CHICKENPOX_41=0.6, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-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 qZYu-6Bpeaum for <pkix@ietfa.amsl.com>; Thu, 16 Jul 2015 08:44:51 -0700 (PDT)
Received: from smtpde01.smtp.sap-ag.de (smtpde01.smtp.sap-ag.de [155.56.68.170]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A9D781A8780 for <pkix@ietf.org>; Thu, 16 Jul 2015 08:44:51 -0700 (PDT)
Received: from mail05.wdf.sap.corp (mail05.sap.corp [194.39.131.55]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtpde01.smtp.sap-ag.de (Postfix) with ESMTPS id CD4362AA0D; Thu, 16 Jul 2015 17:44:49 +0200 (CEST)
X-purgate-ID: 152705::1437061489-0000413A-2D7C3E1E/0/0
X-purgate-size: 702
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate-type: clean
X-SAP-SPAM-Status: clean
Received: from ld9781.wdf.sap.corp (ld9781.wdf.sap.corp [10.21.82.193]) by mail05.wdf.sap.corp (Postfix) with ESMTP id BC369409E9; Thu, 16 Jul 2015 17:44:49 +0200 (CEST)
Received: by ld9781.wdf.sap.corp (Postfix, from userid 10159) id B20051A1EC; Thu, 16 Jul 2015 17:44:49 +0200 (CEST)
In-Reply-To: <198BA0FB-79C1-4AAB-BA15-554C653CE571@mitre.org>
To: "Miller, Timothy J." <tmiller@mitre.org>
Date: Thu, 16 Jul 2015 17:44:49 +0200
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20150716154449.B20051A1EC@ld9781.wdf.sap.corp>
From: mrex@sap.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/pkix/wzg89kGyv1qWd5ffTFoVpryUXw0>
Cc: PKIX <pkix@ietf.org>
Subject: Re: [pkix] Self-issued certificates
X-BeenThere: pkix@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: mrex@sap.com
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 16 Jul 2015 15:44:53 -0000

Miller, Timothy J. wrote:
> 
>> Only a signature of the new key with the old key could provide
>> such a proof.  
> 
> Umm, that?s what an RFC 4210 CA Key Update Announcement is.
> Actually, it contains the old key signed with the new key,
> the new key signed with the old key, and the new key self-signed.

:-)

I'm sorry.

I had not recognized your term "RFC 4210 rollover announcement" as
something that refers to a technical protocol that includes
the relevant PDUs.

rfc4210 is sufficient complex and awkward that is not used anywhere
around TLS (at least the stuff that I come in contact with) nor common
web-service or pkcs#7/CMS based data exchange scenarios.


-Martin

v2.23.0 | Report a Bug | By Email