public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Judah Vang" <judah.vang@intel.com>
To: devel@edk2.groups.io
Subject: [PATCH V1 0/2] CryptoPkg bug fixes
Date: Mon, 24 Oct 2022 09:41:37 -0700	[thread overview]
Message-ID: <20221024164139.792-1-judah.vang@intel.com> (raw)

https://bugzilla.tianocore.org/show_bug.cgi?id=3991
https://bugzilla.tianocore.org/show_bug.cgi?id=3992

There is a #define to deprecate Sha1 functions but not
all the Sha1 function are wrapped around this #define causing
a build error. The fix is to wrap all Sha1 functions with
the #define.

Need crypto AES to be supported for PEI phase and need
crypto KDF to be supported for SMM phase.

Judah Vang (2):
  CryptoPkg: Sha1 functions causing build errors
  CryptoPkg: Need to enable crypto functions

 CryptoPkg/Library/BaseCryptLib/PeiCryptLib.inf    |  2 +-
 CryptoPkg/Library/BaseCryptLib/SmmCryptLib.inf    |  2 +-
 CryptoPkg/Library/BaseHashApiLib/BaseHashApiLib.c | 14 +++++++++++++-
 3 files changed, 15 insertions(+), 3 deletions(-)

-- 
2.35.1.windows.2


             reply	other threads:[~2022-10-24 16:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-24 16:41 Judah Vang [this message]
2022-10-24 16:41 ` [PATCH V1 1/2] CryptoPkg: Sha1 functions causing build errors Judah Vang
2022-10-24 16:41 ` [PATCH V1 2/2] CryptoPkg: Need to enable crypto functions Judah Vang
2022-10-24 17:21 ` [edk2-devel] [PATCH V1 0/2] CryptoPkg bug fixes Michael D Kinney
2022-10-26 18:41   ` Judah Vang
2022-10-26 21:16     ` Michael D Kinney
2022-10-28 23:25       ` Judah Vang
2022-11-07 18:41   ` Judah Vang
2022-12-20  2:43   ` 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=20221024164139.792-1-judah.vang@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