Bug 1401807 - Need a Cert/HCL process to better treat UEFI systems with/without secure boot.
Summary: Need a Cert/HCL process to better treat UEFI systems with/without secure boot.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Hardware Certification Program
Classification: Retired
Component: Policy Guide
Version: FEAT
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Jianwei Weng
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-06 07:07 UTC by Adam Ru
Modified: 2020-02-13 08:47 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-02-06 03:08:16 UTC
aru: needinfo-

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

Description Adam Ru 2016-12-06 07:07:08 UTC 
Hello Redhat team

this is a suggestion or enhancement request for better treat UEFI systems with/without secure boot. 

the Secure Boot is more and more popular, we plan to run Redhat hardware certification with both legacy BIOS and UEFI with secure boot. However the current Redhat certification policy process not allow list them as two certification. it only allow publish one and the other one as a kbase.

So we suggest RedHat to enhance Cert/HCL process to better treat UEFI systems with/without secure boot. 
thanks
Adam
Comment 4 Jianwei Weng 2020-02-05 08:25:54 UTC 
Hi VMware Team,

For the VMware certs, you have tested with both legacy BIOS and UEFI with secure boot, and we created the test plans for both, I am not sure if you still need this  bug?

Thanks
Jianwei
Comment 5 Adam Ru 2020-02-06 03:08:16 UTC 
this is open in year 2016 before we start the UEFI testing, there is no clear guidance how to choose between legacy BIOS and UEFI with secure boot.

now the legacy BIOS/UEFI will test as supplemental test depends on which is the default VM setting.

so, yes, we can close this bug.
Note You need to log in before you can comment on or make changes to this bug.