Re: [Curdle] [Technical Errata Reported] RFC9142 (7799)

Russ Housley <housley@vigilsec.com> Wed, 07 February 2024 15:33 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: curdle@ietfa.amsl.com
Delivered-To: curdle@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE96EC1519AF for <curdle@ietfa.amsl.com>; Wed, 7 Feb 2024 07:33:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level:
X-Spam-Status: No, score=-6.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 PTxXVV8Q_Tsf for <curdle@ietfa.amsl.com>; Wed, 7 Feb 2024 07:32:56 -0800 (PST)
Received: from mail3.g24.pair.com (mail3.g24.pair.com [66.39.134.11]) (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 DA059C1516EB for <curdle@ietf.org>; Wed, 7 Feb 2024 07:32:56 -0800 (PST)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id E2A60122E2E; Wed, 7 Feb 2024 10:32:55 -0500 (EST)
Received: from smtpclient.apple (unknown [96.241.2.243]) (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 BE47B123089; Wed, 7 Feb 2024 10:32:55 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <20240207151307.56DF718F0F68@rfcpa.amsl.com>
Date: Wed, 07 Feb 2024 10:32:45 -0500
Cc: mbaushke.ietf@gmail.com, daniel.migault@ericsson.com, Rich Salz <rsalz@akamai.com>, ben.s3@ncsc.gov.uk, curdle@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <A47EC294-3DCF-4902-8864-1BDC33B321E2@vigilsec.com>
References: <20240207151307.56DF718F0F68@rfcpa.amsl.com>
To: "Roman D. Danyliw" <rdd@cert.org>, Paul Wouters <paul.wouters@aiven.io>
X-Mailer: Apple Mail (2.3731.700.6)
X-Scanned-By: mailmunge 3.11 on 66.39.134.11
Archived-At: <https://mailarchive.ietf.org/arch/msg/curdle/DM9NCdaQrdTAxmu_1DhVgaWhS0A>
Subject: Re: [Curdle] [Technical Errata Reported] RFC9142 (7799)
X-BeenThere: curdle@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "List for discussion of potential new security area wg." <curdle.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/curdle>, <mailto:curdle-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/curdle/>
List-Post: <mailto:curdle@ietf.org>
List-Help: <mailto:curdle-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/curdle>, <mailto:curdle-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Feb 2024 15:33:00 -0000

This looks correct to me.  It should be approved.

Russ


> On Feb 7, 2024, at 10:13 AM, RFC Errata System <rfc-editor@rfc-editor.org> wrote:
> 
> The following errata report has been submitted for RFC9142,
> "Key Exchange (KEX) Method Updates and Recommendations for Secure Shell (SSH)".
> 
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid7799
> 
> --------------------------------------
> Type: Technical
> Reported by: Ben S <ben.s3@ncsc.gov.uk>
> 
> Section: 1.2.1
> 
> Original Text
> -------------
> +============+=============================+
> | Curve Name | Estimated Security Strength |
> +============+=============================+
> | nistp256   | 128 bits                    |
> +------------+-----------------------------+
> | nistp384   | 192 bits                    |
> +------------+-----------------------------+
> | nistp521   | 512 bits                    |
> +------------+-----------------------------+
> | curve25519 | 128 bits                    |
> +------------+-----------------------------+
> | curve448   | 224 bits                    |
> +------------+-----------------------------+
> 
> Corrected Text
> --------------
> +============+=============================+
> | Curve Name | Estimated Security Strength |
> +============+=============================+
> | nistp256   | 128 bits                    |
> +------------+-----------------------------+
> | nistp384   | 192 bits                    |
> +------------+-----------------------------+
> | nistp521   | 256 bits                    |
> +------------+-----------------------------+
> | curve25519 | 128 bits                    |
> +------------+-----------------------------+
> | curve448   | 224 bits                    |
> +------------+-----------------------------+
> 
> Notes
> -----
> P-521 has approximately 256 bits of security (rather than 512), as per Table 1 of Section 6.1.1 of FIPS 186-5, and Section 9 Paragraph 5 of RFC 5656.
> 
> Instructions:
> -------------
> This erratum is currently posted as "Reported". (If it is spam, it 
> will be removed shortly by the RFC Production Center.) Please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party  
> will log in to change the status and edit the report, if necessary.
> 
> --------------------------------------
> RFC9142 (draft-ietf-curdle-ssh-kex-sha2-20)
> --------------------------------------
> Title               : Key Exchange (KEX) Method Updates and Recommendations for Secure Shell (SSH)
> Publication Date    : January 2022
> Author(s)           : M. Baushke
> Category            : PROPOSED STANDARD
> Source              : CURves, Deprecating and a Little more Encryption
> Area                : Security
> Stream              : IETF
> Verifying Party     : IESG