Re: [smime] [Editorial Errata Reported] RFC3394 (6942)
Russ Housley <housley@vigilsec.com> Mon, 25 April 2022 14:14 UTC
Return-Path: <housley@vigilsec.com>
X-Original-To: smime@ietfa.amsl.com
Delivered-To: smime@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E1703A1A20; Mon, 25 Apr 2022 07:14:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] 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 Cxbg4rwhBvqA; Mon, 25 Apr 2022 07:14:35 -0700 (PDT)
Received: from mail3.g24.pair.com (mail3.g24.pair.com [66.39.134.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C9B253A1A36; Mon, 25 Apr 2022 07:14:35 -0700 (PDT)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id B60F316B134; Mon, 25 Apr 2022 10:14:34 -0400 (EDT)
Received: from [10.0.1.3] (pfs.iad.rg.net [198.180.150.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail3.g24.pair.com (Postfix) with ESMTPSA id A458F16B133; Mon, 25 Apr 2022 10:14:34 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.21\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <20220425111718.EAC356A9EE@rfcpa.amsl.com>
Date: Mon, 25 Apr 2022 10:14:34 -0400
Cc: samuel.lee@microsoft.com
Content-Transfer-Encoding: quoted-printable
Message-Id: <B79C6239-9D15-4560-BB1E-E4B7E680D0F0@vigilsec.com>
References: <20220425111718.EAC356A9EE@rfcpa.amsl.com>
To: IETF SMIME <smime@ietf.org>, LAMPS <spasm@ietf.org>
X-Mailer: Apple Mail (2.3445.104.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/smime/xpk1dbJ-lrrA7ybnd6RQ8XFApUc>
Subject: Re: [smime] [Editorial Errata Reported] RFC3394 (6942)
X-BeenThere: smime@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SMIME Working Group <smime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/smime>, <mailto:smime-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/smime/>
List-Post: <mailto:smime@ietf.org>
List-Help: <mailto:smime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/smime>, <mailto:smime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Apr 2022 14:14:41 -0000
I just compared this to NIST SP 800-38F, and it looks to me like this mistake has been in the document unnoticed for a very long time. The algorithm description in Section 2.2 seems to be correct, but the notation description in Section 2.1 has an error. Can someone else take a look? Obviously, by coauthor cannot help any longer... Russ > On Apr 25, 2022, at 7:17 AM, RFC Errata System <rfc-editor@rfc-editor.org> wrote: > > The following errata report has been submitted for RFC3394, > "Advanced Encryption Standard (AES) Key Wrap Algorithm". > > -------------------------------------- > You may review the report below and at: > https://www.rfc-editor.org/errata/eid6942 > > -------------------------------------- > Type: Editorial > Reported by: Samuel Lee <samuel.lee@microsoft.com> > > Section: 2.1 > > Original Text > ------------- > R[i] An array of 64-bit registers where > i = 0, 1, 2, ..., n > A[t], R[i][t] The contents of registers A and R[i] after encryption > step t. > > Corrected Text > -------------- > R[i] An array of 64-bit registers where > i = 1, 2, ..., n > A[t], R[t][i] The contents of registers A and R[i] after encryption > step t. > > Notes > ----- > 1) There are n 64-bit registers indexed R[1] to R[n] in the algorithms in section 2.2. > 2) The notation of the algorithms in section 2.2 dereference R[][] using the step as the first index, and the index of the register from 1 to n as the second index > > 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 > can log in to change the status and edit the report, if necessary. > > -------------------------------------- > RFC3394 (draft-ietf-smime-aes-keywrap-00) > -------------------------------------- > Title : Advanced Encryption Standard (AES) Key Wrap Algorithm > Publication Date : September 2002 > Author(s) : J. Schaad, R. Housley > Category : INFORMATIONAL > Source : S/MIME Mail Security > Area : Security > Stream : IETF > Verifying Party : IESG >
- [smime] [Editorial Errata Reported] RFC3394 (6942) RFC Errata System
- Re: [smime] [Editorial Errata Reported] RFC3394 (… Russ Housley
- Re: [smime] [Editorial Errata Reported] RFC3394 (… Russ Housley
- Re: [smime] [EXTERNAL] Re: [Editorial Errata Repo… Samuel Lee
- Re: [smime] [Editorial Errata Reported] RFC3394 (… Chris Smiley