including a self-generated key should be optional
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- C
- Stars
- 1.1k
- Forks
- 348
- PR merge metrics
- No merged PRs in 30d
Description
the internal key for signing fb.efi and mm.efi should be optional, and shouldn't be created by default. It also should have a much, much better name than "Testing CA Certificate".
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
The issue names no files, tests, or entry points. Start by tracing how the internal signing key and the “Testing CA Certificate” are generated for fb.efi and mm.efi, then identify the existing signing tests or build checks; done means generation is optional, disabled by default, and the certificate has an agreed clearer name.
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
- Needs clarification
- Newbie friendliness
- 35/100