From paul.wouters@aiven.io  Fri Mar 22 21:07:06 2024
Return-Path: <paul.wouters@aiven.io>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
 by ietfa.amsl.com (Postfix) with ESMTP id B6517C15106F
 for <saag@ietfa.amsl.com>; Fri, 22 Mar 2024 21:07:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level: 
X-Spam-Status: No, score=-2.105 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, HTML_MESSAGE=0.001,
 MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001,
 RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001,
 SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01,
 URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001]
 autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key)
 header.d=aiven.io
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 pLiTOcyn_6C5 for <saag@ietfa.amsl.com>;
 Fri, 22 Mar 2024 21:07:02 -0700 (PDT)
Received: from mail-wm1-x333.google.com (mail-wm1-x333.google.com
 [IPv6:2a00:1450:4864:20::333])
 (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 33951C151066
 for <saag@ietf.org>; Fri, 22 Mar 2024 21:07:02 -0700 (PDT)
Received: by mail-wm1-x333.google.com with SMTP id
 5b1f17b1804b1-4146e9e45c8so18857905e9.1
 for <saag@ietf.org>; Fri, 22 Mar 2024 21:07:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=aiven.io; s=google; t=1711166820; x=1711771620; darn=ietf.org;
 h=to:in-reply-to:cc:references:message-id:date:subject:mime-version
 :from:content-transfer-encoding:from:to:cc:subject:date:message-id
 :reply-to; bh=kqXEbn7hLShoyEukrhtObddOG1FWam4mFnCg4UPOLTw=;
 b=A1Mix2bER05tmaU8qRHCmW9uGlbPuWws3oF/xh64JK7/kNd5Hcq1wJd3b+QbZSqAQ/
 CpC9gziJGHVs+BQonhTUQwmt7IeR2ljiKlISrIPBWL1JEbf/KdSOz+2CgychXDn0AEra
 RGXDChaNS2911ReUn5+ngMx3Xd8Kpwq2m5600=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20230601; t=1711166820; x=1711771620;
 h=to:in-reply-to:cc:references:message-id:date:subject:mime-version
 :from:content-transfer-encoding:x-gm-message-state:from:to:cc
 :subject:date:message-id:reply-to;
 bh=kqXEbn7hLShoyEukrhtObddOG1FWam4mFnCg4UPOLTw=;
 b=oA5/sFvRBP/aKc2FGt1GkkcuRoPeBG510lDmDL1bgaE28A6p/r1qKVNJ+LVrutzEX7
 HCsl3iW725kDowQ8pq75m0EyJMiK8wqqPkX3+2xejVFoUnqy5SWZq6GZklbE+A8utUzz
 GgD/Fa6yNJ/8SyT3hf05kzvH7dfibdaVqfDlvk2H4jKBUI6Cfqx8fNGCTyzosrIrStKm
 Xl92Ju67oQbzuzQbQl25zwFI4yCy5MEZuX2J7RXS6c5CPA5fEBb4K/yy9SnsUcwy+hbB
 5Js2YmLsZRyu7ApblgeuV+rMzCw0YSO3ysa0rtM7KfTMMd18E9kmThKKe16yljuzHIUS
 JUzg==
X-Forwarded-Encrypted: i=1;
 AJvYcCVQ8wDKE6sN5YKS0Ng4hRj0yCkm37KdjuQd3g891Ihg1YF2/JOdUM1bk+naDmLY1q8b8qV9HK+MGKS2MX/T
X-Gm-Message-State: AOJu0Yx/JFmhUgb5qw3PKQ+TJXA5w2HEeycfeR2DOttY2RRh+jET3aSh
 Vj9D4TQwQq8TB2SMLyTuUKkB4JVFKBh0Q3Yd+i0gbL4uvXxlxu28ntWMPnJDOjBXXvd3MI4ujbC
 E34OEgCNcUf6Hd5TeKRNCzUDgYIMSxHS8Ym3AL5suhq22wEusJxshfOxCCvadhs4Gbxj1EQ/JMC
 0I0S0wWp5CB5GmujwOIUFoa2OZyXeVww==
X-Google-Smtp-Source: AGHT+IGl3IMo1DvnJux+sSB75YhwsFGADugD+7X0RJps/MSD69vnIKRwpLuBHU7QkhW5dUHS8/jRgg==
X-Received: by 2002:a5d:4681:0:b0:33e:c0f0:c159 with SMTP id
 u1-20020a5d4681000000b0033ec0f0c159mr454498wrq.10.1711166820369; 
 Fri, 22 Mar 2024 21:07:00 -0700 (PDT)
Received: from smtpclient.apple ([185.194.184.56])
 by smtp.gmail.com with ESMTPSA id
 p1-20020a05600c358100b00414105c4cd9sm1287531wmq.21.2024.03.22.21.06.59
 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128);
 Fri, 22 Mar 2024 21:06:59 -0700 (PDT)
