A zero image is currently parsed as a BIOS region with a padding. Is that an intended behavior?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 373
- Forks
- 59
- PR merge metrics
- No merged PRs in 30d
Description
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?
Contributor guide
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 by reproducing the reported behavior with uefi.Parse on an image containing only zeros and inspect how the parser classifies it. The issue is resolved once the project decides and verifies whether that classification is valid or should be rejected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100