-
Notifications
You must be signed in to change notification settings - Fork 8
Initial verifiable builds docs #239
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
base: main
Are you sure you want to change the base?
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
| sidebar_position: 5 | ||
| --- | ||
|
|
||
| Verifiable builds provide cryptographic proof of the source code and build process for EigenCompute applications. EigenCompute verifiable builds |
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.
Make it clear they are linked: "Verifiable builds provide cryptographic proof linking the source code and build process..."
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.
Done
|
|
||
| When submitting a build with dependencies, provenance is validated and dependency digests are recorded in the build's SLSA provenance. | ||
|
|
||
| The EigenCompute TLS and KMS clients are prebuilt and the digests included in all EigenCompute applications. |
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.
In the Read me of the EigenCompute containers repo you can see the official digests there that we keep up to date. Maybe just link to those here?
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.
Done
|
|
||
| EigenCompute applications with dependencies other than the TLS and KMS clients must submit those verifiable builds and include | ||
| the dependency's image digest when verifiably building the application. | ||
|
|
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.
I think we should include the Google SLSA Providence public key that we use to verify everything? And possibly link out to Google's documentation on SLSA provenance.
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.
Yep - I need to add another topic for 'how to verify' and include those.
No description provided.