Support for accessing material stored in a local TPM
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 50
- Forks
- 36
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 2
Description
Some authentication material (eg, x.509 certificates) might be stored in a local TPM rather than in files. For example, if TLS is used to protect traffic to and from the block device on which the root filesystem is stored, keeping certificates in the root filesystem is probably not feasible.
To use a TPM, some mechanism might access the TPM and move the needed authentication material into a keyring that can then be accessed by tlshd.
Contributor guide
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 tlshd's authentication-material and keyring interfaces, then determine how a local TPM could supply certificates or related material without relying on the root filesystem. Done requires an agreed TPM access mechanism and corresponding implementation and validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, linux
- Domain
- operating-systems, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100