oxidecomputer / oxidecomputer/lpc55_support
Derive revocation bits from `root_certs`, etc.
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 13
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Refactoring the image signing routines (#28) left as an open TODO deriving the CFPA KeyStatus bits from root_certs (and whatever else we might need). If we pass the signing root (i.e., signing_certs[0]) then we can check that it occurs in root_certs, and maybe mark as Revoked? (I admit not understanding the difference between Revoked1 and Revoked2) the ones before that. But this appears to be partly a matter of policy rather than a stricly technical decision, so feedback would be welcome on how we intend to set and use these bits.
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 image signing routines changed by #28 and trace how CFPA KeyStatus, root_certs, and signing_certs[0] are represented. Clarify the intended policy for Revoked1 and Revoked2, including what happens to certificates before the signing root; done means the policy is agreed and the bits are derived consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- embedded-iot, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100