summaryrefslogtreecommitdiff
path: root/MdeModulePkg/Library/PiDxeS3BootScriptLib/BootScriptInternalFormat.h
diff options
context:
space:
mode:
authorStanislaw Grams <stanislaw.grams@intel.com>2026-09-16 16:55:43 +0300
committermergify[bot] <37929162+mergify[bot]@users.noreply.github.com>2026-10-23 05:04:33 +0300
commitca211e68cc58bee8490dfde0b84a103f2804501d (patch)
tree3e3b36ec9277f8437f9b54df248bf32750451331 /MdeModulePkg/Library/PiDxeS3BootScriptLib/BootScriptInternalFormat.h
parentdabb4726988590e2db237d5caab6998b3c2c84ef (diff)
downloadedk2-ca211e68cc58bee8490dfde0b84a103f2804501d.tar.xz
OvmfPkg/IntelTdx: Enable Secure Boot and drop the shell by default
The Config-B TDX firmware shipped with SECURE_BOOT_ENABLE=FALSE and BUILD_SHELL=TRUE by default, so a default production build performed no Secure Boot image verification and embedded the full UEFI Shell, giving an attacker an unauthenticated command environment. Default SECURE_BOOT_ENABLE to TRUE and BUILD_SHELL to FALSE, matching the hardened AmdSevX64 posture. Both remain overridable on the build command line (-D FLAG=VALUE) for development. With Secure Boot enabled the shell FV is already excluded by ShellDxe.fdf.inc. Signed-off-by: Stanislaw Grams <stanislaw.grams@intel.com>
Diffstat (limited to 'MdeModulePkg/Library/PiDxeS3BootScriptLib/BootScriptInternalFormat.h')
0 files changed, 0 insertions, 0 deletions