From: "Gary Lin" <glin@suse.com>
To: devel@edk2.groups.io, lersek@redhat.com
Cc: xiaoyux.lu@intel.com, Jian J Wang <jian.j.wang@intel.com>,
Ting Ye <ting.ye@intel.com>
Subject: Re: [edk2-devel] [PATCH v3 0/6] CryptoPkg: Upgrade OpenSSL to 1.1.1b
Date: Tue, 14 May 2019 14:16:30 +0800 [thread overview]
Message-ID: <20190514061630.GC23588@GaryWorkstation> (raw)
In-Reply-To: <d0e9102a-4b90-9277-532a-36df98f3b8e4@redhat.com>
On Mon, May 13, 2019 at 09:24:39PM +0200, Laszlo Ersek wrote:
> On 05/13/19 15:25, Xiaoyu lu wrote:
> > (1) CryptoPkg/OpensslLib: Modify process_files.pl for upgrading OpenSSL
> > OpenSSL only support seeding NONE for UEFI(rand_unix.c line 93).
> > So add --with-rand-seed=none to process_files.pl.
> >
> > (2) CryptoPkg/OpensslLib: Exclude unnecessary files in process_files.pl
> > When running process_files.py to configure OpenSSL, we can exclude some unnecessary files. This can reduce porting time, compiling time and library size.
> >
> > (3) CryptoPkg/IntrinsicLib: Fix possible unresolved external symbol issue
> >
> > (4) CryptoPkg/OpensslLib: Prepare for upgrading OpenSSL
> > Disable warning for building OpenSSL_1_1_1b
> >
> > (5) CryptoPkg: Upgrade OpenSSL to 1.1.1b
> > Update OpenSSL submodule to OpenSSL_1_1_1b
> > OpenSSL_1_1_1b(50eaac9f3337667259de725451f201e784599687)
> >
> > OpenSSL doesn't implement some rand_pool function for UEFI.
> > Use EFI_RNG_PROTOCOL to generate random for entropy.
> > If EFI_RNG_PROTOCOL is not avaliable, fall back to performance
> > counter, but we not sure about the amount of randomness it provides.
> >
> > (6) CryptoPkg/BaseCryptLib: Make HMAC_CTX size backward compatible
> >
> > Note: Will be remove next update.
> > Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=1792
> > Ref: https://github.com/openssl/openssl/pull/4338
> >
> >
> > Cc: Jian J Wang <jian.j.wang@intel.com>
> > Cc: Ting Ye <ting.ye@intel.com>
>
> I'm withdrawing from reviewing or testing this series.
>
> Gary, if you have the time, can you please regression test this (for
> HTTPS boot) in both OVMF and ArmVirtQemu?
>
I'll find some time to do the regression test tomorrorw.
Cheers,
Gary Lin
next prev parent reply other threads:[~2019-05-14 6:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 13:25 [PATCH v3 0/6] CryptoPkg: Upgrade OpenSSL to 1.1.1b Xiaoyu lu
2019-05-13 13:25 ` [PATCH v3 1/6] CryptoPkg/OpensslLib: Modify process_files.pl for upgrading OpenSSL Xiaoyu lu
2019-05-13 13:25 ` [PATCH v3 2/6] CryptoPkg/OpensslLib: Exclude unnecessary files in process_files.pl Xiaoyu lu
2019-05-13 13:25 ` [PATCH v3 3/6] CryptoPkg/IntrinsicLib: Fix possible unresolved external symbol issue Xiaoyu lu
2019-05-13 13:25 ` [PATCH v3 4/6] CryptoPkg/OpensslLib: Prepare for upgrading OpenSSL Xiaoyu lu
2019-05-13 13:25 ` [PATCH v3 5/6] CryptoPkg: Upgrade OpenSSL to 1.1.1b Xiaoyu lu
2019-05-13 13:25 ` [PATCH v3 6/6] CryptoPkg/BaseCryptLib: Make HMAC_CTX size backward compatible Xiaoyu lu
2019-05-13 19:24 ` [edk2-devel] [PATCH v3 0/6] CryptoPkg: Upgrade OpenSSL to 1.1.1b Laszlo Ersek
2019-05-14 6:16 ` Gary Lin [this message]
2019-05-14 12:06 ` Laszlo Ersek
2019-05-14 13:26 ` Wang, Jian J
2019-05-15 1:53 ` Gary Lin
2019-05-15 2:00 ` Xiaoyu lu
2019-05-15 4:33 ` Gary Lin
2019-05-15 8:06 ` Laszlo Ersek
2019-05-15 8:58 ` Xiaoyu lu
2019-05-14 11:58 ` Laszlo Ersek
2019-05-14 15:52 ` Xiaoyu lu
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=20190514061630.GC23588@GaryWorkstation \
--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