shim does not attempt to load chained bootloader again after enrolling keys
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.1k
- Forks
- 348
- PR merge metrics
- No merged PRs in 30d
Description
After shim refuses to load a chained bootloader, and a corresponding key is enrolled via shim's menu, “Continue boot” does not result in another attempt to load, but instead exits shim. On real hardware this typically results in a failed boot error from the BIOS, leaving the user puzzled about whether the key they enrolled is the correct one. After a reboot everything works, but shim could be a bit more user-friendly in this regard, I think.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at shim's menu handling for “Continue boot” and trace the chained-bootloader refusal path after a key is enrolled. Done means selecting “Continue boot” retries the chained bootloader without requiring a reboot, while preserving the existing behavior when loading still fails.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100