From: Laszlo Ersek <lersek@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
qemu-devel@nongnu.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>
Subject: Re: [PATCH v8 5/5] crypto/tls-cipher-suites: Produce fw_cfg consumable blob
Date: Mon, 15 Jun 2020 08:16:46 +0200 [thread overview]
Message-ID: <157cdc98-98b5-00c1-86e5-f3f201299098@redhat.com> (raw)
In-Reply-To: <20200609170727.9977-6-philmd@redhat.com>
On 06/09/20 19:07, Philippe Mathieu-Daudé wrote:
> Since our format is consumable by the fw_cfg device,
> we can implement the FW_CFG_DATA_GENERATOR interface.
>
> Acked-by: Laszlo Ersek <lersek@redhat.com>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> ---
> v8: Add example in qemu-options.hx
> ---
> crypto/tls-cipher-suites.c | 19 +++++++++++++++++++
> qemu-options.hx | 19 +++++++++++++++++++
> 2 files changed, 38 insertions(+)
>
> diff --git a/crypto/tls-cipher-suites.c b/crypto/tls-cipher-suites.c
> index f02a041f9a..d6ea0ed190 100644
> --- a/crypto/tls-cipher-suites.c
> +++ b/crypto/tls-cipher-suites.c
> @@ -14,6 +14,7 @@
> #include "qemu/error-report.h"
> #include "crypto/tlscreds.h"
> #include "crypto/tls-cipher-suites.h"
> +#include "hw/nvram/fw_cfg.h"
> #include "trace.h"
>
> static void parse_cipher_suites(QCryptoTLSCipherSuites *s,
> @@ -99,11 +100,28 @@ static void qcrypto_tls_cipher_suites_finalize(Object *obj)
> g_free(s->cipher_list);
> }
>
> +static const void *qcrypto_tls_cipher_suites_get_data(Object *obj)
> +{
> + QCryptoTLSCipherSuites *s = QCRYPTO_TLS_CIPHER_SUITES(obj);
> +
> + return s->cipher_list;
> +}
> +
> +static size_t qcrypto_tls_cipher_suites_get_length(Object *obj)
> +{
> + QCryptoTLSCipherSuites *s = QCRYPTO_TLS_CIPHER_SUITES(obj);
> +
> + return s->cipher_count * sizeof(IANA_TLS_CIPHER);
> +}
> +
> static void qcrypto_tls_cipher_suites_class_init(ObjectClass *oc, void *data)
> {
> UserCreatableClass *ucc = USER_CREATABLE_CLASS(oc);
> + FWCfgDataGeneratorClass *fwgc = FW_CFG_DATA_GENERATOR_CLASS(oc);
>
> ucc->complete = qcrypto_tls_cipher_suites_complete;
> + fwgc->get_data = qcrypto_tls_cipher_suites_get_data;
> + fwgc->get_length = qcrypto_tls_cipher_suites_get_length;
> }
>
> static const TypeInfo qcrypto_tls_cipher_suites_info = {
> @@ -115,6 +133,7 @@ static const TypeInfo qcrypto_tls_cipher_suites_info = {
> .class_init = qcrypto_tls_cipher_suites_class_init,
> .interfaces = (InterfaceInfo[]) {
> { TYPE_USER_CREATABLE },
> + { TYPE_FW_CFG_DATA_GENERATOR_INTERFACE },
> { }
> }
> };
> diff --git a/qemu-options.hx b/qemu-options.hx
> index c74366d7cc..b12cc910e3 100644
> --- a/qemu-options.hx
> +++ b/qemu-options.hx
> @@ -4585,6 +4585,25 @@ SRST
> string as described at
> https://gnutls.org/manual/html_node/Priority-Strings.html.
>
> + An example of use of this object is to enable the UEFI HTTPS Boot.
(1) s/enable the/control/
(yes, please drop the "the")
> + The tls-cipher-suites object exposes the ordered list of permitted
> + TLS cipher suites from the host side to the firmware, via
(2) s/firmware/guest firmware/
> + fw_cfg. The list is represented as an array of IANA_TLS_CIPHER
> + objects. The firmware uses the IANA_TLS_CIPHER array for configuring
> + guest-side TLS.
> +
> + In the following example, the priority at which the host-side policy
> + is retrieved is given by the ``priority`` property of the new object
> + type. ``priority=@SYSTEM`` may be used to refer to
(3) s/ of the new object type//
Acked-by: Laszlo Ersek <lersek@redhat.com>
Thanks
Laszlo
> + /etc/crypto-policies/back-ends/gnutls.config (given that QEMU uses
> + GNUTLS).
> +
> + .. parsed-literal::
> +
> + # |qemu_system| \
> + -object tls-cipher-suites,id=mysuite0,priority=@SYSTEM \
> + -fw_cfg name=etc/edk2/https/ciphers,gen_id=mysuite0
> +
> ``-object filter-buffer,id=id,netdev=netdevid,interval=t[,queue=all|rx|tx][,status=on|off][,position=head|tail|id=<id>][,insert=behind|before]``
> Interval t can't be 0, this filter batches the packet delivery:
> all packets arriving in a given interval on netdev netdevid are
>
prev parent reply other threads:[~2020-06-15 6:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 17:07 [PATCH v8 0/5] fw_cfg: Add FW_CFG_DATA_GENERATOR; crypto: Add tls-cipher-suites Philippe Mathieu-Daudé
2020-06-09 17:07 ` [PATCH v8 1/5] hw/nvram/fw_cfg: Add the FW_CFG_DATA_GENERATOR interface Philippe Mathieu-Daudé
2020-06-15 5:43 ` Laszlo Ersek
2020-06-09 17:07 ` [PATCH v8 2/5] softmmu/vl: Let -fw_cfg option take a 'gen_id' argument Philippe Mathieu-Daudé
2020-06-15 5:47 ` Laszlo Ersek
2020-06-09 17:07 ` [PATCH v8 3/5] softmmu/vl: Allow -fw_cfg 'gen_id' option to use the 'etc/' namespace Philippe Mathieu-Daudé
2020-06-15 5:52 ` Laszlo Ersek
2020-06-09 17:07 ` [PATCH v8 4/5] crypto: Add tls-cipher-suites object Philippe Mathieu-Daudé
2020-06-15 6:10 ` Laszlo Ersek
2020-06-09 17:07 ` [PATCH v8 5/5] crypto/tls-cipher-suites: Produce fw_cfg consumable blob Philippe Mathieu-Daudé
2020-06-09 17:10 ` Philippe Mathieu-Daudé
2020-06-15 6:16 ` Laszlo Ersek [this message]
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=157cdc98-98b5-00c1-86e5-f3f201299098@redhat.com \
--to=lersek@redhat.com \
--cc=berrange@redhat.com \
--cc=kraxel@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@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).