From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org
Cc: "Markus Armbruster" <armbru@redhat.com>,
"Eric Blake" <eblake@redhat.com>,
"Daniel P . Berrange" <berrange@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: [Qemu-devel] [PATCH v3 0/4] fw_cfg: Add edk2_add_host_crypto_policy()
Date: Sun, 10 Mar 2019 01:47:45 +0100 [thread overview]
Message-ID: <20190310004749.27029-1-philmd@redhat.com> (raw)
Hi,
This series consists of:
- add fw_cfg_add_file_from_host()
- add edk2_add_host_crypto_policy() and the Edk2Crypto object
The Edk2Crypto object is used to hold configuration values specific
to EDK2.
The edk2_add_host_crypto_policy() function loads crypto policies
from the host, and register them as fw_cfg named file items.
So far only the 'https' policy is supported.
A usercase example is the 'HTTPS Boof' feature of OVMF [*].
Usage example:
$ qemu-system-x86_64 \
--object edk2_crypto,id=https,\
ciphers=/etc/crypto-policies/back-ends/openssl.config,\
cacerts=/etc/pki/ca-trust/extracted/edk2/cacerts.bin
(On Fedora these files are provided by the ca-certificates and
crypto-policies packages).
[*]: https://github.com/tianocore/edk2/blob/master/OvmfPkg/README
Since v2:
- Split of
Since v1:
- Addressed Michael and Laszlo comments.
Please review,
Phil.
v2: https://lists.gnu.org/archive/html/qemu-devel/2019-03/msg02522.html
v1: https://lists.gnu.org/archive/html/qemu-devel/2018-12/msg01598.html
Philippe Mathieu-Daudé (4):
hw/nvram/fw_cfg: Add fw_cfg_add_file_from_host()
hw/firmware: Add Edk2Crypto and edk2_add_host_crypto_policy()
hw/i386: Use edk2_add_host_crypto_policy()
hw/arm/virt: Use edk2_add_host_crypto_policy()
MAINTAINERS | 8 ++
hw/Makefile.objs | 1 +
hw/arm/virt.c | 7 +
hw/firmware/Makefile.objs | 1 +
hw/firmware/uefi_edk2_crypto_policies.c | 177 ++++++++++++++++++++++++
hw/i386/pc.c | 7 +
hw/nvram/fw_cfg.c | 21 +++
include/hw/firmware/uefi_edk2.h | 28 ++++
include/hw/nvram/fw_cfg.h | 23 +++
9 files changed, 273 insertions(+)
create mode 100644 hw/firmware/Makefile.objs
create mode 100644 hw/firmware/uefi_edk2_crypto_policies.c
create mode 100644 include/hw/firmware/uefi_edk2.h
--
2.20.1
next reply other threads:[~2019-03-10 0:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-10 0:47 Philippe Mathieu-Daudé [this message]
2019-03-10 0:47 ` [Qemu-devel] [PATCH v3 1/4] hw/nvram/fw_cfg: Add fw_cfg_add_file_from_host() Philippe Mathieu-Daudé
2019-03-11 7:15 ` Markus Armbruster
2019-03-10 0:47 ` [Qemu-devel] [PATCH v3 2/4] hw/firmware: Add Edk2Crypto and edk2_add_host_crypto_policy() Philippe Mathieu-Daudé
2019-03-11 7:26 ` Markus Armbruster
2019-03-11 18:27 ` Philippe Mathieu-Daudé
[not found] ` <5e2f3651-5f00-0c93-353e-e58f079998e9@redhat.com>
[not found] ` <124e54f9-c7e1-0157-61f1-673154872749@redhat.com>
2019-06-20 12:07 ` Philippe Mathieu-Daudé
2019-06-20 13:51 ` Laszlo Ersek
2019-03-10 0:47 ` [Qemu-devel] [PATCH v3 3/4] hw/i386: Use edk2_add_host_crypto_policy() Philippe Mathieu-Daudé
2019-03-10 0:47 ` [Qemu-devel] [PATCH v3 4/4] hw/arm/virt: " Philippe Mathieu-Daudé
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-all 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=20190310004749.27029-1-philmd@redhat.com \
--to=philmd@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=kraxel@redhat.com \
--cc=lersek@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).