You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently if I call uefi.Parse on an image with just a bunch of zeros inside, it will be parsed as a BIOS region with a padding.
While I use uefi.Parse to also verify if a received file is really an UEFI image (not something else). And a zero-file is a quite typical case. For example I faced this problem when another program (which extracts an UEFI image) just works wrong (and extracts a zero-image instead).
So the question is: do we consider parsing a bunch of zeros as a valid BIOS region a correct behavior (for fiano) or not?
The text was updated successfully, but these errors were encountered:
Currently if I call
uefi.Parse
on an image with just a bunch of zeros inside, it will be parsed as a BIOS region with a padding.While I use
uefi.Parse
to also verify if a received file is really an UEFI image (not something else). And a zero-file is a quite typical case. For example I faced this problem when another program (which extracts an UEFI image) just works wrong (and extracts a zero-image instead).So the question is: do we consider parsing a bunch of zeros as a valid BIOS region a correct behavior (for fiano) or not?
The text was updated successfully, but these errors were encountered: