From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: "Yao, Jiewen" <jiewen.yao@intel.com>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
"Tian, Feng" <feng.tian@intel.com>,
"Zeng, Star" <star.zeng@intel.com>
Subject: Re: [PATCH 3/3] MdeModulePkg/DxeCore: Add UEFI image protection.
Date: Mon, 6 Feb 2017 14:52:45 +0000 [thread overview]
Message-ID: <CAKv+Gu_sYOip5mNO0O+H9oqz0gBU9-Yj_g=WZNuzQZCA9ao7tQ@mail.gmail.com> (raw)
In-Reply-To: <74D8A39837DF1E4DA445A8C0B3885C503A8E9938@shsmsx102.ccr.corp.intel.com>
On 6 February 2017 at 14:51, Yao, Jiewen <jiewen.yao@intel.com> wrote:
> Hi Ard
>
> That is a good question.
>
>
>
> We (Intel) discussed this internally.
>
> We do not know if there is any need to make it configurable, so we start
> from non-configurable, and see if there is any feedback from other one.
>
>
>
> Glad to hear your voice. We can define a policy like below: (I borrow some
> definition from security pkg)
>
>
>
> [PcdsFixedAtBuild, PcdsPatchableInModule]
>
> ## Set Image protection policy. The policy is bitwise.
>
> # If a bit is set, the image will be protected by DxeCore if it is
> aligned.
>
> # The code section becomes read-only, and the data section becomes
> non-executable.
>
> # If a bit is clear, the image will not be protected.<BR><BR>
>
> # BIT0 - Image from unknown device. <BR>
>
> # BIT1 - Image from firmware volume.<BR>
>
> # BIT2 - Image from OptionRom.<BR>
>
> # BIT3 - Image from removable media which includes CD-ROM,
> Floppy, USB and network.<BR>
>
> # BIT4 - Image from fixed media device which includes hard
> disk.<BR>
>
> # @Prompt Set Image protection policy.
>
> # @ValidRange 0x80000002 | 0x00000000 - 0x0000001F
>
>
> gEfiMdeModulePkgTokenSpaceGuid.PcdImageProtectionPolicy|0x00000002|UINT32|0x30001047
>
>
>
> I will use 0x2 as default policy, to maximize the compatibility. And you can
> set 0x1A or 0x1F for ARM. Is that OK?
>
Yes, that would be perfect. Thanks!
next prev parent reply other threads:[~2017-02-06 14:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-26 8:39 [PATCH 0/3] DXE Memory Protection Jiewen Yao
2017-01-26 8:39 ` [PATCH 1/3] UefiCpuPkg/CpuDxe: Add memory attribute setting Jiewen Yao
2017-02-03 8:51 ` Gao, Liming
2017-02-04 0:42 ` Yao, Jiewen
2017-02-06 3:27 ` Fan, Jeff
2017-02-06 3:58 ` Yao, Jiewen
2017-02-06 5:26 ` Fan, Jeff
2017-02-06 5:28 ` Yao, Jiewen
2017-01-26 8:39 ` [PATCH 2/3] ArmPkg/CpuDxe: Correct EFI_MEMORY_RO usage Jiewen Yao
2017-01-26 12:11 ` Leif Lindholm
2017-01-26 12:17 ` Yao, Jiewen
2017-01-26 8:39 ` [PATCH 3/3] MdeModulePkg/DxeCore: Add UEFI image protection Jiewen Yao
2017-02-03 8:39 ` Gao, Liming
2017-02-04 0:41 ` Yao, Jiewen
2017-02-04 3:39 ` Gao, Liming
2017-02-06 1:07 ` Tian, Feng
2017-02-06 1:39 ` Yao, Jiewen
2017-02-06 14:34 ` Ard Biesheuvel
2017-02-06 14:51 ` Yao, Jiewen
2017-02-06 14:52 ` Ard Biesheuvel [this message]
2017-02-06 17:52 ` Kinney, Michael D
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='CAKv+Gu_sYOip5mNO0O+H9oqz0gBU9-Yj_g=WZNuzQZCA9ao7tQ@mail.gmail.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