Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1180202

Summary: Overlap with uefi-secure-boot-guide
Product: [Retired] Fedora Documentation Reporter: Florian Weimer <fweimer>
Component: multiboot-guideAssignee: Chris Roberts <chris.roberts>
Status: CLOSED EOL QA Contact: Fedora Docs QA <docs-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: develCC: chris.roberts, me
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-07 15:30:02 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Florian Weimer 2015-01-08 15:40:13 UTC
With the recent updates, there is now some overlap with the UEFI Secure Boot guide.

I'm not sure the current state of Secure Boot is useful for non-dual-boot systems, considering the feature loss and the lack of additional security due to buggy kernels and permissive signed bootloaders from other vendors.  Perhaps merging the UEFI Secure Boot guide into the multiboot guide makes sense?

Comment 1 Pete Travis 2015-11-03 04:02:13 UTC
There was some discussion about this, but I didn't follow up here, apologies.  The UEFI Secure Boot Guide is a detailed technical reference, while I'm targeting the multiboot guide at new users, common issues, and procedural aids.  A lot of the content you're referring to should go to the UEFI Secure Boot guide, or is already there... but a merge would be too much scope creep.

I'll use this bug as a TODO for moving the more dry content out of the multiboot guide.

Comment 2 Petr Bokoc 2019-11-07 15:30:02 UTC
I'm closing this bug as part of a Bugzilla cleanup effort. The most likely reason is that the bug has been opened either against a component we no longer publish, or against Release Notes for an EOL release.