[pkix] [Technical Errata Reported] RFC4211 (4797)
RFC Errata System <rfc-editor@rfc-editor.org> Thu, 08 September 2016 14:01 UTC
Return-Path: <wwwrun@rfc-editor.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 78F3D12B02F for <pkix@ietfa.amsl.com>; Thu, 8 Sep 2016 07:01:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.13
X-Spam-Level:
X-Spam-Status: No, score=-104.13 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.508, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
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 I-cJ12C2fGzn for <pkix@ietfa.amsl.com>; Thu, 8 Sep 2016 07:00:59 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9E6D8127A91 for <pkix@ietf.org>; Thu, 8 Sep 2016 07:00:59 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 7EF20B80BD6; Thu, 8 Sep 2016 07:00:59 -0700 (PDT)
To: jimsch@exmsft.com, stephen.farrell@cs.tcd.ie, Kathleen.Moriarty.ietf@gmail.com, kent@bbn.com, stefan@aaa-sec.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20160908140059.7EF20B80BD6@rfc-editor.org>
Date: Thu, 08 Sep 2016 07:00:59 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pkix/C-Qamrs_2ZcAmsO9IKvx-Rv7uXM>
Cc: pkix@ietf.org, lijun.liao@gmail.com, rfc-editor@rfc-editor.org
Subject: [pkix] [Technical Errata Reported] RFC4211 (4797)
X-BeenThere: pkix@ietf.org
X-Mailman-Version: 2.1.17
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: <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, 08 Sep 2016 14:01:03 -0000
The following errata report has been submitted for RFC4211, "Internet X.509 Public Key Infrastructure Certificate Request Message Format (CRMF)". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=4211&eid=4797 -------------------------------------- Type: Technical Reported by: Lijun Liao <lijun.liao@gmail.com> Section: 4.1 Original Text ------------- 3. The certificate subject places its name in the Certificate Template structure along with the public key. In this case the poposkInput field is omitted from the POPOSigningKey structure. The signature field is computed over the DER-encoded certificate template structure. Corrected Text -------------- 3. The certificate subject places its name in the Certificate Template structure along with the public key. In this case the poposkInput field is omitted from the POPOSigningKey structure. The signature field is computed over the DER-encoded value of certReq Notes ----- The original text conflicts with the following text block (just several lines later). " The fields of POPOSigningKeyInput have the following meaning: sender contains an authenticated identity that has been previously established for the subject. publicKeyMAC contains a computed value that uses a shared secret between the CA/RA and the certificate requestor. publicKey contains a copy of the public key from the certificate template. This MUST be exactly the same value as is contained in the certificate template." Instructions: ------------- This erratum is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party (IESG) can log in to change the status and edit the report, if necessary. -------------------------------------- RFC4211 (draft-ietf-pkix-rfc2511bis-08) -------------------------------------- Title : Internet X.509 Public Key Infrastructure Certificate Request Message Format (CRMF) Publication Date : September 2005 Author(s) : J. Schaad Category : PROPOSED STANDARD Source : Public-Key Infrastructure (X.509) Area : Security Stream : IETF Verifying Party : IESG
- [pkix] [Technical Errata Reported] RFC4211 (4797) RFC Errata System
- Re: [pkix] [Technical Errata Reported] RFC4211 (4… Lijun Liao
- Re: [pkix] [Technical Errata Reported] RFC4211 (4… Megan Ferguson
- Re: [pkix] [Technical Errata Reported] RFC4211 (4… Jim Schaad
- [pkix] [Errata Verified] RFC4211 (4797) RFC Errata System