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

[Scudo] Describe all configurations for handling in-toto layouts #10

Open
adityasaky opened this issue Jan 5, 2023 · 4 comments
Open

Comments

@adityasaky
Copy link
Contributor

Currently, the Scudo PURE specifies that every image must have a mapping to the in-toto layout to use to verify its software supply chain. @trishankatdatadog noted in #9 (comment) that this is one option and layouts for each image may be inferred or communicated to clients out of band. The PURE should explore both of these options and lay out the pros and cons for each.

See: #9, #2

@jhdalek55
Copy link
Contributor

@adityasaky Was this resolved? If so, then can you close it?

@adityasaky
Copy link
Contributor Author

I'd like @trishankatdatadog to weigh in here. I'm not 100% convinced we should describe a way where the layout information is not included for image. I think we can't do justice in describing out-of-band mechanisms to correctly associate layouts to images. In comparison, I think the con of including layout information (the current status of the document) is not very troubling as attackers can do more than just associate the wrong layout in that scenario.

@adityasaky
Copy link
Contributor Author

That said, I think we don't have to block #9 on this as we aren't marking it as "Final", per PURE-1.

@trishankatdatadog
Copy link
Member

I'd like @trishankatdatadog to weigh in here. I'm not 100% convinced we should describe a way where the layout information is not included for image. I think we can't do justice in describing out-of-band mechanisms to correctly associate layouts to images. In comparison, I think the con of including layout information (the current status of the document) is not very troubling as attackers can do more than just associate the wrong layout in that scenario.

We should describe the pros and cons of each option

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

No branches or pull requests

3 participants