From: "Xiaoyu Lu" <xiaoyux.lu@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"rebecca@bluestop.org" <rebecca@bluestop.org>
Cc: "Wang, Jian J" <jian.j.wang@intel.com>, Laszlo Ersek <lersek@redhat.com>
Subject: Re: [edk2-devel] Problems using HTTPS boot: Http->Request can't find TLS Service Binding Protocol
Date: Tue, 18 Jun 2019 08:52:08 +0000 [thread overview]
Message-ID: <BFD21A70FD4B3446B866B6088E3259E50B9777AC@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <09db8908-09be-f303-b705-56586b69246d@bluestop.org>
Hi bcran,
I test this in my own environment, It works well.
The edk2 commit id : f03859ea6c8fddeaa3a5cc3d9a3461
Build command:
build -p ~/code/edk2/OvmfPkg/OvmfPkgX64.dsc -a X64 -t GCC5 -D NETWORK_TLS_ENABLE -D NETWORK_HTTP_BOOT_ENABLE
DHCP server: Internet Systems Consortium DHCP Server 4.3.3
Do you enroll your ca cert in Tls Auth Configuration?
Could you give us more information?
Thanks,
Xiaoyu
> -----Original Message-----
> From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of
> rebecca@bluestop.org
> Sent: Tuesday, June 18, 2019 8:44 AM
> To: devel@edk2.groups.io; Laszlo Ersek <lersek@redhat.com>
> Subject: Re: [edk2-devel] Problems using HTTPS boot: Http->Request can't
> find TLS Service Binding Protocol
>
> On 2019-06-17 16:14, rebecca@bluestop.org wrote:
> > I'm having problems using HTTPS boot in OVMF: Http->Request can't find
> > the EFI_TLS_SERVICE_BINDING_PROTOCOL.
> >
>
> It appears the OpenSSL update broke it. Revision b739678918 works, but
> f03859ea6c doesn't.
>
>
> --
> Rebecca Cran
>
>
>
next prev parent reply other threads:[~2019-06-18 8:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <15A91C212A9A35C2.15755@groups.io>
2019-06-18 0:43 ` [edk2-devel] Problems using HTTPS boot: Http->Request can't find TLS Service Binding Protocol rebecca
2019-06-18 8:52 ` Xiaoyu Lu [this message]
2019-06-18 17:53 ` rebecca
[not found] ` <15A95C72ACE0D0D5.4869@groups.io>
2019-06-18 21:26 ` rebecca
2019-06-19 8:07 ` Xiaoyu Lu
2019-06-19 13:40 ` rebecca
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=BFD21A70FD4B3446B866B6088E3259E50B9777AC@SHSMSX101.ccr.corp.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