content: draft: Add attested build environment track #1115
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for slsa ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
4 tasks
marcelamelara
force-pushed
the
attested-build-env-track
branch
2 times, most recently
from
e505871
to
5a2a961
Compare
|
FYI if you want to make the linter happy easily this might help. The linter caused me a ton of trouble until I figured this out. |
TomHennen
reviewed
Aug 16, 2024
marcelamelara
changed the title
marcelamelara
force-pushed
the
attested-build-env-track
branch
from
cbf816f
to
7a39858
Compare
marcelamelara
added
the
build-environment-track
paveliak
reviewed
Aug 26, 2024
This was referenced Aug 26, 2024
marcelamelara
force-pushed
the
attested-build-env-track
branch
2 times, most recently
from
dbc5dd1
to
8846927
Compare
marcelamelara
force-pushed
the
attested-build-env-track
branch
2 times, most recently
from
8df324b
to
08b92e8
Compare
deeglaze
reviewed
Sep 18, 2024
This was referenced Sep 23, 2024
deeglaze
reviewed
Sep 29, 2024
Signed-off-by: Marcela Melara <marcela.melara@intel.com>
Signed-off-by: Marcela Melara <marcela.melara@intel.com>
Signed-off-by: Marcela Melara <marcela.melara@intel.com>
Signed-off-by: Marcela Melara <marcela.melara@intel.com>
Signed-off-by: Marcela Melara <marcela.melara@intel.com>
Co-authored-by: Dionna Amalie Glaze <drdeeglaze@gmail.com> Signed-off-by: Marcela Melara <marcela.melara@intel.com>
Signed-off-by: Marcela Melara <marcela.melara@intel.com>
Signed-off-by: Marcela Melara <marcela.melara@intel.com>
marcelamelara
force-pushed
the
attested-build-env-track
branch
from
4610a2c
to
c0c8105
Compare
Signed-off-by: Marcela Melara <marcela.melara@intel.com>
Co-authored-by: Andrew McNamara <arewm@users.noreply.github.com> Signed-off-by: Marcela Melara <marcela.melara@intel.com>
Signed-off-by: Marcela Melara <marcela.melara@intel.com>
This was referenced Oct 15, 2024
Explicitly mention that BuildEnv L2 build platform MUST verify the SLSA Provenance OR its VSA.
#1196
Open
TomHennen
approved these changes
Oct 15, 2024
TomHennen
changed the title
|
FYI updated title to indicate this is draft! |
This was referenced Oct 21, 2024
arewm
approved these changes
Oct 21, 2024
There was a problem hiding this comment.
Thanks for this draft content. Many of the topics that I have raised have moved to issues. Partially for my reference (because there were so many threads), I think the conversation has moved here:
- Potential clarification for hosted terminology: Rename "hosted" to "dedicated"? #947
- Which parts of the build system should this apply to: Clarify that it's the CI's control plane that gives it privileged access #1211
- Clarifications of where/how to use provenance vs VSA: Clarify where to use SLSA Provenance vs. VSA #974; Move source track VSA info to the VSA spec? #1148
- Missing figure: Add figures for build environment track spec #1165
- Consistency of terminology/definitions: Link build environment terms to their definitions #1177 (additionally, build image producer should be explicit about the party/parties involved content: draft: Add attested build environment track #1115 (comment))
- Agent-less build environments: Cover use case of build environments without a build agent #1185
- Connection between build and build environment track: Clarify the connection between the Build and BuildEnv tracks #1210
- Attestation flow including how/when to verify: Document detailed attested build environment verification flow #1169
- VM and container differentiation: More cleanly separate container vs. VM requirements in BuildEnv L2+ #1192
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces the following spec changes associated with #975. The spec enhancements are being proposed as the new "build Environment track".
Spec changes: Adds new high-level build environment terminology and levels.
Part 1 of #975 CC @paveliak