From: "Zurcher, Christopher J" <christopher.j.zurcher@intel.com>
To: devel@edk2.groups.io
Cc: Jian J Wang <jian.j.wang@intel.com>, Xiaoyu Lu <xiaoyux.lu@intel.com>
Subject: [PATCH v3 0/2] CryptoPkg/OpensslLib: Remove "no-autoalginit" flag from OpenSSL build
Date: Thu, 13 Feb 2020 16:40:19 -0800 [thread overview]
Message-ID: <20200214004021.17300-1-christopher.j.zurcher@intel.com> (raw)
In order to implement the EVP interface, the EVP_get_digestbyname function
requires the desired digest to be already initialized. Removing the
"no-autoalginit" build option will allow algorithms to be retrieved by name.
I plan to submit a future patch with an EVP implementation; the OpenSSL
documentation has stated that the EVP interface "should almost always be
used" over direct digest interfaces at least as far back as version 0.9.6c.
This patch set also adds the "sort" keyword to the header file parsing loop
so the .inf files aren't randomized after every run of process_files.pl.
Cc: Jian J Wang <jian.j.wang@intel.com>
Cc: Xiaoyu Lu <xiaoyux.lu@intel.com>
Christopher J Zurcher (2):
CryptoPkg/OpensslLib: Add "sort" keyword to header file parsing loop
CryptoPkg/OpensslLib: Remove "no-autoalginit" flag from OpenSSL build
CryptoPkg/Library/OpensslLib/OpensslLib.inf | 66 ++++++++++----------
CryptoPkg/Library/OpensslLib/OpensslLibCrypto.inf | 62 +++++++++---------
CryptoPkg/Library/Include/openssl/opensslconf.h | 3 -
CryptoPkg/Library/OpensslLib/process_files.pl | 5 +-
4 files changed, 66 insertions(+), 70 deletions(-)
--
2.16.2.windows.1
next reply other threads:[~2020-02-14 0:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 0:40 Zurcher, Christopher J [this message]
2020-02-14 0:40 ` [PATCH v3 1/2] CryptoPkg/OpensslLib: Add "sort" keyword to header file parsing loop Zurcher, Christopher J
2020-02-14 16:10 ` [edk2-devel] " Laszlo Ersek
2020-02-14 0:40 ` [PATCH v3 2/2] CryptoPkg/OpensslLib: Remove "no-autoalginit" flag from OpenSSL build Zurcher, Christopher J
2020-02-14 8:51 ` [edk2-devel] [PATCH v3 0/2] " Liming Gao
2020-02-22 4:28 ` Zurcher, Christopher J
2020-02-17 6:50 ` Wang, Jian J
2020-03-10 10:52 ` Laszlo Ersek
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=20200214004021.17300-1-christopher.j.zurcher@intel.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