From: Gary Lin <glin@suse.com>
To: edk2-devel@lists.01.org
Subject: [PATCH 0/3] Enable HTTPS Boot in OVMF
Date: Tue, 17 Jan 2017 12:52:29 +0800 [thread overview]
Message-ID: <20170117045232.4765-1-glin@suse.com> (raw)
This series adjusts the build files of OVMF in order to support HTTPS.
It introdues a new build option, TLS_ENABLE, and makes OpenSSL a hard
requirement to enable IPv6 support.
Gary Lin (3):
OvmfPkg: always resolve OpenSslLib, IntrinsicLib and BaseCryptLib
OvmfPkg: correct the set of modules included for the IPv6 stack
OvmfPkg: pull in TLS modules with -D TLS_ENABLE (also enabling HTTPS)
OvmfPkg/OvmfPkgIa32.dsc | 29 ++++++++++++++++-------------
OvmfPkg/OvmfPkgIa32.fdf | 8 ++++----
OvmfPkg/OvmfPkgIa32X64.dsc | 29 ++++++++++++++++-------------
OvmfPkg/OvmfPkgIa32X64.fdf | 8 ++++----
OvmfPkg/OvmfPkgX64.dsc | 29 ++++++++++++++++-------------
OvmfPkg/OvmfPkgX64.fdf | 8 ++++----
6 files changed, 60 insertions(+), 51 deletions(-)
--
2.11.0
next reply other threads:[~2017-01-17 4:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 4:52 Gary Lin [this message]
2017-01-17 4:52 ` [PATCH 1/3] OvmfPkg: always resolve OpenSslLib, IntrinsicLib and BaseCryptLib Gary Lin
2017-01-17 8:03 ` Wu, Jiaxin
2017-01-17 9:13 ` Laszlo Ersek
2017-01-17 4:52 ` [PATCH 2/3] OvmfPkg: correct the set of modules included for the IPv6 stack Gary Lin
2017-01-17 8:04 ` Wu, Jiaxin
2017-01-17 9:22 ` Laszlo Ersek
2017-01-18 0:47 ` Wu, Jiaxin
2017-01-18 8:17 ` Laszlo Ersek
2017-01-18 9:21 ` Gary Lin
2017-01-19 3:09 ` Wu, Jiaxin
2017-01-19 8:36 ` Laszlo Ersek
2017-01-17 4:52 ` [PATCH 3/3] OvmfPkg: pull in TLS modules with -D TLS_ENABLE (also enabling HTTPS) Gary Lin
2017-01-17 8:04 ` Wu, Jiaxin
2017-01-17 9:24 ` Laszlo Ersek
2017-01-17 8:13 ` [PATCH 0/3] Enable HTTPS Boot in OVMF Long, Qin
2017-01-17 8:25 ` Jordan Justen
2017-01-17 20:13 ` Laszlo Ersek
2017-01-18 1:59 ` Gary Lin
2017-01-17 9:49 ` 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=20170117045232.4765-1-glin@suse.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