IETF Logo Mail Archive

Re: [Pqc] Mapping the state of PQC and IETF - ssh

Alexandre Petrescu <alexandre.petrescu@gmail.com> Fri, 10 March 2023 14:19 UTC

Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: pqc@ietfa.amsl.com
Delivered-To: pqc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C393C14CE4A for <pqc@ietfa.amsl.com>; Fri, 10 Mar 2023 06:19:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.63
X-Spam-Level:
X-Spam-Status: No, score=-1.63 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no 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 J7zmjIf_Voty for <pqc@ietfa.amsl.com>; Fri, 10 Mar 2023 06:19:36 -0800 (PST)
Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 502D5C17B359 for <pqc@ietf.org>; Fri, 10 Mar 2023 06:19:36 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 32AEJYcx049258; Fri, 10 Mar 2023 15:19:34 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id AD702205BDE; Fri, 10 Mar 2023 15:19:34 +0100 (CET)
Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 9EAF920368E; Fri, 10 Mar 2023 15:19:34 +0100 (CET)
Received: from [10.8.32.70] (is156570.intra.cea.fr [10.8.32.70]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 32AEJYj5043132; Fri, 10 Mar 2023 15:19:34 +0100
Message-ID: <80fec8fc-2a8a-3a1d-d29f-30120b4ea6ca@gmail.com>
Date: Fri, 10 Mar 2023 15:19:34 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0
Content-Language: fr
To: Thom Wiggers <thom@thomwiggers.nl>
Cc: pqc@ietf.org
References: <20230303112532.1126239.qmail@cr.yp.to> <b086d1fb-c8a6-80df-320e-cd92e7ec2602@gmail.com> <CABzBS7k2FSWxu--eNVe8-ptPPcJ+qRVosmE2TmsjSXi_v8czBg@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
In-Reply-To: <CABzBS7k2FSWxu--eNVe8-ptPPcJ+qRVosmE2TmsjSXi_v8czBg@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/pqc/4zAV1EIg-038YlFDpBW0MQiHQbU>
Subject: Re: [Pqc] Mapping the state of PQC and IETF - ssh
X-BeenThere: pqc@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Post Quantum Cryptography discussion list <pqc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pqc>, <mailto:pqc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pqc/>
List-Post: <mailto:pqc@ietf.org>
List-Help: <mailto:pqc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pqc>, <mailto:pqc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Mar 2023 14:19:40 -0000


Le 10/03/2023 à 15:10, Thom Wiggers a écrit :
> Hi Alexandre,
> 
> 
> Op vr 10 mrt 2023 om 14:47 schreef Alexandre Petrescu 
> <alexandre.petrescu@gmail.com
> <mailto:alexandre.petrescu@gmail.com>>:
> 
> 
> 
> But how about openssh saying "WE DO NOT RECOMMEND RELYING ON THIS
> FORK IN A PRODUCTION ENVIRONMENT OR TO PROTECT ANY SENSITIVE DATA"?
> at https://github.com/open-quantum-safe/openssl 
> <https://github.com/open-quantum-safe/openssl>
> 
> 
> This is Open Quantum Safe's experimental fork of the OpenSSL project
>  (they similarly have an OpenSSH fork) and not the upstream OpenSSL
> (nor OpenSSH) project.
> 
> OpenSSH has integrated NTRUPrime and made it the default key exchange
>  algorithm (hybridized with ECDH) in version 8.9, released just over
> a year ago.

Thanks for the explanation.  It seems I am being disinformed by my own
trusted source.  It seems the best might come from the public
discussion.  Or maybe it is simply a learning process.

Let me ask this: when I call 'ssh' in command line without any other
argument than the destination host address - is NTRUPrime being used?
Or do I have to type in some additional option like -qr or -ntruprime or
similar?

Alex

> 
> Cheers,
> 
> Thom
> 
> Alex
> 
> -- Pqc mailing list Pqc@ietf.org <mailto:Pqc@ietf.org> 
> https://www.ietf.org/mailman/listinfo/pqc 
> <https://www.ietf.org/mailman/listinfo/pqc>
>

v2.23.0 | Report a Bug | By Email