From: "Sukerkar, Amol N" <amol.n.sukerkar@intel.com>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Yao, Jiewen" <jiewen.yao@intel.com>,
"Wang, Jian J" <jian.j.wang@intel.com>,
"Agrawal, Sachin" <sachin.agrawal@intel.com>,
"Gao, Liming" <liming.gao@intel.com>,
"Sukerkar, Amol N" <amol.n.sukerkar@intel.com>
Subject: Re: [edk2-devel] [PATCH v3 0/2] Enhancement and Fixes to BaseHashApiLib
Date: Sat, 15 Feb 2020 00:11:38 +0000 [thread overview]
Message-ID: <SN6PR11MB2893429C53C15CD799ACE338AC140@SN6PR11MB2893.namprd11.prod.outlook.com> (raw)
In-Reply-To: <E92EE9817A31E24EB0585FDF735412F5B9EBA745@ORSMSX113.amr.corp.intel.com>
Hi Mike,
Although the values were listed in 8-digit hex format, the PCD, PcdHashApiLibPolicy itself was of type UINT8 earlier that was changed to UINT16. I agree changing the type to UINT32 will align with all the other PCDs implementing TCG spec (and using Tpm20.h defines). Can you confirm my understanding is accurate?
Thanks,
Amol
-----Original Message-----
From: Kinney, Michael D <michael.d.kinney@intel.com>
Sent: Friday, February 14, 2020 5:04 PM
To: devel@edk2.groups.io; Sukerkar, Amol N <amol.n.sukerkar@intel.com>; Kinney, Michael D <michael.d.kinney@intel.com>
Cc: Yao, Jiewen <jiewen.yao@intel.com>; Wang, Jian J <jian.j.wang@intel.com>; Agrawal, Sachin <sachin.agrawal@intel.com>; Gao, Liming <liming.gao@intel.com>
Subject: RE: [edk2-devel] [PATCH v3 0/2] Enhancement and Fixes to BaseHashApiLib
Amol,
Thanks for the quick update.
I see you changed the PCD to type UINT16. I think this was based on Jiewen feedback to use a set of TPM specific algorithms defines that were UINT16.
However, the HASH define values being used are 32-bits and everywhere else that those defines values are used, they are also 32-bits.
I recommend we keep the type UINT32, and use 8 digit hex values in all references to the values and valid value checks.
Thanks,
Mike
> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of
> Sukerkar, Amol N
> Sent: Friday, February 14, 2020 3:21 PM
> To: devel@edk2.groups.io
> Cc: Kinney, Michael D <michael.d.kinney@intel.com>; Yao, Jiewen
> <jiewen.yao@intel.com>; Wang, Jian J <jian.j.wang@intel.com>; Agrawal,
> Sachin <sachin.agrawal@intel.com>; Gao, Liming <liming.gao@intel.com>
> Subject: [edk2-devel] [PATCH v3 0/2] Enhancement and Fixes to
> BaseHashApiLib
>
> This patch implements the fixes and enhancement to BaseHashApiLib in
> the following manner:
> - Remove reference to MD4 and MD5 hashing algorithms as they are
> deprecated;
> - Align the enumeration for hashing algorithmswith the one used in
> TPM 2.0 implementation defined in
> IndustryStandard/Tpm20.h;
> - Change the type of PcdHashApiLibPolicy to PcdsFixedAtBuild to
> optimize away the unused hashing algorithms for a particular
> instance of HashApiLib.
>
> More information can be found at Bugzilla ticket,
> https://bugzilla.tianocore.org/show_bug.cgi?id=2511.
>
> Amol N Sukerkar (2):
> CryptoPkg/BaseHashApiLib: Align BaseHashApiLib with TPM 2.0
> Implementation
> CryptoPkg/BaseHashApiLib: Change PcdHashApiLibPolicy type to
> FixedAtBuild
>
> CryptoPkg/Library/BaseHashApiLib/BaseHashApiLib.c |
> 121 ++++++--------------
> CryptoPkg/CryptoPkg.dec |
> 18 ++-
> CryptoPkg/CryptoPkg.uni |
> 12 +-
> CryptoPkg/Include/Library/HashApiLib.h |
> 16 +--
> 4 files changed, 52 insertions(+), 115 deletions(-)
>
> --
> 2.16.2.windows.1
>
>
>
next prev parent reply other threads:[~2020-02-15 0:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 23:20 [PATCH v3 0/2] Enhancement and Fixes to BaseHashApiLib Sukerkar, Amol N
2020-02-14 23:20 ` [PATCH v3 1/2] CryptoPkg/BaseHashApiLib: Align BaseHashApiLib with TPM 2.0 Implementation Sukerkar, Amol N
2020-02-14 23:21 ` [PATCH v3 2/2] CryptoPkg/BaseHashApiLib: Change PcdHashApiLibPolicy type to FixedAtBuild Sukerkar, Amol N
2020-02-15 0:04 ` [edk2-devel] [PATCH v3 0/2] Enhancement and Fixes to BaseHashApiLib Michael D Kinney
2020-02-15 0:11 ` Sukerkar, Amol N [this message]
2020-02-15 0:13 ` Michael D Kinney
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=SN6PR11MB2893429C53C15CD799ACE338AC140@SN6PR11MB2893.namprd11.prod.outlook.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