Bug 11530 - RMC:[EFI] modify shim to launch an EFI binary when not running in secure boot mode
Summary: RMC:[EFI] modify shim to launch an EFI binary when not running in secure boot...
Status: RESOLVED WONTFIX
Alias: None
Product: BSPs
Classification: Build System, Metadata & Runtime
Component: bsps-meta-intel (show other bugs)
Version: 2.4
Hardware: x86 Multiple
: Medium enhancement
Target Milestone: 2.4 M2
Assignee: Ng, Wei Tee
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2017-05-18 16:48 UTC by Todor Minchev
Modified: 2017-07-10 23:43 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Yes (doc changes required)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Todor Minchev 2017-05-18 16:48:45 UTC 
When running in non-secure boot mode, RMC just needs to start the next stage bootloader. Modify shim (https://github.com/rhinstaller/shim) to ignore secure boot options and just start the 2nd stage bootloader (load_image -> start_image).
Comment 1 Todor Minchev 2017-05-22 16:59:14 UTC 
Thinking about this again, shim will probably do this out of the box. 
It might be just a case of verifying if this is the case.
Comment 2 Todor Minchev 2017-07-10 23:43:49 UTC 
Closing this, we decided that RMC will not support secure boot out of the box.