IETF Logo Mail Archive

Re: [Curdle] sntrup761x25519-sha512

Niels Möller <nisse@lysator.liu.se> Tue, 16 May 2023 09:33 UTC

Return-Path: <nisse@lysator.liu.se>
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 3BCE1C05E027 for <curdle@ietfa.amsl.com>; Tue, 16 May 2023 02:33:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 E3RhrlGOncay for <curdle@ietfa.amsl.com>; Tue, 16 May 2023 02:33:29 -0700 (PDT)
Received: from mail.lysator.liu.se (mail.lysator.liu.se [130.236.254.3]) (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 12EAAC236F21 for <curdle@ietf.org>; Tue, 16 May 2023 02:33:28 -0700 (PDT)
Received: from mail.lysator.liu.se (localhost [127.0.0.1]) by mail.lysator.liu.se (Postfix) with ESMTP id B66641D136; Tue, 16 May 2023 11:33:24 +0200 (CEST)
Received: from shipon.lysator.liu.se (shipon.lysator.liu.se [IPv6:2001:6b0:17:f0a0::83]) by mail.lysator.liu.se (Postfix) with SMTP id 2E6551CD74; Tue, 16 May 2023 11:33:23 +0200 (CEST)
Received: by shipon.lysator.liu.se (sSMTP sendmail emulation); Tue, 16 May 2023 11:33:23 +0200
From: Niels Möller <nisse@lysator.liu.se>
To: Simon Josefsson <simon@josefsson.org>
Cc: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>, "Mark Baushke (ietf)" <mbaushke@gmail.com>, Simo Sorce <simo@redhat.com>, "curdle@ietf.org" <curdle@ietf.org>, "ietf-ssh@netbsd.org" <ietf-ssh@netbsd.org>
References: <875y8y4ip2.fsf@kaka.sjd.se> <84296E62-5843-4E7A-BD43-430491A5A1F3@akamai.com> <30525ce993ee83050cd8181c15bc84746a002f95.camel@redhat.com> <0E4AB77A-7C09-41C6-9196-74F4BD202579@akamai.com> <B3DC74FC-CF38-426F-969C-B93C4726DB5A@gmail.com> <108FE7B2-0769-4FA1-A8A4-2BD8D48C426B@akamai.com> <877ct8256g.fsf@kaka.sjd.se>
Date: Tue, 16 May 2023 11:33:23 +0200
In-Reply-To: <877ct8256g.fsf@kaka.sjd.se> (Simon Josefsson's message of "Tue, 16 May 2023 07:53:11 +0200")
Message-ID: <cpf353w1uzg.fsf@shipon.lysator.liu.se>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (berkeley-unix)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Virus-Scanned: ClamAV using ClamSMTP
Archived-At: <https://mailarchive.ietf.org/arch/msg/curdle/-DbVNc3eoENRw1cTqbpjugcca9I>
Subject: Re: [Curdle] sntrup761x25519-sha512
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: Tue, 16 May 2023 09:33:33 -0000

Simon Josefsson <simon@josefsson.org> writes:

> "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org> writes:
>
>> Nice to hear from you Mark!
>>
>>> I personally believe that using the @openssh.com extension is
>> sufficient until final NIST candidate parameters are published.
>>
>> Okay, if that works, then that makes sense :)
>
> It doesn't work -- sntrup761 is used widely on the Internet today and
> will continue to be used.

I'm not sure who's quoting who here.

But to me, documenting the way it's currently used in openssh (and
possible other implementations) seems like a great thing.

Then if the algorithm id for it is in the @openssh.org namespace, or
@josefsson.org, or an alias is defined in the iana namespace (no @...
suffix) is a detail of a lot less importance. I'd expect the currently
deployed stuff use an @openssh.org name?

Regards,
/Niels

-- 
Niels Möller. PGP key CB4962D070D77D7FCB8BA36271D8F1FF368C6677.
Internet email is subject to wholesale government surveillance.

v2.23.0 | Report a Bug | By Email