-
Notifications
You must be signed in to change notification settings - Fork 50
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
[feature][byob] verification for sha1 provided by TRW for v0.2 #599
Comments
Doesn't that break our main use case which was for things like jReleaser which would be a builder rather than a generator? |
sorry. I meant we need to fail if options like |
blocked on #604 |
If we are allowing users to specify a different sha1 then probably we shouldn't look at the GitHub event's |
Correct. For BYOB, we should allow that. Today we verify both, we'll have to relax the verification on the GitHub event's |
I found that while we do verify that both had the same repository, we didn't really verify that the sha or tag/branch ref were the same between the source and trigger. Though I believe that the builders have always specified the same values, we just never verified it. |
Blocked on slsa-framework/github-actions-buildtypes#4 |
verification counterpart for slsa-framework/slsa-github-generator#2079
To think about: if the sha1 != GitHub event, options like
--source-branch
,--source-tag
or another source option should fail because we can no longer trust the event?For generators, I think it's fine to trust keep the code as-is because the options refer to the trigger workflow. For builders, I think we need to fail.
The text was updated successfully, but these errors were encountered: