Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Stephan =?ISO-8859-1?Q?M=FCller?= <smueller@chronox.de>
To:     yumeng <yumeng18@huawei.com>
Cc:     linux-crypto@vger.kernel.org, xuzaibo@huawei.com,
        wangzhou1@hisilicon.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 4/5] crypto: hisilicon/hpre - add 'ECDH' algorithm
Date:   Sat, 19 Dec 2020 22:25:32 +0100
Message-ID: <4588284.GXAFRqVoOG@positron.chronox.de>
In-Reply-To: <06fa1f72-fad8-a3e5-987a-d322918ac30a@huawei.com>
References: <13db294664a6b2e26a892dd544c714d3e385b0cc.camel@chronox.de> <b38e3b40ef198166bff193940b8c82c41db6f13c.camel@chronox.de> <06fa1f72-fad8-a3e5-987a-d322918ac30a@huawei.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Precedence: bulk

Am Donnerstag, 17. Dezember 2020, 04:07:30 CET schrieb yumeng:

Hi yumeng,

> 
> I see in "SEC 2: Recommended Elliptic Curve Domain ParametersVersion2.0"
> that 'Recommend Elliptic Curve Domain Parameters over Fp' are secp192,
> secp224, secp256, secp384, and secp521, secp128 and secp320 are not
> recommended.
> So you mean it's better not to include secp128 and secp320, right?

Precisely because I do not see the use case in the kernel.
> 
> Thanks,


Ciao
Stephan