Received: by 2002:a25:1985:0:0:0:0:0 with SMTP id 127csp942731ybz; Wed, 15 Apr 2020 23:04:40 -0700 (PDT) X-Google-Smtp-Source: APiQypKCs6rl+h4e9JZeiTGBOF5C8rhlUqeBYwU+btW4hzZ2dFZPjMF568iPnWreDJrVSm/pTb5N X-Received: by 2002:a50:ee86:: with SMTP id f6mr14066375edr.123.1587017080374; Wed, 15 Apr 2020 23:04:40 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1587017080; cv=none; d=google.com; s=arc-20160816; b=qqvH0J+kbycdqjIkwmj5X+ZxhmhkpRbVxIEZjNV5q2pP6UdjZzE7qU65+8VQH3fevv /ce+cxTTlRYArytB3C7lpRPGhj1y17jAfmHfMHM7zpBEvGmeSCci0eq2kmwN3F6KGdqL BDqesqpE0FoDf5cxCCAkEfQnyh5BbiMbupg95PKWjbo+uq7eQQD5g558bHV7N7EcuKzq +3Q7htm9TcUHjPMruhTJX5VVIlN2uF/CFP6i5i0+5nt2Kr3gdzdFSvdKnrhvyYm7IcIk lRBsIPNuEldeHguga0cVJMGvOB0Wien1fi0dNg+XYCt0uM2UkHbJ6oxRMJlXe3vWq/1H J1Aw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=UPjIpGbsBO8tEhS1kBUzqL5IT5xIRqb5JX4DRKfiymw=; b=anKEMEoLHTHWSLdfA59zrc+QUG7V4O1yIjLdVUqiVOAOYUdNxtxVM2N3ywkn+lGik4 togO/y8SFNzTZIeUhgFAGrPkZetQgSXXApQ6Dcekod7DdY5KmBuBMMQIQAOVKFgGLwgW RdcR9CuoNRbSSrnq5SiQTmOC9PWavg4F68YYxcUtKLnCgmxL9YboJwfe5zUGEXgTwUEX 3U3F1CTVXQ6RzDQnH9Q4hm0Ph15y8NRlhoBB8wTuqwcB0SkiV9NaT3DgfhWIJ5ICUu8Y A6QouecfFAQXtFIiNRY/wPsm5gaGa9awuHL/S9b3QD0ydbPyeUp1C30YRwJkDpS6DFFu U4sQ== 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 oh24si11317822ejb.531.2020.04.15.23.04.06; Wed, 15 Apr 2020 23:04:40 -0700 (PDT) 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 S2407272AbgDPGDE (ORCPT + 99 others); Thu, 16 Apr 2020 02:03:04 -0400 Received: from helcar.hmeau.com ([216.24.177.18]:41096 "EHLO fornost.hmeau.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2407219AbgDPGDD (ORCPT ); Thu, 16 Apr 2020 02:03:03 -0400 Received: from gwarestrin.me.apana.org.au ([192.168.0.7] helo=gwarestrin.arnor.me.apana.org.au) by fornost.hmeau.com with smtp (Exim 4.89 #2 (Debian)) id 1jOxai-0004JT-Ro; Thu, 16 Apr 2020 16:01:37 +1000 Received: by gwarestrin.arnor.me.apana.org.au (sSMTP sendmail emulation); Thu, 16 Apr 2020 16:01:36 +1000 Date: Thu, 16 Apr 2020 16:01:36 +1000 From: Herbert Xu To: Tianjia Zhang Cc: davem@davemloft.net, ebiggers@kernel.org, ebiggers@google.com, pvanleeuwen@rambus.com, zohar@linux.ibm.com, gilad@benyossef.com, jarkko.sakkinen@linux.intel.com, dmitry.kasatkin@intel.com, nicstange@gmail.com, tadeusz.struk@intel.com, jmorris@namei.org, serge@hallyn.com, zhang.jia@linux.alibaba.com, linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 0/7] crpyto: introduce OSCCA certificate and SM2 asymmetric algorithm Message-ID: <20200416060136.GA19149@gondor.apana.org.au> References: <20200402123504.84628-1-tianjia.zhang@linux.alibaba.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200402123504.84628-1-tianjia.zhang@linux.alibaba.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-crypto-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org On Thu, Apr 02, 2020 at 08:34:57PM +0800, Tianjia Zhang wrote: > Hello all, > > This new module implement the OSCCA certificate and SM2 public key > algorithm. It was published by State Encryption Management Bureau, China. > List of specifications for OSCCA certificate and SM2 elliptic curve > public key cryptography: > > * GM/T 0003.1-2012 > * GM/T 0003.2-2012 > * GM/T 0003.3-2012 > * GM/T 0003.4-2012 > * GM/T 0003.5-2012 > * GM/T 0015-2012 > * GM/T 0009-2012 > > IETF: https://tools.ietf.org/html/draft-shen-sm2-ecdsa-02 > oscca: http://www.oscca.gov.cn/sca/xxgk/2010-12/17/content_1002386.shtml > scctc: http://www.gmbz.org.cn/main/bzlb.html > > These patchs add the OID object identifier defined by OSCCA. The > x509 certificate supports sm2-with-sm3 type certificate parsing > and verification. I don't have any objections to the crypto API bits, but obviously this is contingent on the x509 bits getting accepted since that's the only in-kernel user. So can I see some acks on that please? Thanks, -- Email: Herbert Xu Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt