From: rebecca@bluestop.org
To: "Lu, XiaoyuX" <xiaoyux.lu@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
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 15:26:51 -0600 [thread overview]
Message-ID: <49280c46-1faa-5f3a-72ad-36f79c4473f6@bluestop.org> (raw)
In-Reply-To: <15A95C72ACE0D0D5.4869@groups.io>
On 2019-06-18 11:53, rebecca@bluestop.org wrote:
> On 2019-06-18 02:52, Lu, XiaoyuX wrote:
>> 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?
>
> I set up a Linux environment to test, and found that it does actually
> work there after all. So it seems the breakage is limited to running
> OVMF built on FreeBSD, which I'll work on myself to fix.
>
>
Sorry - actually, I realized I was only testing the NOOPT build on
FreeBSD, and on Linux the NOOPT build also doesn't work, while RELEASE
does. And on FreeBSD the RELEASE and DEBUG builds work, but just NOOPT
doesn't.
Could you check if the NOOPT OVMF build works with HTTPS on your system,
please?
--
Rebecca Cran
next prev parent reply other threads:[~2019-06-18 21:26 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
2019-06-18 17:53 ` rebecca
[not found] ` <15A95C72ACE0D0D5.4869@groups.io>
2019-06-18 21:26 ` rebecca [this message]
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=49280c46-1faa-5f3a-72ad-36f79c4473f6@bluestop.org \
--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