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

Sign provenance #105

Open
LourensVeen opened this issue Nov 3, 2021 · 0 comments
Open

Sign provenance #105

LourensVeen opened this issue Nov 3, 2021 · 0 comments

Comments

@LourensVeen
Copy link
Contributor

Intermediate results arrive with some metadata that includes a workflow graph describing how they were made. This provenance information is used in combination with the policies to determine what can be done with them and anything produced from them. This means that we depend on the sites that produced our inputs to give us correct provenance in order to be able to correctly apply policies from others.

There's nothing we can do if they lie to us, but at least we have to be able to prove that they did. So the provenance must be signed. Probably, each step needs to have a signature by whoever ran it that covers that step: its inputs, the compute asset, and the outputs. Since one step's outputs are another step's inputs, that should provide a closed chain. Do we need some kind of signature on the workflow inputs though? And should there be signatures on the images as well as on the provenance? Needs some thought.

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

1 participant