-
Notifications
You must be signed in to change notification settings - Fork 59
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
Fixing CA Path Flag to be used and adding policy timestamp server flag #353
Merged
Merged
Changes from 1 commit
Commits
Show all changes
30 commits
Select commit
Hold shift + click to select a range
6d85e84
fixing ca path flag to be used and allowing timestamp server to be
ChaosInTheCRD 995e01a
adding tests
ChaosInTheCRD 7c04733
Merge branch 'main' into fixing-ca-path
ChaosInTheCRD d3ecb0e
fixing function definitions
ChaosInTheCRD 8aaf8b7
Merge branch 'fixing-ca-path' of github.com:ChaosInTheCRD/witness int…
ChaosInTheCRD 2f10938
Merge branch 'main' into fixing-ca-path
ChaosInTheCRD 3071f44
Merge branch 'main' of github.com:in-toto/witness into fixing-ca-path
ChaosInTheCRD a9189f0
added intermediates and made final changes
ChaosInTheCRD 2e00dc1
Merge branch 'fixing-ca-path' of github.com:ChaosInTheCRD/witness int…
ChaosInTheCRD 461a90c
passing cert constraint options into verify func
ChaosInTheCRD c289ad2
Merge branch 'main' into fixing-ca-path
ChaosInTheCRD 086a263
fixing if statement
ChaosInTheCRD 595a2f3
tidying up
ChaosInTheCRD a1a1955
forgot docgen
ChaosInTheCRD 220dc78
fixing gitignore issue
ChaosInTheCRD 541a8ed
Merge branch 'main' into fixing-ca-path
jkjell 002ba00
Merge branch 'main' into fixing-ca-path
ChaosInTheCRD a5697da
Merge branch 'main' of github.com:in-toto/witness into fixing-ca-path
ChaosInTheCRD b907b4c
Merge branch 'fixing-ca-path' of github.com:ChaosInTheCRD/witness int…
ChaosInTheCRD 11d8eaa
saving the flags for now, need to finish
ChaosInTheCRD e1e0afb
added the flags for fulcio extensions
ChaosInTheCRD ec2e837
Merge branch 'main' into fixing-ca-path
ChaosInTheCRD a0b9ff6
fixing the test
ChaosInTheCRD 2ba07f7
Merge branch 'fixing-ca-path' of github.com:ChaosInTheCRD/witness int…
ChaosInTheCRD d648399
running docgen
ChaosInTheCRD fd6d4de
Merge branch 'main' into fixing-ca-path
jkjell d1354de
Update to latest commit of go-witness after related PR merged
jkjell f320be5
policy json gone for some reason? adding it back
ChaosInTheCRD 8b85256
think i've been silly
ChaosInTheCRD 6e5265e
getting go-witness main
ChaosInTheCRD File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should address this todo as a part of this as well. The verification for a policy and an attestation should be the same I think.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah for sure. The only difference with policy is that there isn't going to be a policy document for verifying the policy... if that makes sense. So we ought to keep the number of ways that one can use to verify the policy signature small...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you think it makes sense to make all these changes in this PR?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would be the same as the step verification: https://github.com/in-toto/go-witness/blob/main/policy/policy.go#L230
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We're essentially defining the functionary from the CLI
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah the problem though is that defining all the available parameters for the functionaries from the CLI could quickly become unwieldly imo. Consider this functionary:
In this case, we would need to define:
How we would present that in a flag form I am not quite sure on. To me I think that limiting support for the number of policy signing mechanisms might be the way forward? It also seems to be the case to me that TUF may be a solution to this. @kairoaraujo any thoughts?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree that it is unwieldy, however I would normally expect the user to wrap this in a bash script, or maybe a "witness verify" github action. I also think we could provide some syntactic sugar for sigstore that would let us provide better UX for the common use case while being secure by default.
ex:
for enterprise use:
witness verify -p signedpolicy.json -k ca.pem -i int.pem --commonname="*" --dnsname="*" --email="[email protected]" --organization="*" --uri="*" --root="wippywoo" artifact.tar
for sigstore:
witness verify -p signedpolicy.json --use-sigstore --use-archivista --email="[email protected]" artifact.tar
We would also need to provide a TSA pem or add support for Rekor