From: "Heng Luo" <heng.luo@intel.com>
To: "Li, Yi1" <yi1.li@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Gao, Zhichao" <zhichao.gao@intel.com>, "Tan, Ming" <ming.tan@intel.com>
Subject: Re: [edk2-staging][PATCH 1/2] CryptoPkg: update openssl to 1.1.1t
Date: Tue, 28 Feb 2023 08:15:23 +0000 [thread overview]
Message-ID: <SN6PR11MB275214690AD4BFADA4DC18C893AC9@SN6PR11MB2752.namprd11.prod.outlook.com> (raw)
In-Reply-To: <3173762af8de2875991996856347156f0933c382.1677218500.git.yi1.li@intel.com>
Reviewed-by: Heng Luo <heng.luo@intel.com>
> -----Original Message-----
> From: Li, Yi1 <yi1.li@intel.com>
> Sent: Friday, February 24, 2023 2:49 PM
> To: devel@edk2.groups.io
> Cc: Li, Yi1 <yi1.li@intel.com>; Gao, Zhichao <zhichao.gao@intel.com>; Tan,
> Ming <ming.tan@intel.com>; Luo, Heng <heng.luo@intel.com>
> Subject: [edk2-staging][PATCH 1/2] CryptoPkg: update openssl to 1.1.1t
>
> Pick up bugfixes from the latest openssl release.
>
> Cc: Zhichao Gao <zhichao.gao@intel.com>
> Cc: Ming Tan <ming.tan@intel.com>
> Cc: Heng Luo <heng.luo@intel.com>
> Signed-off-by: Yi Li <yi1.li@intel.com>
> ---
> CryptoPkg/Library/OpensslLib/OpensslLib.inf | 1 +
> CryptoPkg/Library/OpensslLib/openssl | 2 +-
> 2 files changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/CryptoPkg/Library/OpensslLib/OpensslLib.inf
> b/CryptoPkg/Library/OpensslLib/OpensslLib.inf
> index 1d67ed55e1..c112b737ba 100644
> --- a/CryptoPkg/Library/OpensslLib/OpensslLib.inf
> +++ b/CryptoPkg/Library/OpensslLib/OpensslLib.inf
> @@ -157,6 +157,7 @@
> $(OPENSSL_PATH)/crypto/bn/bn_srp.c
> $(OPENSSL_PATH)/crypto/bn/bn_word.c
> $(OPENSSL_PATH)/crypto/bn/bn_x931p.c
> + $(OPENSSL_PATH)/crypto/bn/rsa_sup_mul.c
> $(OPENSSL_PATH)/crypto/buffer/buf_err.c
> $(OPENSSL_PATH)/crypto/buffer/buffer.c
> $(OPENSSL_PATH)/crypto/cmac/cm_ameth.c
> diff --git a/CryptoPkg/Library/OpensslLib/openssl
> b/CryptoPkg/Library/OpensslLib/openssl
> index 52c587d60b..830bf8e1e4 160000
> --- a/CryptoPkg/Library/OpensslLib/openssl
> +++ b/CryptoPkg/Library/OpensslLib/openssl
> @@ -1 +1 @@
> -Subproject commit 52c587d60be67c337364b830dd3fdc15404a2f04
> +Subproject commit 830bf8e1e4749ad65c51b6a1d0d769ae689404ba
> --
> 2.31.1.windows.1
next prev parent reply other threads:[~2023-02-28 8:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 6:49 [edk2-staging][PATCH 0/2] CryptoPkg: openssl submodule update Li, Yi
2023-02-24 6:49 ` [edk2-staging][PATCH 1/2] CryptoPkg: update openssl to 1.1.1t Li, Yi
2023-02-28 8:15 ` Heng Luo [this message]
2023-02-24 6:49 ` [edk2-staging][PATCH 2/2] CryptoPkg: fix wrong name in tls 1.2 cipher suite Li, Yi
2023-02-28 8:15 ` Heng Luo
2023-02-28 8:16 ` [edk2-staging][PATCH 0/2] CryptoPkg: openssl submodule update Heng Luo
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=SN6PR11MB275214690AD4BFADA4DC18C893AC9@SN6PR11MB2752.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