IETF Logo Mail Archive

Re: [TLS] [Errata Verified] RFC8422 (5703)

Benjamin Kaduk <kaduk@mit.edu> Wed, 01 May 2019 17:17 UTC

Return-Path: <kaduk@mit.edu>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C121F12008F; Wed, 1 May 2019 10:17:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 jyRnosy2n0cz; Wed, 1 May 2019 10:17:58 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.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 1F1A21200A2; Wed, 1 May 2019 10:17:57 -0700 (PDT)
Received: from kduck.mit.edu (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id x41HHl7n027888 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 1 May 2019 13:17:49 -0400
Date: Wed, 01 May 2019 12:17:47 -0500
From: Benjamin Kaduk <kaduk@mit.edu>
To: Peter Gutmann <pgut001@cs.auckland.ac.nz>
Cc: RFC Errata System <rfc-editor@rfc-editor.org>, "Frank.Theinen@web.de" <Frank.Theinen@web.de>, "ynir.ietf@gmail.com" <ynir.ietf@gmail.com>, "simon@josefsson.org" <simon@josefsson.org>, "mpg@elzevir.fr" <mpg@elzevir.fr>, "tls@ietf.org" <tls@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
Message-ID: <20190501171746.GL59871@kduck.mit.edu>
References: <20190501170139.09724B81BFF@rfc-editor.org> <1556730851631.37840@cs.auckland.ac.nz>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <1556730851631.37840@cs.auckland.ac.nz>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/Olwx_6J84tJ-rHEcvnWtcuPDPLI>
Subject: Re: [TLS] [Errata Verified] RFC8422 (5703)
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 May 2019 17:18:00 -0000

On Wed, May 01, 2019 at 05:14:16PM +0000, Peter Gutmann wrote:
> RFC Errata System <rfc-editor@rfc-editor.org> writes:
> 
> >Section 7.2 of RFC 8017 describes the RSAES-PKCS1-v1_5 encryption scheme.
> >Section 8.2 of RFC 8017 describes the RSASSA-PKCS1-v1_5 signature scheme. The
> >original text contradicts the natural expectation and is probably wrong.
> 
> The original text is correct, TLS 1.2 (and earlier) use PKCS #1 v1.5.  Stating
> that RSA-PSS should be used is wrong.

Section 7.2 is an encryption scheme, not a signature scheme; this is just a
typo.

(And RSASSA-PKCS1-v1_5 is, well, PKCS #1 v1.5, not RSASSA-PSS.)

-Ben

v2.23.0 | Report a Bug | By Email