<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style></style> </head> <body lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word"> <div class="WordSection1"> Hello<o:p></o:p> I would like to give a proposal for the openssl 1.1 replacement in EDKII community.<o:p></o:p> <o:p> </o:p> [Problem Statement]<o:p></o:p> Openssl 1.1 is about to EOL at September, 2023. We need find replacement.<o:p></o:p> <o:p> </o:p> Bugzilla:<o:p></o:p> 1. Openssl3.0: <a href="https://bugzilla.tianocore.org/show_bug.cgi?id=3466"> https://bugzilla.tianocore.org/show_bug.cgi?id=3466</a><o:p></o:p> 2. MbedTls: <a href="https://bugzilla.tianocore.org/show_bug.cgi?id=4177"> https://bugzilla.tianocore.org/show_bug.cgi?id=4177</a><o:p></o:p> <o:p> </o:p> [POC result]<o:p></o:p> 1. The natural successor is Openssl 3.0.<o:p></o:p> However, it brings size issue according to the POC evaluation - <a href="https://edk2.groups.io/g/devel/topic/87479913">https://edk2.groups.io/g/devel/topic/87479913</a>.<o:p></o:p> The concern is that: The size of flash is fixed. If we naīve replace it directly, the existing platforms may be broken immediately.<o:p></o:p> <o:p> </o:p> 2. The alternative is MbedTls, which is much smaller.<o:p></o:p> However, there is feature gap, e.g. PKCS7 is not there.<o:p></o:p> <o:p> </o:p> 3. At same time, we evaluated other crypto library.<o:p></o:p> A. Intel-IPP: <a href="https://software.intel.com/en-us/intel-ipp"> https://software.intel.com/en-us/intel-ipp</a> , <a href="https://github.com/intel/ipp-crypto"> https://github.com/intel/ipp-crypto</a> (Apache license) - CON: Only crypto primitive, no certificate, no TLS<o:p></o:p> B. Libsodium: <a href="https://doc.libsodium.org/">https://doc.libsodium.org/</a>, <a href="https://github.com/jedisct1/libsodium">https://github.com/jedisct1/libsodium</a> (ISC license) - CON: Only crypto primitive, no certificate, no TLS<o:p></o:p> C: BoringSSL: <a href="https://github.com/google/boringssl"> https://github.com/google/boringssl</a> (ISC license) – CON: Google only project. It says: “We don't recommend that third parties depend upon it.”<o:p></o:p> D: WolfSSL: <a href="https://www.wolfssl.com/">https://www.wolfssl.com/</a>, <a href="https://github.com/wolfSSL/wolfssl">https://github.com/wolfSSL/wolfssl</a> (GPL license) - CON: GPL License issue.<o:p></o:p> E: BearSSL: <a href="https://bearssl.org/">https://bearssl.org/</a> (MIT license) – CON: Current version is 0.6. It is now considered beta-quality software.<o:p></o:p> <o:p> </o:p> [Proposal]<o:p></o:p> 1. Let’s put *Openssl 3.0 POC* to *edk2-staging*, and continue the research on how to reduce the size.<o:p></o:p> It is possible that we may need add MACRO to Openssl 3.0 to reduce the size. We can do POC and submit to openssl community.<o:p></o:p> <o:p> </o:p> 2. Let’s put *MbedTls POC* to *edk2-staging*, and continue the research on how to add missing features.<o:p></o:p> <o:p> </o:p> 3. If 1 or 2 can success, we can replace openssl 1.1 with one crypto lib.<o:p></o:p> If both 1 and 2 fail, we may use *dual-crypto module*. For example: mbedtls for PEI and openssl3.0 for DXE.<o:p></o:p> The source code size will become larger, more time to download the tree.<o:p></o:p> <o:p> </o:p> 4. We need control the quality of Openssl 1.1 replacement to avoid regression.<o:p></o:p> I propose the check-in criteria below:<o:p></o:p> A) Size delta < +10%<o:p></o:p> B) No API change.<o:p></o:p> C) All existing crypto usages in EDKII are covered, including:<o:p></o:p> UEFI Secure Boot - image verification/auth variable update (PKCS7)<o:p></o:p> TCG Trusted Boot (SHA2/SM3)<o:p></o:p> UEFI/PI FMP Capsule (PKCS7/PKCS1-v1.5-RSA)<o:p></o:p> HTTPs Boot (TLS 1.2/1.3)<o:p></o:p> BIOS Password (PKCS5-PBKDF)<o:p></o:p> iSCSI (SHA2)<o:p></o:p> HDD Password (SHA2)<o:p></o:p> Hash2Dxe (SHA2)<o:p></o:p> Pkcs7Verify (PKCS7)<o:p></o:p> D) All crypto APIs in EDKII are covered besides above use case, including:<o:p></o:p> SHA3-ParallelHash<o:p></o:p> HMAC/HKDF<o:p></o:p> ECC<o:p></o:p> E) All crypto test need pass.<o:p></o:p> <o:p> </o:p> Please review and provide your feedback. <o:p></o:p> <o:p> </o:p> <o:p> </o:p> [Misc]<o:p></o:p> I would like to clarify my position on the original openssl 3.0 path, to avoid the misunderstanding:<o:p></o:p> A) I never expressed a desire to retain the OpenSSL 1.1. (I am sorry, if I did not say that clearly.)<o:p></o:p> B) I raised the concern that *current OpenSSL 3.0 patch requires more improvement*, because it will increase the size and break the existing platform.<o:p></o:p> It has no difference with other comment I give in the EDKII. If we want to check in, we need resolve the concern and ensure it can still work with existing platform.<o:p></o:p> <o:p> </o:p> <o:p> </o:p> Last but not least, I would like to suggest *again* that we maintain *a civil and healthy community environment*. (Thanks, Ard)<o:p></o:p> NOTE: All EDKII maintainers are doing volunteer work here. We are using development mailing list. Let’s focus on technical topic.<o:p></o:p> If anyone has any constructive technical idea, feel free to express your opinion, and we are happy to listen and discuss.<o:p></o:p> Any collaboration, patch submission, and validation are more than welcome.<o:p></o:p> <o:p> </o:p> This is not a small work. We need all EDK-II community people’s help to deal with this OpenSSL 1.1 EOL.<o:p></o:p> <o:p> </o:p> Thank you<o:p></o:p> Yao, Jiewen<o:p></o:p> <o:p> </o:p> </div> </body> </html> <div width="1" style="color:white;clear:both">_._,_._,_</div> <hr> Groups.io Links: You receive all messages sent to this group. <a target="_blank" href="https://edk2.groups.io/g/devel/message/99638">View/Reply Online (#99638)</a> | | <a target="_blank" href="https://groups.io/mt/96741156/1813853">Mute This Topic</a> | <a href="https://edk2.groups.io/g/devel/post">New Topic</a> <a href="https://edk2.groups.io/g/devel/editsub/1813853">Your Subscription</a> | <a href="mailto:devel+owner@edk2.groups.io">Contact Group Owner</a> | <a href="https://edk2.groups.io/g/devel/unsub">Unsubscribe</a> [edk2-devel-archive@redhat.com] <div width="1" style="color:white;clear:both">_._,_._,_</div>