Content-Type: multipart/alternative;
 boundary=Apple-Mail-13B78793-DC14-4E99-9D11-E3423494D91A
Content-Transfer-Encoding: 7bit
From: Paul Wouters <paul.wouters@aiven.io>
Mime-Version: 1.0 (1.0)
Date: Sat, 23 Mar 2024 14:06:43 +1000
Message-Id: <5C2EAC21-A4F2-4442-90BA-63F4CF8D3FF1@aiven.io>
References: <CAOp4FwQ6PfX9NQY2hRNL1r572wvE0L4Crpc_Pyv2uN_1PD8G=Q@mail.gmail.com>
Cc: Eric Rescorla <ekr@rtfm.com>, saag <saag@ietf.org>
In-Reply-To: <CAOp4FwQ6PfX9NQY2hRNL1r572wvE0L4Crpc_Pyv2uN_1PD8G=Q@mail.gmail.com>
To: Loganaden Velvindron <loganaden@gmail.com>
X-Mailer: iPhone Mail (21D61)
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/58XAd9tTISBodI36HHo0UJczSzQ>
Subject: Re: [saag] SSH & Ntruprime
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/saag>,
 <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/saag/>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>,
 <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Mar 2024 04:07:06 -0000


--Apple-Mail-13B78793-DC14-4E99-9D11-E3423494D91A
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

On Mar 23, 2024, at 13:45, Loganaden Velvindron <loganaden@gmail.com> wrote:=

>=20
> =EF=BB=BF
> So this will never be updated to include curve25519+sntrup761 ?
>=20
> https://www.iana.org/assignments/ssh-parameters/ssh-parameters.xhtml#ssh-p=
arameters-16
>=20

Would openssh switch to an IETF registration or keep using their own ? Or wo=
uld applications just have to support both identical code points?

Paul=

--Apple-Mail-13B78793-DC14-4E99-9D11-E3423494D91A
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto">On Mar 23, 2024, at 13:45, Loganaden Velvin=
dron &lt;loganaden@gmail.com&gt; wrote:<br><div dir=3D"ltr"><blockquote type=
=3D"cite"><br></blockquote></div><blockquote type=3D"cite"><div dir=3D"ltr">=
=EF=BB=BF<div dir=3D"auto">So this will never be updated to include curve255=
19+sntrup761 ?<div dir=3D"auto"><br></div><div dir=3D"auto"><a href=3D"https=
://www.iana.org/assignments/ssh-parameters/ssh-parameters.xhtml#ssh-paramete=
rs-16" target=3D"_blank" rel=3D"noreferrer">https://www.iana.org/assignments=
/ssh-parameters/ssh-parameters.xhtml#ssh-parameters-16</a><br></div><div dir=
=3D"auto"><br></div></div></div></blockquote><div><br></div><div>Would opens=
sh switch to an IETF registration or keep using their own ? Or would applica=
tions just have to support both identical code points?</div><div><br></div><=
div>Paul</div></body></html>=

--Apple-Mail-13B78793-DC14-4E99-9D11-E3423494D91A--

