IETF Logo Mail Archive

Re: [saag] sntrup761x25519-sha512

Mark Baushke <mbaushke@gmail.com> Tue, 23 May 2023 23:54 UTC

Return-Path: <mbaushke@gmail.com>
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 3D038C15109C for <saag@ietfa.amsl.com>; Tue, 23 May 2023 16:54:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.202
X-Spam-Level:
X-Spam-Status: No, score=-1.202 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, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.1, MIME_HTML_ONLY_MULTI=0.001, MIME_QP_LONG_LINE=0.001, MPART_ALT_DIFF=0.79, 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=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aMKYovrZ517d for <saag@ietfa.amsl.com>; Tue, 23 May 2023 16:54:36 -0700 (PDT)
Received: from mail-qk1-x72d.google.com (mail-qk1-x72d.google.com [IPv6:2607:f8b0:4864:20::72d]) (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 ACCA8C14CE2F for <saag@ietf.org>; Tue, 23 May 2023 16:54:31 -0700 (PDT)
Received: by mail-qk1-x72d.google.com with SMTP id af79cd13be357-75b0f2ce4b7so43673385a.2 for <saag@ietf.org>; Tue, 23 May 2023 16:54:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1684886070; x=1687478070; h=to:references:message-id:cc:date:in-reply-to:from:subject :mime-version:content-transfer-encoding:from:to:cc:subject:date :message-id:reply-to; bh=06ZEbQzUPdyCZyxGlOPXbuC/aaBQ8HJQ6lnznaK6F6I=; b=kp1KJ5JqwBt+16efUAtoQU52zgbcqDPb/mEpTySCImL6iCDyREeG+6D/Anrq1Cia6u VYEJEiDAcs2peQ3ZIeQWu/F1CrNon8SfLQ2fJi/JjV00FCd5iS1jCP4HseksL86Ybeg/ sR765XAO5mDYnfmn1OJyL4VH9VSCJSgbBX9jypAcBc/maaH4R6QkvHNSbUu61RIzzLJB 9nV5ijJTpUDP/ZGUCfkq2ONE+E74iO2GpxAlThm2NWpsNSjCThOOsABqvwWugVfIExzW yTqDphd222F7gNlln5Ma/QQczM30OL/LLzTzvd2kt9wMggq7xm5R9IV6d10+knGl7pO9 TEXg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684886070; x=1687478070; h=to:references:message-id:cc:date:in-reply-to:from:subject :mime-version:content-transfer-encoding:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=06ZEbQzUPdyCZyxGlOPXbuC/aaBQ8HJQ6lnznaK6F6I=; b=Qkp9S+212KqWl/ClGcucgbjyFJGs5izrkVPNlUMebH/alamaNCvctoRdLvoy3e69rZ FpgVC6b3YH1UM4Noa/7ymleJG8r8CoQcQ+aKfo7mrDu772yK11eTZR/Ggn3I9GJJacjC m5Kz3wNwW51txxioPXHqJXsHBnRZbSKEJqPh8GiQall4sC8p9WmfmUI578zN3gocfOYJ jvc5jOfmKub74MGu45JERyUAVyGtWWHTeaCLc3U4lMhuXAFO69Z1bl78wG1vtFJjUXTn 5qBL7JOerBU1VWY3CR4vMVHcPRMlNUSMmLIlF0KWYb+G533BIZKIFkU0tqHINEEQpd5T cqIA==
X-Gm-Message-State: AC+VfDzK7BL3j1blsnCjqC+Rfq17OsI4GEbDkYqitD+c1RH+frC+PNXc xFRLMuRpWy4JLBnQblcoSts=
X-Google-Smtp-Source: ACHHUZ70mXcg8v7jdHaEWKNXH9v0Rf7XfDvteq7cCXyhrC5crYxNZzl9/PTLwjM5hKOaxCCMLoETvA==
X-Received: by 2002:a05:6214:2b0b:b0:625:aa1a:9384 with SMTP id jx11-20020a0562142b0b00b00625aa1a9384mr108554qvb.64.1684886070277; Tue, 23 May 2023 16:54:30 -0700 (PDT)
Received: from smtpclient.apple ([2601:246:5481:da50:7911:fb75:3268:6315]) by smtp.gmail.com with ESMTPSA id d5-20020a0cfe85000000b005ef5f7c1ae1sm3090388qvs.105.2023.05.23.16.54.29 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 23 May 2023 16:54:29 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail-E1CC46F2-5C6D-4052-B068-FFB802E7EBC3"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
From: Mark Baushke <mbaushke@gmail.com>
In-Reply-To: <CABcZeBMobKFKjtFn3xt7DDD1rx0ZtvW2m5sq6Gz1q29ETp04rQ@mail.gmail.com>
Date: Tue, 23 May 2023 18:54:18 -0500
Cc: Simon Josefsson <simon=40josefsson.org@dmarc.ietf.org>, saag@ietf.org
Message-Id: <B8A2154F-5A94-404A-AB90-C34A05DAFB7B@gmail.com>
References: <CABcZeBMobKFKjtFn3xt7DDD1rx0ZtvW2m5sq6Gz1q29ETp04rQ@mail.gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
X-Mailer: iPad Mail (20E252)
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/bVpEl_gJliILFHHGX8OPdi-2yN0>
Subject: Re: [saag] sntrup761x25519-sha512
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: Tue, 23 May 2023 23:54:37 -0000

+1 on loosening SSH Kex code policy for adding points to the IANA registry.

-- Mark

[Sent from my iPad -- Please pardon any auto-fix created typos.]

On May 23, 2023, at 5:57 PM, Eric Rescorla <ekr@rtfm.com> wrote:


Without taking a position on this draft, I think it would be good if we loosened
the policy for the SSH-KEX registry, as we have for TLS and some other
protocols.

-Ekr


On Tue, May 23, 2023 at 3:37 PM Simon Josefsson <simon=40josefsson.org@dmarc.ietf.org> wrote:
"Martin Thomson" <mt@lowentropy.net> writes:

> On Tue, May 23, 2023, at 15:35, Simon Josefsson wrote:
>> In the same way that if the IETF decided to change the details of a
>> deployed protocol, then the implementor community would change over to
>> that code point, yes.
>
> So if the IETF decided that Kyber was preferred to SNTRU (as Panos
> suggested), that goes too, right?  That's a pretty significant change,
> but a good test of whether this is IETF vs. independent for me.

I may be missing your actual point, and I don't speak for anyone but
myself, but I believe that the SSH community is interested in
standardizing, implementing and deploying a KEX based on Kyber in
collaboration with the IETF community, and further believe that this
does not take away the desire or usefulness for the IETF to publish a
document that describes sntrup761x25519-sha512.  Those are orthogonal
issues.  The latter is a widely deployed SSH KEX and will continue to be
widely used for many years to come, even if Kyber would be implemented
as well.

> I think that you said that you wouldn't be interested in that outcome,
> which is why I suggested that independent submissions would be better.

As far as I understand, the independent submission route is not possible
due to the IANA registration policy for the SSH KEX registry.

/Simon
_______________________________________________
saag mailing list
saag@ietf.org
https://www.ietf.org/mailman/listinfo/saag" rel="noreferrer nofollow" target="_blank">https://www.ietf.org/mailman/listinfo/saag
_______________________________________________
saag mailing list
saag@ietf.org
https://www.ietf.org/mailman/listinfo/saag

v2.23.0 | Report a Bug | By Email