-
Notifications
You must be signed in to change notification settings - Fork 0
Initial builder wrapper for swtpm #1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
b9c6ac3 to
3725aec
Compare
| - ubuntu-24.04 | ||
| - ubuntu-22.04 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we really need to test the prior Ubuntu version? What are we getting from testing it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are dependency differences between the two and as a rule of thumb we should generally be supporting and testing on the last 2 versions for the major distros.
f4c70e6 to
b712ba6
Compare
b712ba6 to
8fc36dc
Compare
Building
swtpmmight be a challenge depending on the target platform or OS. The primary goal is to simplify the user experience by removing the need to install external dependencies. This allows developers to focus on building applications around the Software TPM emulator without needing to manage additional system installations.When developing Elixir firmware for embedded Linux applications, developers can run the firmware on the developers host machine or the target hardware. While the target hardware may include a physical TPM, the host machine might not. This limitation can complicate proper testing of TPM-dependent features.
By using
swtpm, a software TPM emulator, developers can run a fully functional TPM on their host machine. Allowing for realistic testing of the firmware in an environment that closely mirrors the behavior of a physical TPM, without relying on additional mocks. This capability allows for better testing and might accelerate the development cycle since it's one less thing the team needs to worry about.