Documentation request: guidance for Microsoft's signing questionnaire
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.1k
- Forks
- 348
- PR merge metrics
- No merged PRs in 30d
Description
There are a number of questions that Microsoft asks about UEFI signing submissions that I wasn't sure how best to answer. I figure these answers should be pretty generic for anyone trying to get a shim submission signed, so it'd be great if the answers could be publicly documented in this repo:
Do any of the products in this submission load or execute any other code prior to ExitBootServices()? If so, please explain how the code is loaded, authorized, and executed.
Do any of the products in this submission take any user input? If so, what input validation is performed?
Do any of the products in this submission take any programmatic input (files on disk, UEFI variables, etc.)? If so, what input validation is performed?
Do any of the products in this submission use OpenSSL? If so, which version?
Do any of the products in this submission consist of EfiByteCode? If so, what platforms are supported?
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
Start with the five Microsoft questionnaire prompts in this issue and review the repository's UEFI signing context before drafting guidance. Done means each question has a generic, publicly documented answer suitable for shim submissions; no target documentation file or test is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100