-
Notifications
You must be signed in to change notification settings - Fork 293
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Loader protocol (with Device Path resolution support) #656
Open
kukrimate
wants to merge
8
commits into
rhboot:main
Choose a base branch
from
kukrimate:loader-protocol
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains 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
kukrimate
force-pushed
the
loader-protocol
branch
3 times, most recently
from
April 18, 2024 10:54
d57be0b
to
b997ca7
Compare
kukrimate
commented
Apr 19, 2024
kukrimate
force-pushed
the
loader-protocol
branch
from
April 19, 2024 10:34
d748616
to
b5556cd
Compare
kukrimate
force-pushed
the
loader-protocol
branch
from
May 24, 2024 10:27
b5556cd
to
a791a4f
Compare
Define a new protocol for loading and starting images, encapsulating shim's PE loading facilities and verification/authentication against the same set of certificates that shim_lock::verify() authenticates against. This removes the need for loaders like GRUB to implement their own PE loader in order to be able to invoke loaded images as PE applications, rather than implementing a bespoke OS dependent handover protocol (e.g., invoke Linux via its EFI stub) Signed-off-by: Ard Biesheuvel <[email protected]>
Currently the EFI_SIMPLE_FILE_SYSTEM_PROTOCOL and EFI_LOAD_FILE2_PROTOCOL are supported. Signed-off-by: Mate Kukri <[email protected]>
This will bring SBAT enforcement in-line with the shim_lock protocol. Signed-off-by: Mate Kukri <[email protected]>
…in_protocol This isn't desirable when GRUB has control of the screen, and would mess its content up. Signed-off-by: Mate Kukri <[email protected]>
…et's respect this Signed-off-by: Mate Kukri <[email protected]>
kukrimate
force-pushed
the
loader-protocol
branch
from
October 22, 2024 07:39
15f9540
to
4f99c12
Compare
kukrimate
changed the title
[RFC] Loader protocol with support for device path resolution and loading executables
Loader protocol (with Device Path resolution support)
Oct 22, 2024
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.
This rebases the current loader protocol work on main and adds support for loading executables if only a device path is provided. Currently the EFI_SIMPLE_FILE_SYSTEM_PROTOCOL and EFI_LOAD_FILE2_PROTOCOL are supported, which should be sufficient for most users.