Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp1484617pxb; Thu, 28 Jan 2021 19:02:21 -0800 (PST) X-Google-Smtp-Source: ABdhPJyv5N/b/IyWe3MCsZKHBv4nfXB9vEcUk0kfPTo0tv6AAz4OtETQLgZD3qZOkH0IU9rgGXKZ X-Received: by 2002:a50:ec05:: with SMTP id g5mr2883498edr.182.1611889341780; Thu, 28 Jan 2021 19:02:21 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1611889341; cv=none; d=google.com; s=arc-20160816; b=s6YqWJbeSH/Yyi4nNiMFyXMoVTCb/jTjnEyPusvd5iCLBkYnrhCaqRyFlTLtw/RRjY fByz0KuOsoPOWJgOFFf4fDQo9fUPPZrHdJtLFu5pRG7AuE4g5dvSaBZDfP9bt2YzVdne O/xCHaXD50b8oPbvPSLsesOykjvX0tt6PmatjYn4RgUlk9/Ee9m03IfjEb8WA1B29QMu iXLMUmwztBAbUSGtwkVr2hEHJt6hQrTlarULs8s+/OpslP8aatRJoYnWjBbL5Ika+gg5 m+CNsDXy3fnLMXI6nP+Rcr1O+ZiCrDwEWzx7wsCRBMC9vBvyk3DdssyzwARRww4BHqWH 1fAQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=QIxAgrxem7dD9J1NGgiij+uTV9YyQBqzT8bMdoC6FbU=; b=nnRmohx1ImSGlm+a1tqEim60B3u5kBfWcJ5YPwlCOSXUeGMC/f+LKLZyxEmWvgd83h HJ9H2CuyZBB2eLQcBNHXnjVyeuItti8Si2duA+E2UQUQcmNV+VhyppyadoiW7PBA2g22 /mSsApNYl6UMmS2YZ24eP0RB7kQdyGxbXv0TZyNfH+UfbiVWejWpougw7FeQhMgoHJmm 4XtLKwOomJTN1pIlRZuPg7iv8JorDGn4Fg2TuAYx5JiKo+XPRzWCXzlfYiInvJrHhH8a uV9a7M2zr4+Yy9GmutcUeQK0FdWmXIKl6BrBKNTHDTsjZux9h2QXH+pfKBxBEoaW3kS0 9G9A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id g7si3174236edu.57.2021.01.28.19.01.54; Thu, 28 Jan 2021 19:02:21 -0800 (PST) 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; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231386AbhA2DBa (ORCPT + 99 others); Thu, 28 Jan 2021 22:01:30 -0500 Received: from helcar.hmeau.com ([216.24.177.18]:55166 "EHLO fornost.hmeau.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231165AbhA2DB3 (ORCPT ); Thu, 28 Jan 2021 22:01:29 -0500 Received: from gwarestrin.arnor.me.apana.org.au ([192.168.103.7]) by fornost.hmeau.com with smtp (Exim 4.92 #5 (Debian)) id 1l5K0y-0000jx-Cv; Fri, 29 Jan 2021 14:00:05 +1100 Received: by gwarestrin.arnor.me.apana.org.au (sSMTP sendmail emulation); Fri, 29 Jan 2021 14:00:04 +1100 Date: Fri, 29 Jan 2021 14:00:04 +1100 From: Herbert Xu To: Stefan Berger Cc: Ard Biesheuvel , Meng Yu , "David S. Miller" , Linux Crypto Mailing List , Zaibo Xu , wangzhou1@hisilicon.com, Linux Kernel Mailing List , Daniele Alessandrelli , Mark Gross , "Khurana, Prabhjot" , "Reshetova, Elena" , Patrick Uiterwijk Subject: Re: [PATCH v7 4/7] crypto: add ecc curve and expose them Message-ID: <20210129030004.GA3463@gondor.apana.org.au> References: <1611299395-675-1-git-send-email-yumeng18@huawei.com> <1611299395-675-5-git-send-email-yumeng18@huawei.com> <20210128050354.GA30874@gondor.apana.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org On Thu, Jan 28, 2021 at 09:49:41PM -0500, Stefan Berger wrote: > > In my patch series I initially had registered the akciphers under the names > ecc-nist-p192 and ecc-nist-p256 but now, in V4, joined them together as > 'ecdsa'. This may be too generic for a name. Maybe it should be called > ecsda-nist for the NIST family. What I'm proposing is specifying the curve in the name as well, i.e., ecdsa-nist-p192 instead of just ecdsa or ecdsa-nist. This simplifies the task of handling hardware that only supports a subset of curves. There is a parallel discussion of exactly what curves we should support in the kernel. Personally if there is a user in the kernel for it then I'm happy to see it added. In your specific case, as long as your use of the algorithm in x509 is accepted then I don't have any problems with adding support in the Crypto API. Cheers, -- Email: Herbert Xu Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt