Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <1bcf580b-3a19-c0aa-b3cb-1f9f183b61e4@huawei.com>
Date:   Fri, 11 Aug 2023 11:25:27 +0800
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PATCH RFC v3 3/3] crypto: Introduce SM9 key exchange algorithm
Content-Language: en-US
To:     Herbert Xu <herbert@gondor.apana.org.au>
CC:     <davem@davemloft.net>, <linux-crypto@vger.kernel.org>
References: <20230625014958.32631-1-guozihua@huawei.com>
 <20230625014958.32631-4-guozihua@huawei.com>
 <ZLD+9pRFQdSpfMog@gondor.apana.org.au>
From:   "Guozihua (Scott)" <guozihua@huawei.com>
In-Reply-To: <ZLD+9pRFQdSpfMog@gondor.apana.org.au>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 2023/7/14 15:53, Herbert Xu wrote:
> On Sun, Jun 25, 2023 at 09:49:58AM +0800, GUO Zihua wrote:
>> This patch introduces a generic implementation of SM9 (ShangMi 9) key
>> exchange algorithm.
>>
>> SM9 is an ID-based cryptography algorithm within the ShangMi family whose
>> key exchange algorithm was accepted in ISO/IEC 11770-3 as an
>> international standard.
> 
> For each new algorithm we require an in-kernel user.  Where is the
> in-kernel user for this?
> 
> Thanks,
Hi Herbert,

Unfortunately we don't have such usage right now and we are researching
into it.

Just while we are here, do you think it's a good idea to also introduce
a new crypto algorithm type for IBCs to better support their
functionality if there are usage within kernel and we are to port this
algorithm in?

-- 
Best
GUO Zihua