From: "Laszlo Ersek" <lersek@redhat.com>
To: Gary Lin <glin@suse.com>, devel@edk2.groups.io
Cc: Jordan Justen <jordan.l.justen@intel.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: Re: [PATCH 1/1] OvmfPkg/README: Update the network build flags
Date: Tue, 11 Jun 2019 17:11:56 +0200 [thread overview]
Message-ID: <3eab3506-c8a0-5b96-dd80-c474e2e6c7eb@redhat.com> (raw)
In-Reply-To: <20190610065509.19573-1-glin@suse.com>
On 06/10/19 08:55, Gary Lin wrote:
> The following network build flags changed due to the inclusion of
> NetworkPkg/Network.fdf.inc.
>
> HTTP_BOOT_ENABLE -> NETWORK_HTTP_BOOT_ENABLE
> TLS_ENABLE -> NETWORK_TLS_ENABLE
>
> This commit also adds NETWORK_ALLOW_HTTP_CONNECTIONS to reflect the
> change in OvmfPkg/OvmfPkg*.dsc.
>
> Cc: Jordan Justen <jordan.l.justen@intel.com>
> Cc: Laszlo Ersek <lersek@redhat.com>
> Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=1884
> Signed-off-by: Gary Lin <glin@suse.com>
> ---
> OvmfPkg/README | 11 ++++++++---
> 1 file changed, 8 insertions(+), 3 deletions(-)
>
> diff --git a/OvmfPkg/README b/OvmfPkg/README
> index c014d07bfbdb..3dd28474ead4 100644
> --- a/OvmfPkg/README
> +++ b/OvmfPkg/README
> @@ -260,9 +260,14 @@ HTTPS Boot is an alternative solution to PXE. It replaces the tftp server
> with a HTTPS server so the firmware can download the images through a trusted
> and encrypted connection.
>
> -* To enable HTTPS Boot, you have to build OVMF with -D HTTP_BOOT_ENABLE and
> - -D TLS_ENABLE. The former brings in the HTTP stack from NetworkPkg while
> - the latter enables TLS support in both NetworkPkg and CryptoPkg.
> +* To enable HTTPS Boot, you have to build OVMF with -D NETWORK_HTTP_BOOT_ENABLE
> + and -D NETWORK_TLS_ENABLE. The former brings in the HTTP stack from
> + NetworkPkg while the latter enables TLS support in both NetworkPkg and
> + CryptoPkg.
> +
> + If you want to exclude the unsecured HTTP connection completely, OVMF has to
> + be built with -D NETWORK_ALLOW_HTTP_CONNECTIONS=FALSE so that only the HTTPS
> + connections will be accepted.
>
> * By default, there is no trusted certificate. The user has to import the
> certificates either manually with "Tls Auth Configuration" utility in the
>
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
Pushed as commit 1631bb26ae99.
Thank you!
Laszlo
prev parent reply other threads:[~2019-06-11 15:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 6:55 [PATCH 1/1] OvmfPkg/README: Update the network build flags Gary Lin
2019-06-11 15:11 ` 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-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=3eab3506-c8a0-5b96-dd80-c474e2e6c7eb@redhat.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