shim doesn't boot boot entries without spaces/zero characters in optional data

Bug #1965972 reported by Julian Andres Klode
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
shim (Ubuntu)
New
Undecided
Unassigned

Bug Description

shim ignores any optional data passed that does not contain a space or nul character.

bad fallback csv entry:

shimx64.efi,Ubuntu with kernel 5.4.0-1072-azure-cvm,\kernel.efi-5.4.0-1072-azure-cvm,Ubuntu entry for kernel 5.4.0-1072-azure-cvm

good csv, with additional space:

shimx64.efi,Ubuntu with kernel 5.4.0-1072-azure-cvm,\kernel.efi-5.4.0-1072-azure-cvm ,Ubuntu entry for kernel 5.4.0-1072-azure-cvm

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

given how cryptic optional data parsing in shim, I am not surprised.
last time I tried to figure out how to make it work, I failed.
so somewhat this sounds right that a space helps.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.