aarch64: gaps between PE/COFF sections?
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 169
- Forks
- 42
- PR merge metrics
- No merged PRs in 30d
Description
When building latest 4.0.2 for aarch64 and then signing some app, the tools issue warnings:
# sbsign --cert cert.pem --key my.key aarch64/apps/printenv.efi
warning: data remaining[42496 vs 52747]: gaps between PE/COFF sections?
warning: data remaining[42496 vs 52752]: gaps between PE/COFF sections?
Signing Unsigned original image
# sbverify --cert cert.pem aarch64/apps/printenv.efi.signed
warning: data remaining[44344 vs 54600]: gaps between PE/COFF sections?
Signature verification OK
Is that known? It seems harmless in practice but it leaves strange feelings, specifically as I just had to sort out various issues with gaps for arm binaries, though caused by downstream build procedures.
Contributor guide
No contributing guide indexed for this repository
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
Reproduce the warning with the aarch64/apps/printenv.efi artifact built from version 4.0.2, then run the sbsign and sbverify commands shown in the report. Trace the generated PE/COFF sections and determine whether the gaps originate in gnu-efi; done means the warning's cause and whether it requires a project change are established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100