IETF Logo Mail Archive

Re: [saag] SSH & Ntruprime

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 29 March 2024 10:37 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 AD172C14F5EA for <saag@ietfa.amsl.com>; Fri, 29 Mar 2024 03:37:36 -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 1kM_dsrM-_7i for <saag@ietfa.amsl.com>; Fri, 29 Mar 2024 03:37:32 -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)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B4F3C14F5E6 for <saag@ietf.org>; Fri, 29 Mar 2024 03:37:32 -0700 (PDT)
Received: from dyas.sandelman.ca (unknown [161.30.203.8]) by relay.sandelman.ca (Postfix) with ESMTPS id 2BB711F448; Fri, 29 Mar 2024 10:37:28 +0000 (UTC)
Authentication-Results: relay.sandelman.ca; dkim=pass (2048-bit key; secure) header.d=sandelman.ca header.i=@sandelman.ca header.b="gruXqAxb"; dkim-atps=neutral
Received: by dyas.sandelman.ca (Postfix, from userid 1000) id EAFCEA191D; Fri, 29 Mar 2024 23:37:18 +1300 (NZDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=sandelman.ca; s=dyas; t=1711708638; bh=VdB6I0w5Hs3PlhCjmUwUYNoRtm8qP1z4LBU2XSOGOq0=; h=From:To:cc:Subject:In-reply-to:References:Date:From; b=gruXqAxboKX0/XWGQHVzwHGwwHPW9YIZzQjMXTaP4WbNoH8pdx4/7Zb8klN45TujP oC8ssfvxi91yvYzlyry/JLGFRoAzs/nhs6ok/l6DU7bVq/ZRyFHm6h9Lkw0h8PHP8S VIpaEWeeP4gVObGhPxoGEAl56dQZvMkX160uTXb//8/xgWVMFSNr0zXBn8n4KAULsW VcdzTJPsOhyj7zJpGJGjfsYbpJqviiFRgfkLN9LqrPX1y0zkdjSFU+XZ0FaxYH9cJ5 ACjxxVqZddeKH6xXcg5l22bjpUyWdC7xr0MK1+fovRPG1Nqc8Yt8C5MX7nZDuncrBy l+LYtnuJxBdnA==
Received: from dyas (localhost [127.0.0.1]) by dyas.sandelman.ca (Postfix) with ESMTP id E9259A0C69; Fri, 29 Mar 2024 23:37:18 +1300 (NZDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Loganaden Velvindron <loganaden@gmail.com>
cc: saag <saag@ietf.org>
In-reply-to: <CAOp4FwSFZTJ574chhfBHPDH8un6kayRMyZBSt2pcxBcgPY0Rtw@mail.gmail.com>
References: <CABcZeBPWjXvLh06-DBO3Z0sfeb2hgzqzaSZ-J2-TZ7qesrSraA@mail.gmail.com> <D0CD341B-523B-48A0-8954-EE7F89113241@aiven.io> <AF7B6F32-9EE6-4810-A99A-833DEA917FA9@sonic.net> <CABcZeBPfXQckpZageogUxTYgX2j_Nr_O3bvf-a-x0S_82BHMxg@mail.gmail.com> <079A0AA3-FA02-440F-ABA0-6AF897570E86@sonic.net> <CABcZeBOxfYR+=61DV1XN0F9nrmbzLR2zq_ZvADw4UUy1uFafzw@mail.gmail.com> <8caa2d4d-bc80-4fcf-b8bc-839052371730@lear.ch> <CABcZeBMABJ89T0qY0-9C3xxd=mFfGyCh7_9GKbEUBm6JtR+_ng@mail.gmail.com> <87sf0dupjn.fsf@kaka.sjd.se> <CAN8C-_JTwA1fP=d0c_AXOdYsAX6fDfnFb0U05aO8y8tg8R3bVw@mail.gmail.com> <484345.1711508956@dyas> <CAOp4FwSFZTJ574chhfBHPDH8un6kayRMyZBSt2pcxBcgPY0Rtw@mail.gmail.com>
Comments: In-reply-to Loganaden Velvindron <loganaden@gmail.com> message dated "Thu, 28 Mar 2024 22:40:02 +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:37:18 +1300
Message-ID: <559112.1711708638@dyas>
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/mrs_U1EEltRlWVwnv7ltJtjdsuo>
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:37:36 -0000

Loganaden Velvindron <loganaden@gmail.com> wrote:
    >> Orie Steele <orie@transmute.industries> wrote:
    >> > 1. Publish SSH related specifications as RFCs
    >> > 2. Support the review process from RFC9519 (We're working to resolve the
    >> > issue with the list, thanks for reporting it)
    >>
    >> > I don't think using IDs to document SSH algorithms and then never
    >> > publishing those drafts helps either community.
    >>
    >> It's a lot of effort and money to publish a document for an algorithm that
    >> some say isn't as secure as claimed, and perhaps shouldn't be widely implemented.
    >>
    > Hi Michael,

    > I asked about the security of ntru prime back in December 2022:

    > https://mailarchive.ietf.org/arch/msg/cfrg/AX9WGbiNpNmRpe9KJ1DEc7vi6ss/

    > Are you aware of weaknesses in ntruprime now ?
    > Can you please share if such is the case ?

It's above my paygrade to understand comment, sorry.
So what I said was heresay. Sorry abou that.

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

v2.23.0 | Report a Bug | By Email