linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tianjia Zhang <tianjia.zhang@linux.alibaba.com>
To: herbert@gondor.apana.org.au, davem@davemloft.net,
	ebiggers@kernel.org, pvanleeuwen@rambus.com, zohar@linux.ibm.com,
	dmitry.kasatkin@intel.com, penguin-kernel@I-love.SAKURA.ne.jp,
	jmorris@namei.org, rusty@rustcorp.com.au, nicstange@gmail.com,
	tadeusz.struk@intel.com, gilad@benyossef.com
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Introduce OSCCA certificate and SM2 asymmetric algorithm
Date: Mon, 2 Mar 2020 14:27:53 +0800	[thread overview]
Message-ID: <b48a70cf-8f3d-011c-275e-0c508ca212f5@linux.alibaba.com> (raw)
In-Reply-To: <20200216085928.108838-1-tianjia.zhang@linux.alibaba.com>



On 2020/2/16 16:59, 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.
> 
> The sm2 algorithm is based on libgcrypt's mpi implementation, and has
> made some additions to the kernel's original mpi library, and added the
> implementation of ec to better support elliptic curve-like algorithms.
> 
> sm2 has good support in both openssl and gnupg projects, and sm3 and sm4
> of the OSCCA algorithm family have also been implemented in the kernel.
> 
> Signed-off-by: Tianjia Zhang <tianjia.zhang@linux.alibaba.com>
> 
> Thanks,
> Tianjia
> 

Hello all,

This is the review request.

The OSCCA certificate and related algorithms used to verify the 
certificate are newly introduced. Among them, sm3 and sm4 have been well 
implemented in the kernel. This group of patches has newly introduced sm2.
In order to implement sm2 more perfectly, I expanded the mpi library and 
introduced the ec implementation of the mpi library as the basic 
algorithm. Compared to the kernel's crypto/ecc.c, the implementation of 
mpi/ec.c is more complete and elegant, sm2 is implemented based on these 
algorithms.
At this point, the kernel can parse and verify sm2-with-sm3 certificates 
normally.

Thanks,
Tianjia

      parent reply	other threads:[~2020-03-02  6:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-16  8:59 [PATCH] Introduce OSCCA certificate and SM2 asymmetric algorithm Tianjia Zhang
2020-02-16  8:59 ` [PATCH 1/7] lib/mpi: Extend the MPI library Tianjia Zhang
2020-02-16  8:59 ` [PATCH 2/7] lib/mpi: Introduce ec implementation to " Tianjia Zhang
2020-02-16  8:59 ` [PATCH 3/7] crypto: sm2 - introduce OSCCA SM2 asymmetric cipher algorithm Tianjia Zhang
2020-02-16  8:59 ` [PATCH 4/7] crypto: testmgr - support test with different ciphertext per encryption Tianjia Zhang
2020-02-16  8:59 ` [PATCH 5/7] crypto: testmgr - Add SM2 test vectors Tianjia Zhang
2020-02-16  8:59 ` [PATCH 6/7] X.509: support OSCCA certificate parse Tianjia Zhang
2020-02-16  8:59 ` [PATCH 7/7] X.509: support OSCCA sm2-with-sm3 certificate verification Tianjia Zhang
2020-03-17  6:31   ` Gilad Ben-Yossef
2020-03-17  6:50     ` Tianjia Zhang
2020-03-02  6:27 ` Tianjia Zhang [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b48a70cf-8f3d-011c-275e-0c508ca212f5@linux.alibaba.com \
    --to=tianjia.zhang@linux.alibaba.com \
    --cc=davem@davemloft.net \
    --cc=dmitry.kasatkin@intel.com \
    --cc=ebiggers@kernel.org \
    --cc=gilad@benyossef.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=jmorris@namei.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicstange@gmail.com \
    --cc=penguin-kernel@I-love.SAKURA.ne.jp \
    --cc=pvanleeuwen@rambus.com \
    --cc=rusty@rustcorp.com.au \
    --cc=tadeusz.struk@intel.com \
    --cc=zohar@linux.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).