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

rfc-editor@rfc-editor.org Mon, 19 March 2018 22:23 UTC

Return-Path: <wwwrun@rfc-editor.org>
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 E15B312DA3D; Mon, 19 Mar 2018 15:23:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-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 Jra3VuFAjh_i; Mon, 19 Mar 2018 15:23:37 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 466CE12DA0C; Mon, 19 Mar 2018 15:23:35 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id B356EB810F9; Mon, 19 Mar 2018 15:23:27 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, curdle@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20180319222327.B356EB810F9@rfc-editor.org>
Date: Mon, 19 Mar 2018 15:23:27 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/curdle/M2sEyf2wdTvZaCO0fhQy9hHoFKM>
Subject: [Curdle] =?utf-8?q?RFC_8332_on_Use_of_RSA_Keys_with_SHA-256_and_S?= =?utf-8?q?HA-512_in_the_Secure_Shell_=28SSH=29_Protocol?=
X-BeenThere: curdle@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 19 Mar 2018 22:23:46 -0000

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
        Mailbox:    ietf-ssh3@denisbider.com
        Pages:      9
        Characters: 17873
        Updates:    RFC 4252, RFC 4253

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

        URL:        https://www.rfc-editor.org/info/rfc8332

        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 (https://www.rfc-editor.org/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
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

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


The RFC Editor Team
Association Management Solutions, LLC