Timeline for UEFI Self-Signed Kernel loading from a Microsoft Signed OS Loader
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 21, 2022 at 14:03 | history | edited | NJP | CC BY-SA 4.0 |
MMX64
|
| Jan 21, 2022 at 7:15 | history | edited | NJP | CC BY-SA 4.0 |
Used shim
|
| Jan 18, 2022 at 5:35 | vote | accept | NJP | ||
| Jan 14, 2022 at 11:27 | answer | added | telcoM | timeline score: 3 | |
| Jan 14, 2022 at 10:06 | comment | added | Alex Baranowski | Well. It might be a little bit harder than you initially thought. Generally speaking, getting anything signed from Microsoft require quite a lot, and it's a good thing. It's pretty easy to compromise the whole secure boot idea by leaking a key [many people don't patch their firmware very often]. You can look at the Linux distros that are trying to get a secure boot key for their shims/grubs/kernels at the - github.com/rhboot/shim-review/issues | |
| Jan 14, 2022 at 9:38 | comment | added | NJP | Well not yet. It is just a thought that Microsoft will sign it. | |
| Jan 14, 2022 at 9:35 | comment | added | Alex Baranowski | Sorry for asking, but how did you manage to get your OS loader signed by Microsoft? | |
| Jan 14, 2022 at 9:33 | answer | added | Alex Baranowski | timeline score: 1 | |
| Jan 14, 2022 at 5:43 | history | asked | NJP | CC BY-SA 4.0 |