This is going to be needed in the next 6 months because OpenSSL 1.1.1 is
going EOL.
From https://www.openssl.org/blog/blog/2023/03/28/1.1.1-EOL/ :
"We are now less than 6 months away from the End Of Life (EOL) date for
the OpenSSL 1.1.1 series. Users of OpenSSL 1.1.1 should consider their
The current purpose of this POC is to find all ways to reduce the size increase
as much as possible to meet our goal of +10% size increase.
I understand that the current code changes seem unacceptable, and the next step
of the POC is to find a suitable way to apply these changes (some breaking
Hi Gerd
Currently, the *blocking issue* for openssl 3.0 adoption in EDKII is *size*.
The big size increase will break exist platforms easily. As such, we are not
able to switch to openssl 3.0 directly.
I have written the proposal at
On Fri, Mar 17, 2023 at 12:28:12PM +0800, Yi Li wrote:
> Please check the patch series if interested.
> PR: https://github.com/tianocore/edk2-staging/pull/359
So it seems you are doing a number of larger changes to the openssl
code base. What is the plan for those?
I'd prefer to not be in a
Please check the patch series if interested.
PR: https://github.com/tianocore/edk2-staging/pull/359
Latest size data:
Binaries:
CryptoDxeFull -> 1.7%17KB (New)
CryptoDxe 14% -> 10.10% 82KB
CryptoSmm
