From: "Gerd Hoffmann" <kraxel@redhat.com>
To: devel@edk2.groups.io, jiewen.yao@intel.com
Subject: Re: [edk2-devel] [RFC] [staging/CryptoLibrary] Openssl1.1 replacement proposal
Date: Wed, 8 Feb 2023 12:45:06 +0100 [thread overview]
Message-ID: <20230208114506.otktqepwuapbxgf6@sirius.home.kraxel.org> (raw)
In-Reply-To: <MW4PR11MB58721619F00F0D9E3D47F7698CD49@MW4PR11MB5872.namprd11.prod.outlook.com>
Hi,
> 3. If 1 or 2 can success, we can replace openssl 1.1 with one crypto lib.
> If both 1 and 2 fail, we may use *dual-crypto module*. For example: mbedtls for PEI and openssl3.0 for DXE.
> The source code size will become larger, more time to download the tree.
Suggestions how to do that best, ideally without duplicating CryptoPkg
for that?
A while back I've tried to add openssl-3 in parallel to openssl-11,
with the idea to allow projects picking the one or the other, and quicky
ran into problems because apparently libraries can't add include
directories. Only packages can do that (see Includes.Common.Private in
CryptoPkg/CryptoPkg.dec which adds Library/OpensslLib/openssl/include).
take care,
Gerd
next prev parent reply other threads:[~2023-02-08 11:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <MW4PR11MB58723F4FCC357DCDADBFEE238CD49@MW4PR11MB5872.namprd11.prod.outlook.com>
2023-02-04 9:25 ` [RFC] [staging/CryptoLibrary] Openssl1.1 replacement proposal Yao, Jiewen
2023-02-04 16:04 ` [edk2-devel] " Marvin Häuser
2023-02-08 11:45 ` Gerd Hoffmann [this message]
2023-02-09 3:21 ` Yao, Jiewen
[not found] ` <174209E894D5CF7F.15261@groups.io>
2023-02-11 2:20 ` Yao, Jiewen
[not found] ` <1742A3BAD41DE0F1.13814@groups.io>
2023-03-10 12:28 ` Yao, Jiewen
2023-03-10 15:50 ` Gerd Hoffmann
2023-03-10 16:06 ` Yao, Jiewen
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=20230208114506.otktqepwuapbxgf6@sirius.home.kraxel.org \
--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