Re: [Curdle] RFC 8332 on Use of RSA Keys with SHA-256 and SHA-512 in the Secure Shell (SSH) Protocol

Daniel Migault <> Mon, 19 March 2018 22:46 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A07571205F0 for <>; Mon, 19 Mar 2018 15:46:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id CKs_a4VjNEz8 for <>; Mon, 19 Mar 2018 15:46:14 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id B4486124BAC for <>; Mon, 19 Mar 2018 15:46:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256;; s=mailgw201801; c=relaxed/simple; q=dns/txt;; t=1521499574; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=OA7gIUJqDgw1zku/gixJV51b5aRLc9agnqESpeemSf0=; b=N8EVkH+sH8A5ppzP7OgJTbVBWUXpOLc4l6lKGIA03pGTT36XivBzepA+L7E8Xvta CGM9jSww5xTRqIS+jJhhULre8pYmBB8I1SoAOn36cms04MXwbJ50PV7HivzJTOdu LHhYh9UgJdBt4Y1ObfZXvXdd2S4a7lu9XHvOEhojHxg=;
X-AuditID: c618062d-8d7ff70000004288-61-5ab03db52bb8
Received: from (Unknown_Domain []) by (Symantec Mail Security) with SMTP id 4F.83.17032.5BD30BA5; Mon, 19 Mar 2018 23:46:14 +0100 (CET)
Received: from ([]) by ([]) with mapi id 14.03.0382.000; Mon, 19 Mar 2018 18:46:13 -0400
From: Daniel Migault <>
To: "" <>
CC: "" <>, "" <>
Thread-Topic: [Curdle] RFC 8332 on Use of RSA Keys with SHA-256 and SHA-512 in the Secure Shell (SSH) Protocol
Thread-Index: AQHTv9Eo43oweq6rnEaDxvF3iuO/16PYKDVg
Date: Mon, 19 Mar 2018 22:46:12 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrOLMWRmVeSWpSXmKPExsUyuXRPgu422w1RBveOMlpsXTiL2eLWj0Z2 i6b9X9kcmD165D2WLPnJ5NHQdow1gDmKyyYlNSezLLVI3y6BK+N043TGghciFVfOf2ZuYJwn 0MXIySEhYCJxf/YBli5GLg4hgSOMEg3fDrCBJIQEljNK3GkSArHZBIwk2g71s4PYIgLWEh+3 zmYCsZkFUiTWrJkMVi8skC+x5MAGRoiaAolVxy8wQdhGEle7d4LFWQRUJVZO/wMW5xXwlVh/ +j07xC5ziSdP54LVcApYSKzc2QI2k1FATOL7qTVQu8Qlbj2ZzwRxtIDEkj3nmSFsUYmXj/+x QtjKEpf/v2OHqNeRWLD7ExuErS2xbOFrZoi9ghInZz5hmcAoOgvJ2FlIWmYhaZmFpGUBI8sq Ro7S4oKc3HQjg02MwOg4JsGmu4Px/nTPQ4wCHIxKPLzr5TdECbEmlhVX5h5ilOBgVhLhfXpl XZQQb0piZVVqUX58UWlOavEhRmkOFiVx3jOevFFCAumJJanZqakFqUUwWSYOTqkGxkiuTwdk t9jVnViWv2p3pzpTXdMbuy/PlHZ/SLr9XTnSYr1thWde68fNLGfPJdfM5qmfcDenb81EEcO+ p4Z/npwJmfbuuHZnrZRZz4z7h94ecvibtffQ3gWK1mf29xbNv6rwc/u9J/e2W+iWuTQ7X2i0 6ehmqxGbMGGRzb/gnEvfdwjJTs8001ZiKc5INNRiLipOBAAJY1tsigIAAA==
Archived-At: <>
Subject: Re: [Curdle] RFC 8332 on Use of RSA Keys with SHA-256 and SHA-512 in the Secure Shell (SSH) Protocol
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "List for discussion of potential new security area wg." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 19 Mar 2018 22:46:18 -0000

Thank you all for your effort and congratulation Denis!

-----Original Message-----
From: Curdle [] On Behalf Of
Sent: Monday, March 19, 2018 10:23 PM
Subject: [Curdle] RFC 8332 on Use of RSA Keys with SHA-256 and SHA-512 in the Secure Shell (SSH) Protocol

A new Request for Comments is now available in online RFC libraries.

        RFC 8332

        Title:      Use of RSA Keys with SHA-256 and SHA-512 
                    in the Secure Shell (SSH) Protocol 
        Author:     D. Bider
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2018
        Pages:      9
        Characters: 17873
        Updates:    RFC 4252, RFC 4253

        I-D Tag:    draft-ietf-curdle-rsa-sha2-12.txt


        DOI:        10.17487/RFC8332

This memo updates RFCs 4252 and 4253 to define new public key algorithms for use of RSA keys with SHA-256 and SHA-512 for server and client authentication in SSH connections.

This document is a product of the CURves, Deprecating and a Little more Encryption Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements.  Please refer to the current edition of the Official Internet Protocol Standards ( for the standardization state and status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see For downloading RFCs, see

Requests for special distribution should be addressed to either the author of the RFC in question, or to  Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC

Curdle mailing list