Re: [pkix] [Technical Errata Reported] RFC4211 (4797)
Lijun Liao <lijun.liao@gmail.com> Thu, 08 September 2016 14:16 UTC
Return-Path: <lijun.liao@gmail.com>
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 D7A3612B04D for <pkix@ietfa.amsl.com>; Thu, 8 Sep 2016 07:16:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 5kPg1SWLl4uL for <pkix@ietfa.amsl.com>; Thu, 8 Sep 2016 07:16:26 -0700 (PDT)
Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DDBBD12B1A4 for <pkix@ietf.org>; Thu, 8 Sep 2016 07:16:22 -0700 (PDT)
Received: by mail-wm0-x233.google.com with SMTP id b187so171698182wme.1 for <pkix@ietf.org>; Thu, 08 Sep 2016 07:16:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=huGK4IeP/w6yX7Ind2rlLUhl9464i08+5jf+cT6HQBs=; b=AHY43qRqnNv2xi+khbWnZ4pxFf4z2TUobOB5Sv2W60oZdJbQ/+bAJVpdSmegOSgu/w ifC9XsrN7Vq+H4NchmCLeGBCSWI4WPM3V7bRx1UoNkZnz8OVbtFkDXfgNl+zzPmoDfQ5 U0Zm/g4gxksf03XTfjX3eFcRp57QzIwxOyBajym+4xVi+a5i+BZqTocY6vGQKrw+rAQc CvmzAqFYY2ShmjF75XSGbKONkaYwo/Vpx1ykZNb660gMwPlRDoYCIPVAWVJlT08boZGK ODC53lKAE7GhRLNUcssbbqnHj0wXDIFlKXX86yspF1lCjhlugeJ+kJaRqmh56CuaMB9n c3lw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=huGK4IeP/w6yX7Ind2rlLUhl9464i08+5jf+cT6HQBs=; b=JHdqUgeb3EID+Lhexwzud7AWHmt+44NtF+phi+7bLmx6nV7GSKlrrXy+eWW9Qmk/R9 Xh2umpqZ4xpnJeKh9AY6t1qTksrPOVv5+J3EsFnqANsreqDiaA3WU6y97FU7O4OeM5yf RXInhNzWWA03n3OmTcbRoMSEZGJ3D30OLXXV6dyhNJ4EcB8/vMxCCCBxM/EFv6cgfjcP q7rbdmdMUxqcnf5kmjhBT8MhmQ123zFyssnz5a66A3Q6cpP+CIpYk/sUjw4WSFvMao8i q0RZSwrWdk5UgUNSJ6Qm2JiooWqnBHYlvjlaLgN88rPwZUz4WsuYq/euisaEQN+Tl4ef 0gew==
X-Gm-Message-State: AE9vXwN94QdWTzBs8l4zrfdvTe4DyTwFVN9AOQFCI8z1wzYo7RdjeRXKBfl3k4rpvKIlg0UPfe77feHqBK0kyg==
X-Received: by 10.194.146.174 with SMTP id td14mr10645316wjb.152.1473344181401; Thu, 08 Sep 2016 07:16:21 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.80.171.195 with HTTP; Thu, 8 Sep 2016 07:16:20 -0700 (PDT)
In-Reply-To: <20160908140059.7EF20B80BD6@rfc-editor.org>
References: <20160908140059.7EF20B80BD6@rfc-editor.org>
From: Lijun Liao <lijun.liao@gmail.com>
Date: Thu, 08 Sep 2016 16:16:20 +0200
Message-ID: <CANNx7D_NPPYOekz4yOv7N-dE9Fa5VBkWKay2ADNQdS91YwP=GA@mail.gmail.com>
To: RFC Errata System <rfc-editor@rfc-editor.org>
Content-Type: multipart/alternative; boundary="089e0122787c907f4b053bffacd7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pkix/dG8IqfaeD5z1Ijk7BFL4k36UTkg>
X-Mailman-Approved-At: Thu, 08 Sep 2016 07:24:54 -0700
Cc: stefan@aaa-sec.com, jimsch@exmsft.com, pkix@ietf.org
Subject: Re: [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:16:28 -0000
Just correction: The Notes should be as follows: ------------------------------------------ The original text conflicts with the following text block (just several lines later). " The fields of POPOSigningKey have the following meaning: ... signature contains the POP value produce. If poposkInput is present, the signature is computed over the DER-encoded value of poposkInput. If poposkInput is absent, the signature is computed over the DER-encoded value of certReq." On Thu, Sep 8, 2016 at 4:00 PM, RFC Errata System <rfc-editor@rfc-editor.org > wrote: > 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 > > -- Lijun Liao
- [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