IEIT logging support
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.1k
- Forks
- 348
- PR merge metrics
- No merged PRs in 30d
Description
Currently, when validation is disabled, shim doesn't make any attempt to validate signatures at all. It would be better to always validate them and log the results in the IEIT ("Image Execution Information Table"), but not /honor/ the validation results if disabled. This allows admins and tooling use the IEIT to determine which keys and hashes they actually need in their db/dbx/kek.
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
No files, tests, or entry points are named. Start by locating shim's signature-validation and IEIT handling, then trace the behavior when validation is disabled; done means signatures are still validated and their results are logged in the IEIT without affecting acceptance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100