On 14.05.25 13:15, 'Felix Moessbauer' via EFI Boot Guard wrote: > Hi, > > we got reports from the field stating that the boot failed because the > efi variables could not be set and we bail out in this case. Handling this > gracefully is fixed in this series. > > Notes on testing: I was only able to test the "good" path. Testing the > bad path is tricky as I don't have an EFI implementation at hand that does > not support getting the boot part UUID. > > Changes since v1: > > - log messages as warning instead of error > > Best regards, > Felix > > Felix Moessbauer (2): > kernel-stub: only warn if device part uuid variable cannot be set > kernel-stub: fix nullptr deref on error getting boot part UUID > > main.c | 18 +++++++++++------- > 1 file changed, 11 insertions(+), 7 deletions(-) >
Thanks, applied. I was briefly wondering if the second fix this could also be security relevant, but we would be consistently crashing due to strlen(NULL). Jan -- Siemens AG, Foundational Technologies Linux Expert Center -- You received this message because you are subscribed to the Google Groups "EFI Boot Guard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/efibootguard-dev/a79ea4f7-a600-46a5-be2b-bd5dcfe5cc23%40siemens.com.
