summaryrefslogtreecommitdiff
path: root/SecurityPkg/SecurityPkg.dec
diff options
context:
space:
mode:
authorBrijesh Singh <brijesh.singh@amd.com>2017-10-05 15:16:41 -0500
committerLaszlo Ersek <lersek@redhat.com>2017-10-17 21:28:26 +0200
commit071f1d19ddbc4abaaccbddfc7d6fcc5677f9b5c3 (patch)
tree613606109d69d3682585d996601449a11f170394 /SecurityPkg/SecurityPkg.dec
parent65c77f02104cf0cf7bd224df3a5fc08795df9aad (diff)
downloadedk2-071f1d19ddbc4abaaccbddfc7d6fcc5677f9b5c3.zip
edk2-071f1d19ddbc4abaaccbddfc7d6fcc5677f9b5c3.tar.gz
edk2-071f1d19ddbc4abaaccbddfc7d6fcc5677f9b5c3.tar.bz2
SecurityPkg: make PcdOptionRomImageVerificationPolicy dynamic
By default the image verification policy for option ROM images is 0x4 (DENY_EXECUTE_ON_SECURITY_VIOLATION) but the following OvmfPkg commit: 1fea9ddb4e3f OvmfPkg: execute option ROM images regardless of Secure Boot set it to 0x0 (ALWAYS_EXECUTE). This is fine because typically option ROMs comes from host-side and most of the time cloud provider (i.e hypervisor) have full access over a guest anyway. But when secure boot is enabled, we would like to deny the execution of option ROM when SEV is active. Having dynamic Pcd will give us flexibility to set the security policy at the runtime. Fixes: https://bugzilla.tianocore.org/show_bug.cgi?id=728 Cc: Chao Zhang <chao.b.zhang@intel.com> Cc: Jordan Justen <jordan.l.justen@intel.com> Cc: Laszlo Ersek <lersek@redhat.com> Cc: Tom Lendacky <thomas.lendacky@amd.com> Contributed-under: TianoCore Contribution Agreement 1.1 Signed-off-by: Brijesh Singh <brijesh.singh@amd.com> Reviewed-by: Jiewen Yao <jiewen.yao@intel.com> Reviewed-by: Long Qin <qin.long@intel.com>
Diffstat (limited to 'SecurityPkg/SecurityPkg.dec')
-rw-r--r--SecurityPkg/SecurityPkg.dec24
1 files changed, 12 insertions, 12 deletions
diff --git a/SecurityPkg/SecurityPkg.dec b/SecurityPkg/SecurityPkg.dec
index df4082b..50dbe95 100644
--- a/SecurityPkg/SecurityPkg.dec
+++ b/SecurityPkg/SecurityPkg.dec
@@ -234,18 +234,6 @@
#
[PcdsFixedAtBuild, PcdsPatchableInModule]
- ## Image verification policy for OptionRom. Only following values are valid:<BR><BR>
- # NOTE: Do NOT use 0x5 and 0x2 since it violates the UEFI specification and has been removed.<BR>
- # 0x00000000 Always trust the image.<BR>
- # 0x00000001 Never trust the image.<BR>
- # 0x00000002 Allow execution when there is security violation.<BR>
- # 0x00000003 Defer execution when there is security violation.<BR>
- # 0x00000004 Deny execution when there is security violation.<BR>
- # 0x00000005 Query user when there is security violation.<BR>
- # @Prompt Set policy for the image from OptionRom.
- # @ValidRange 0x80000001 | 0x00000000 - 0x00000005
- gEfiSecurityPkgTokenSpaceGuid.PcdOptionRomImageVerificationPolicy|0x04|UINT32|0x00000001
-
## Image verification policy for removable media which includes CD-ROM, Floppy, USB and network.
# Only following values are valid:<BR><BR>
# NOTE: Do NOT use 0x5 and 0x2 since it violates the UEFI specification and has been removed.<BR>
@@ -308,6 +296,18 @@
gEfiSecurityPkgTokenSpaceGuid.PcdStatusCodeSubClassTpmDevice|0x010D0000|UINT32|0x00000007
[PcdsFixedAtBuild, PcdsPatchableInModule, PcdsDynamic, PcdsDynamicEx]
+ ## Image verification policy for OptionRom. Only following values are valid:<BR><BR>
+ # NOTE: Do NOT use 0x5 and 0x2 since it violates the UEFI specification and has been removed.<BR>
+ # 0x00000000 Always trust the image.<BR>
+ # 0x00000001 Never trust the image.<BR>
+ # 0x00000002 Allow execution when there is security violation.<BR>
+ # 0x00000003 Defer execution when there is security violation.<BR>
+ # 0x00000004 Deny execution when there is security violation.<BR>
+ # 0x00000005 Query user when there is security violation.<BR>
+ # @Prompt Set policy for the image from OptionRom.
+ # @ValidRange 0x80000001 | 0x00000000 - 0x00000005
+ gEfiSecurityPkgTokenSpaceGuid.PcdOptionRomImageVerificationPolicy|0x04|UINT32|0x00000001
+
## Indicates the presence or absence of the platform operator during firmware booting.
# If platform operator is not physical presence during boot. TPM will be locked and the TPM commands
# that required operator physical presence can not run.<BR><BR>