[smime] [Errata Verified] RFC4056 (7280)

RFC Errata System <rfc-editor@rfc-editor.org> Tue, 20 December 2022 22:14 UTC

Return-Path: <wwwrun@rfcpa.amsl.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 4FA4BC14F74D; Tue, 20 Dec 2022 14:14:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.648
X-Spam-Level:
X-Spam-Status: No, score=-6.648 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LmNA_oBy0c7T; Tue, 20 Dec 2022 14:14:00 -0800 (PST)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A63BC14F74E; Tue, 20 Dec 2022 14:14:00 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 119B14C95E; Tue, 20 Dec 2022 14:14:00 -0800 (PST)
To: jaak.ristioja@cyber.ee, jimsch@exmsft.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: rfc-ed@rfc-editor.org, iesg@ietf.org, smime@ietf.org, iana@iana.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20221220221400.119B14C95E@rfcpa.amsl.com>
Date: Tue, 20 Dec 2022 14:14:00 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/smime/UBFwjC04V52ZTCn_0zMNPbP18xI>
Subject: [smime] [Errata Verified] RFC4056 (7280)
X-BeenThere: smime@ietf.org
X-Mailman-Version: 2.1.39
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: Tue, 20 Dec 2022 22:14:04 -0000

The following errata report has been verified for RFC4056,
"Use of the RSASSA-PSS Signature Algorithm in Cryptographic Message Syntax (CMS)". 

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid7280

--------------------------------------
Status: Verified
Type: Editorial

Reported by: Jaak Ristioja <jaak.ristioja@cyber.ee>
Date Reported: 2022-12-20
Verified by: RFC Editor  

Section: 2.2

Original Text
-------------
The algorithm identifier for RSASAA-PSS signatures is:

Corrected Text
--------------
The algorithm identifier for RSASSA-PSS signatures is:

Notes
-----
Replace RSASAA-PSS with RSASSA-PSS.

--------------------------------------
RFC4056 (draft-ietf-smime-pss-03)
--------------------------------------
Title               : Use of the RSASSA-PSS Signature Algorithm in Cryptographic Message Syntax (CMS)
Publication Date    : June 2005
Author(s)           : J. Schaad
Category            : PROPOSED STANDARD
Source              : S/MIME Mail Security
Area                : Security
Stream              : IETF