public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Wang, Jian J" <jian.j.wang@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"Desai, Imran" <imran.desai@intel.com>
Subject: Re: [edk2-devel] [PATCH v2 3/5] SecurityPkg/HashLibBaseCryptoRouter: recognize the SM3 digest algorithm
Date: Fri, 7 Jun 2019 22:18:15 +0000	[thread overview]
Message-ID: <D827630B58408649ACB04F44C5100036259122BB@SHSMSX107.ccr.corp.intel.com> (raw)
In-Reply-To: <20190528204049.86463-4-imran.desai@intel.com>


Reviewed-by: Jian J Wang <jian.j.wang@intel.com>


> -----Original Message-----
> From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of Imran
> Desai
> Sent: Wednesday, May 29, 2019 4:41 AM
> To: devel@edk2.groups.io
> Subject: [edk2-devel] [PATCH v2 3/5] SecurityPkg/HashLibBaseCryptoRouter:
> recognize the SM3 digest algorithm
> 
> 
> BZ: https://bugzilla.tianocore.org/show_bug.cgi?id=1781
> 
> EDK2 Support for SM3 digest algorithm is needed to enable TPM with SM3 PCR
> banks. This digest algorithm is part of the China Crypto algorithm suite.
> This integration has dependency on the openssl_1_1_1b integration into
> edk2.
> This patch adds SM3 as an available digest algorithm to crypto router.
> 
> 
> Signed-off-by: Imran Desai <imran.desai@intel.com>
> Cc: Chao Zhang <chao.b.zhang@intel.com>
> Cc: Jiewen Yao <jiewen.yao@intel.com>
> Cc: Jian Wang <jian.j.wang@intel.com>
> ---
> 
> SecurityPkg/Library/HashLibBaseCryptoRouter/HashLibBaseCryptoRouterComm
> on.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git
> a/SecurityPkg/Library/HashLibBaseCryptoRouter/HashLibBaseCryptoRouterCom
> mon.c
> b/SecurityPkg/Library/HashLibBaseCryptoRouter/HashLibBaseCryptoRouterCom
> mon.c
> index 7f3bdab53066..aec874a9e072 100644
> ---
> a/SecurityPkg/Library/HashLibBaseCryptoRouter/HashLibBaseCryptoRouterCom
> mon.c
> +++
> b/SecurityPkg/Library/HashLibBaseCryptoRouter/HashLibBaseCryptoRouterCom
> mon.c
> @@ -25,6 +25,7 @@ TPM2_HASH_MASK mTpm2HashMask[] = {
>    {HASH_ALGORITHM_SHA256_GUID,       HASH_ALG_SHA256},
>    {HASH_ALGORITHM_SHA384_GUID,       HASH_ALG_SHA384},
>    {HASH_ALGORITHM_SHA512_GUID,       HASH_ALG_SHA512},
> +  {HASH_ALGORITHM_SM3_256_GUID,      HASH_ALG_SM3_256},
>  };
> 
>  /**
> --
> 2.17.0
> 
> 
> 


  reply	other threads:[~2019-06-07 22:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-28 20:40 [PATCH v2 0/5] Implement SM3 measured boot Imran Desai
2019-05-28 20:40 ` [PATCH v2 1/5] MdePkg/Protocol/Hash: introduce GUID for SM3 Imran Desai
2019-05-28 20:40 ` [PATCH v2 2/5] SecurityPkg: introduce the SM3 digest algorithm Imran Desai
2019-06-07 22:17   ` [edk2-devel] " Wang, Jian J
2019-05-28 20:40 ` [PATCH v2 3/5] SecurityPkg/HashLibBaseCryptoRouter: recognize " Imran Desai
2019-06-07 22:18   ` Wang, Jian J [this message]
2019-05-28 20:40 ` [PATCH v2 4/5] SecurityPkg: set SM3 bit in TPM 2.0 hash mask by default Imran Desai
2019-06-07 22:19   ` [edk2-devel] " Wang, Jian J
2019-05-28 20:40 ` [PATCH v2 5/5] OvmfPkg: link SM3 support into Tcg2Pei and Tcg2Dxe Imran Desai
2019-07-03 20:37   ` [edk2-devel] " Laszlo Ersek
2019-07-03 21:18     ` Leif Lindholm
2019-07-03 22:48       ` Imran Desai
2019-07-04  8:30         ` Laszlo Ersek
2019-07-05  3:02     ` Wang, Jian J
2019-05-30  4:55 ` [edk2-devel] [PATCH v2 0/5] Implement SM3 measured boot Wang, Jian J

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-list 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=D827630B58408649ACB04F44C5100036259122BB@SHSMSX107.ccr.corp.intel.com \
    --to=devel@edk2.groups.io \
    /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