RFE: add protocol to let 2nd/3rd stage loaders append ephemerally to MokListRT
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.1k
- Forks
- 348
- PR merge metrics
- No merged PRs in 30d
Description
These days MokListRT certificates are consumed by the kernel and added to the machine keyring, which can be linked into the secondary keyring, which allows using those certificates, among other things, for verifying kernel modules and dm-verity images.
We'd like to extend UKIs with a .keyring section. As part of the UKI, it would be covered by the UKI's signature. systemd-stub would parse this new section, and append the content to the Mok variable that is read by the kernel.
It was mentioned by @vathpela that the preference would be to add a new protocol for this, rather than letting other stages simply write directly to the variable, due to concerns with variable sizes, even when they are volatile.
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 or tests are named. Start by tracing how systemd-stub parses UKI sections and how the Mok variable is consumed by the kernel, then review the proposed protocol for second- and third-stage loaders. Done means an agreed protocol and support for an ephemeral .keyring section covered by the UKI signature.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- operating-systems, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100