-
Notifications
You must be signed in to change notification settings - Fork 546
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
Add trusted-root create helper command #3876
Merged
Merged
Changes from 1 commit
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
2552371
Fixes #3700: add trusted-root create helper command
steiza ea1c77f
Linter fixes and docgen
steiza a53ec25
Fix Windows unit test
steiza e0041bb
Output via stdout instead of stderr
steiza 06284e2
Add ctlogs to `cosign trusted-root create`
steiza b3262d7
Replace `--rekor-url` with `--ignore-tlog`
steiza cab9148
Just use paths to files on disk
steiza f705836
Add the ability to supply multiple verification material
steiza b8d58d7
Don't panic if there's unexpected content in PEM file
steiza 1e7a436
remove trailing newline
steiza 1bd2b08
Simplify imports
steiza 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
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
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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.
@why do we remove the notice about conflicting flags? When I run
cosign verify
built from this branch with both--ca-roots file.pem
and--certificate-chain file.crt
, I'm getting the following error:so the "mutual exclusion" of these flags is still there - why then the change of the flags documentation, here and also in doc/cosign_trusted-root_create.md?
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.
Yes, so
cosign verify
supports both--certificate-chain
and--ca-roots
, but later we decided thatcosign trusted-root create
would only support--certificate-chain
. There isn't a--ca-roots
option forcosign trusted-root create
anymore.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.
would
--certificate-chain
support PEM files with multiple chains, or only a single one? If you have a PEM bundle with a dozen "top-level" self-signed CA root certificates, would you be able to usecosign trusted-root create
to create a trusted root JSON file or not? Would one had to "manually" split that bundle into multiple PEM files, one per certificate (or certificate chain)? Can you use--certificate-chain
multiple times?As mentioned on Slack , if you currently try to pass a PEM bundle with multiple CA root certificates as
--certificate-chain
, the generated JSON file is incorrect, or at least not what one would expect: it puts all of them in the same chain, with one certificate being the root, and the rest - Intermediates, even though they are all self-signed roots.The same issue is with parsing a timestamp certificate bundle with multiple certificates.
If these are use cases that we do not intend to support, let's explicitly state it in the documentation.