Non-security-critical bugs can be filed on the Issues tracker:
https://github.com/Microsoft/ms-tpm-20-ref/issues
Security sensitive bugs should be reported to [email protected]
This repository tracks official TPM Library Specification releases and errata from the Trusted Computing Group:
https://trustedcomputinggroup.org/tpm-library-specification/
All changes to core TPM logic, particularly changes to files in TPMCmd/tpm and its subdirectories, must be approved by TCG voting members. Github pull requests may be used to propose changes, but changes will not be incorporated without TCG member approval.
Other changes (e.g. new files or changes to TPMCmd/Platform or TPMCmd/Simulator), particularly to support new platforms, scenarios, build environments or crypto-libraries, will be considered if they are expected to be widely useful.
Contributors that wish to be involved in the future evolution of the TPM specification and reference implementation should consider joining the Trusted Computing Group. Information about membership and liaison programs is available at https://trustedcomputinggroup.org/membership/
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.
When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repositories using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.
If you are new, please read the documentation beginning with Introduction
The following are prerequisites before requesting change approval:
- Decide if the change is a feature or a bug fix and describe it accordingly
- Get a solid understanding of the change and the scope
- Decide specifically which versions of the TPM code need to be updated
Make sure you are familiar with the architecture of the TPM codebase
NOTE: If introducing multiple changes, treat each change individually creating a different branch and pull request for each change
This will make the code review (acceptance) process much easier