Support new TPMDirect API
- Dominant language
- C
- Stars
- 309
- Forks
- 118
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 33
Description
Are there any plans to refactor go-tpm-tools to use the new TPMDirect API in go-tpm/tpm2?
Anyone using the new TPMDirect API and wants to use go-tpm-tools ends up with a bloated binary that includes the old and new APIs.
I think using the old API here also makes trying to navigate the docs for go-tpm and figuring out how to stitch the libraries together to create a new, future-proofed project more difficult and misleading with all the references to the old lib.
Contributor guide
Research direction
Start by comparing go-tpm-tools' current use of the old go-tpm API with the TPMDirect API in go-tpm/tpm2, including the dependency and documentation concerns described in the issue. Done means go-tpm-tools uses the new API without pulling in both APIs and no longer guides users toward the old API.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- security
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100