IETF Logo Mail Archive

Re: [saag] SSH & Ntruprime

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 29 March 2024 10:36 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 88E08C14F5EA for <saag@ietfa.amsl.com>; Fri, 29 Mar 2024 03:36:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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, RCVD_IN_DNSWL_BLOCKED=0.001, 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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sandelman.ca
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 IfZlfhtd0ovO for <saag@ietfa.amsl.com>; Fri, 29 Mar 2024 03:36:22 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (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 CEFD3C14F5E6 for <saag@ietf.org>; Fri, 29 Mar 2024 03:36:22 -0700 (PDT)
Received: from dyas.sandelman.ca (unknown [161.30.203.8]) by relay.sandelman.ca (Postfix) with ESMTPS id 661761F448; Fri, 29 Mar 2024 10:36:19 +0000 (UTC)
Authentication-Results: relay.sandelman.ca; dkim=pass (2048-bit key; secure) header.d=sandelman.ca header.i=@sandelman.ca header.b="lelM3Jgd"; dkim-atps=neutral
Received: by dyas.sandelman.ca (Postfix, from userid 1000) id B5AF1A191D; Fri, 29 Mar 2024 23:36:10 +1300 (NZDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=sandelman.ca; s=dyas; t=1711708570; bh=SQaFzquo3VOnoC8F+f0RIPgIGwnUavaxBO+5jKiOc7Y=; h=From:To:cc:Subject:In-reply-to:References:Date:From; b=lelM3JgdMPu2nF46o4kglQ2kfquNkXlH2ZqS7a5CUTMO+iD1VPAD4d80YTqudx0vn q9P1A4pq09+cZXUvBfWaiRqBaDCAm3iyZHyyQUfWkpDN5npqDaS5qvdc3pMJO39t82 fXjZCyhRxs7XsjhUdvxYHZxojrSIBq3EeMZnLdwUL0MPhCv8FvU0mOe0xidguAeeIM wZA1/vKBADmcQCwDmt4k2v3HRN7sBlO0+lb+YLbR9SRM28xteRhbN0VTusQZugtOmh 4i2rJvo4Tfnq9Fd5Mht+iqwCAAxgF6ZrGT/z/K6AcBowKdoyNkFRuzWButCfPSGQ6v 5+0cfsH5NdJuQ==
Received: from dyas (localhost [127.0.0.1]) by dyas.sandelman.ca (Postfix) with ESMTP id B3064A0C69; Fri, 29 Mar 2024 23:36:10 +1300 (NZDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Loganaden Velvindron <loganaden@gmail.com>
cc: Paul Wouters <paul.wouters@aiven.io>, saag <saag@ietf.org>
In-reply-to: <CAOp4FwSUpp4AHwr86G5gS1K9RhLZ7KmsdHXJMRj7ZWh4=EtL_A@mail.gmail.com>
References: <CAOp4FwQ6PfX9NQY2hRNL1r572wvE0L4Crpc_Pyv2uN_1PD8G=Q@mail.gmail.com> <5C2EAC21-A4F2-4442-90BA-63F4CF8D3FF1@aiven.io> <CAOp4FwSUpp4AHwr86G5gS1K9RhLZ7KmsdHXJMRj7ZWh4=EtL_A@mail.gmail.com>
Comments: In-reply-to Loganaden Velvindron <loganaden@gmail.com> message dated "Thu, 28 Mar 2024 22:54:48 +0400."
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.3
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Fri, 29 Mar 2024 23:36:10 +1300
Message-ID: <559061.1711708570@dyas>
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/5-Ko6RWoMV8o0DqxrV-Y8Mv0tZE>
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: Fri, 29 Mar 2024 10:36:28 -0000

Loganaden Velvindron <loganaden@gmail.com> wrote:
    > Personally, I think that the OpenSSH community would switch if the
    > IETF registration process was more welcoming.

?- you can use anything you like if you @example.com it.
How is that unwelcoming?

If you want a name with an @, then write an RFC.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-                      *I*LIKE*TRAINS*

v2.23.0 | Report a Bug | By Email