IETF Logo Mail Archive

Re: [Curdle] RFC 9142 on Key Exchange (KEX) Method Updates and Recommendations for Secure Shell (SSH)

denis bider <denisbider.ietf@gmail.com> Fri, 14 January 2022 09:31 UTC

Return-Path: <denisbider.ietf@gmail.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 E81783A1FF9 for <curdle@ietfa.amsl.com>; Fri, 14 Jan 2022 01:31:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.098
X-Spam-Level:
X-Spam-Status: No, score=-1.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 sGi7SqnQDMyN for <curdle@ietfa.amsl.com>; Fri, 14 Jan 2022 01:31:42 -0800 (PST)
Received: from mail-io1-xd2b.google.com (mail-io1-xd2b.google.com [IPv6:2607:f8b0:4864:20::d2b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F2BF33A1FF8 for <curdle@ietf.org>; Fri, 14 Jan 2022 01:31:41 -0800 (PST)
Received: by mail-io1-xd2b.google.com with SMTP id v1so11589529ioj.10 for <curdle@ietf.org>; Fri, 14 Jan 2022 01:31:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=tuOo2l5COJPDlBxy6G8DRUUeYTr9lHLPpl/jc15Idd0=; b=FOYUGkrshg/Om8y/xgFxvr9gpwn/mzleOmr4V+mhbQotrp/TpGNdUo3rt9D5NqwWJH PfuHqVvrBJSmGm41aPEz66qnEhUAWw2L8jtWwMZNGM4/MgxANynvxNLqF92h0l0Mf2Be 7YXiZCPYvtwogKFAsZGw8fTt3Eo0X+XmWt0VYU8TSfw2PQvvQyFD5/iarLMpprsoDDK6 WKiwOhZ0AUpBsz2j57VlJOH08Tu5THe0+ancCoVWOnuO9GzLkj9WhvoKy5v7AVSTJc/4 9otyJebqANlZnLf6YR8rV1IPJc/YgPU/jELyOft3M2CaGU14H7ZA1HM5ypTdvOVSu0UV 5hJw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=tuOo2l5COJPDlBxy6G8DRUUeYTr9lHLPpl/jc15Idd0=; b=hPlx81JBmF5Naj5XmwHHQqz3wx6QDaFwHp6wKXkFSXcDIUrVVlIGb66AgXQ/GY8frh AlS1lP8ehi7U5GcLeAyRdDYX9Kqflqa/BTm3JE6mfVLXjtP2PA8ABoSi8JFsa4bivVMp xOuC/Zad2jfLrIwr+K9bHGd8KxWRC8GmHmePleuydpfjWlmbt6i5udSYYg/K394JY+aL 0rxs6csmVTjRsJ7lo/hyjlnSs3u0fpws5rwsZqMFRABq7Zu8kyoI5DeBW06BDVEKYo5C iIUFbjrQtTEnswpyqEXuQCFpEt0l78Oc0iWGkAL+qj0ifQBpAAmRvnY91ZUxg1eC3imK 0e1g==
X-Gm-Message-State: AOAM533kWnMZF/Z0/5bzoOADr9b9rpmjq4/vrF54ssXZtker8N81L943 hO1/4+4REDZUkGsdHPHxDvYjXeq0fCU1cQfWwC1GFyhT
X-Google-Smtp-Source: ABdhPJzaNiBUGz+BsJ2HMhEyUEuoX3dMdCsA1nv7LSfcekxa2DAkYg7FYPboqM/njnA6WzcVDrpEnUYkcnyCVHGMaAE=
X-Received: by 2002:a05:6638:264a:: with SMTP id n10mr3693347jat.90.1642152700193; Fri, 14 Jan 2022 01:31:40 -0800 (PST)
MIME-Version: 1.0
References: <20220114053618.3C06DF5DC8@rfc-editor.org>
In-Reply-To: <20220114053618.3C06DF5DC8@rfc-editor.org>
From: denis bider <denisbider.ietf@gmail.com>
Date: Fri, 14 Jan 2022 03:31:29 -0600
Message-ID: <CADPMZDCEUXbOEN8oc9xeQOMmYCUFUh0ZfVjFOMc70HJreUADCQ@mail.gmail.com>
To: curdle <curdle@ietf.org>, "Mark Baushke (ietf)" <mbaushke@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/curdle/yBIqwHqRAddcWjoqPv8c9r3UmSI>
Subject: Re: [Curdle] RFC 9142 on Key Exchange (KEX) Method Updates and Recommendations for Secure Shell (SSH)
X-BeenThere: curdle@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 14 Jan 2022 09:31:46 -0000

Nice! Congrats, Mark! :-)

Thanks for the perseverance on this one!

On Thu, Jan 13, 2022 at 11:36 PM <rfc-editor@rfc-editor.org> wrote:
>
> 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
>
> _______________________________________________
> Curdle mailing list
> Curdle@ietf.org
> https://www.ietf.org/mailman/listinfo/curdle

v2.23.0 | Report a Bug | By Email