RFC 9142 on Key Exchange (KEX) Method Updates and Recommendations for Secure Shell (SSH)

rfc-editor@rfc-editor.org Fri, 14 January 2022 05:36 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4EF343A1B1A; Thu, 13 Jan 2022 21:36:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, 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 MKs18R02oFEq; Thu, 13 Jan 2022 21:36:21 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4C01E3A1B19; Thu, 13 Jan 2022 21:36:19 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 499) id 3C06DF5DC8; Thu, 13 Jan 2022 21:36:18 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9142 on Key Exchange (KEX) Method Updates and Recommendations for Secure Shell (SSH)
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: <20220114053618.3C06DF5DC8@rfc-editor.org>
Date: Thu, 13 Jan 2022 21:36:18 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/a1S5YCoDPSZN6djjA8OOXQdjts8>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Jan 2022 05:36:25 -0000

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

        
        RFC 9142

        Title:      Key Exchange (KEX) Method Updates 
                    and Recommendations for Secure Shell (SSH) 
        Author:     M. Baushke
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2022
        Mailbox:    mbaushke.ietf@gmail.com
        Pages:      19
        Updates:    RFC 4250, RFC 4253, RFC 4432, RFC 4462

        I-D Tag:    draft-ietf-curdle-ssh-kex-sha2-20.txt

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

        DOI:        10.17487/RFC9142

This document updates the recommended set of key exchange methods for
use in the Secure Shell (SSH) protocol to meet evolving needs for
stronger security.  It updates RFCs 4250, 4253, 4432, and 4462.

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