Skip to content
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

Use in-toto CycloneDX predicate to be compatible with cosign #1270

Merged
merged 3 commits into from
Oct 19, 2022

Conversation

lehors
Copy link
Contributor

@lehors lehors commented Oct 17, 2022

This addresses Issue #1268

As noted in in-toto/attestation#82 (comment) it is not clear what the predicate value should really be but this change leaves that question to in-toto and ensures alignment with other tools such as cosign.

Signed-off-by: Arnaud J Le Hors [email protected]

@lehors lehors marked this pull request as draft October 17, 2022 15:29
@lehors
Copy link
Contributor Author

lehors commented Oct 17, 2022

I'm told the CycloneDX project has discussed the matter and decided to use the same value as what syft is currently using. So, I'm changing this to a draft PR. We should wait for the in-toto definition to be updated before applying this PR.
See in-toto/attestation#82 (comment)

@kzantow
Copy link
Contributor

kzantow commented Oct 17, 2022

Thanks for the follow-up @lehors!

@lehors lehors marked this pull request as ready for review October 18, 2022 18:56
@lehors
Copy link
Contributor Author

lehors commented Oct 18, 2022

The decision by the CycloneDX project is now official:
https://cyclonedx.org/specification/overview/#recognized-predicate-type

And in-toto-goland has been updated accordingly:
in-toto/in-toto-golang#188

I think it makes sense to merge this PR. It will make no difference in how syft works but it makes the code cleaner.

@spiffcs
Copy link
Contributor

spiffcs commented Oct 18, 2022

Yea Happy to merge this so we're using the value from the in-toto library. Really appreciate the follow up on this @lehors!

@spiffcs
Copy link
Contributor

spiffcs commented Oct 18, 2022

I think we just need to update this PR with the latest in-toto-golang

@lehors
Copy link
Contributor Author

lehors commented Oct 18, 2022

I think we just need to update this PR with the latest in-toto-golang

Indeed, I had just thought about that: I also need to update go.mod to get the newer version. I don't know what your policy is with regard to dependencies. Would you rather wait for the next official release of in-toto-golang so we can simply use the new tag? I think that's fine, there is no hurry.

Signed-off-by: Christopher Phillips <[email protected]>
@spiffcs
Copy link
Contributor

spiffcs commented Oct 18, 2022

Just pushed a commit that has the latest from main @anchore/tools let me know if you think we should just wait for the next release

@lehors
Copy link
Contributor Author

lehors commented Oct 19, 2022

Looks good. I think you can go ahead and merge this now. Thanks!

@spiffcs spiffcs merged commit d3ee240 into anchore:main Oct 19, 2022
aiwantaozi pushed a commit to aiwantaozi/syft that referenced this pull request Oct 20, 2022
GijsCalis pushed a commit to GijsCalis/syft that referenced this pull request Feb 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants