Repository navigation
docs(wiki): explain optional TPM and Secure Boot - #4
Merged
Merged
Conversation
Document optional boot security without making it an installation gate. Explain the development launcher flags and distinguish VM evidence from EAC v2 compliance. Replace blanket advice to disable Secure Boot with checksum and firmware troubleshooting in both locales.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The installation guide recommends disabling Secure Boot when the live image does not start, without explaining the supported boot path or the consequences of changing firmware settings. It also leaves the distinction between optional platform features and game-specific requirements unclear.
Add English and Brazilian Portuguese guides explaining TPM 2.0 and Secure Boot as independent, optional features. Replace the blanket disablement advice with checksum and firmware troubleshooting, and link the new guides from the installation instructions and sidebar.
Document the QEMU options introduced by luminusOS/images#27, including their prerequisites and persistent per-VM state. Keep the development status explicit and distinguish observed boot behavior from the guest verification and attestation still needed before claiming EAC Linux v2 compliance.
The Wiki check and embedded build pass with these changes.