From: "Laszlo Ersek" <lersek@redhat.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
edk2-devel-groups-io <devel@edk2.groups.io>
Cc: Leif Lindholm <leif@nuviainc.com>,
Peter Jones <pjones@redhat.com>,
Matthew Garrett <mjg59@google.com>,
Alexander Graf <agraf@csgraf.de>,
Daniel Kiper <daniel.kiper@oracle.com>,
Arvind Sankar <nivedita@alum.mit.edu>
Subject: Re: [edk2-devel] [PATCH 1/1] OvmfPkg IA32: add support for loading X64 Linux images
Date: Fri, 14 Feb 2020 22:43:34 +0100 [thread overview]
Message-ID: <4715e9d7-ebfa-7ae6-86f9-0f7c3c761416@redhat.com> (raw)
In-Reply-To: <CAKv+Gu-twaeZxhSDFeG1AM+JPHrfe_146cyvniU+6zFX_Ffsww@mail.gmail.com>
On 02/14/20 16:05, Ard Biesheuvel wrote:
> On Fri, 14 Feb 2020 at 15:45, Laszlo Ersek <lersek@redhat.com> wrote:
>> (5) Can you please explain how EDKII_PECOFF_IMAGE_EMULATOR_PROTOCOL
>> relates to Secure Boot and/or Trusted Boot?
>>
>> (5a) Is the ".compat" section included in the image hashing?
>>
>
> Yes.
>
>> (5b) Does the DXE core subject such non-native images to verification /
>> measurement at all? (Sorry I didn't follow your original work on
>> EDKII_PECOFF_IMAGE_EMULATOR_PROTOCOL.)
>>
>
> Yes. They are treated entirely like ordinary images, with all the
> policy checks regarding authentication and measurement.
[...]
Thank you!
Laszlo
prev parent reply other threads:[~2020-02-14 21:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 11:41 [PATCH 1/1] OvmfPkg IA32: add support for loading X64 Linux images ard.biesheuvel
2020-02-14 14:45 ` Laszlo Ersek
2020-02-14 15:05 ` [edk2-devel] " Ard Biesheuvel
2020-02-14 21:43 ` 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=4715e9d7-ebfa-7ae6-86f9-0f7c3c761416@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