-
Notifications
You must be signed in to change notification settings - Fork 40
feat(keyless): signing use case #859
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
Conversation
Signed-off-by: Jose I. Paris <jiparis@chainloop.dev>
migmartri
left a comment
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.
Awesome!
Signed-off-by: Jose I. Paris <jiparis@chainloop.dev>
| csr []byte | ||
| } | ||
|
|
||
| func (s *signingUseCaseTestSuite) TestSigningUseCase_CreateSigningCert() { |
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.
nitpick: I think this is smth I asked @javirln once, but is using _ i.e TestSigningUseCase_CreateSigningCert go idiomatic?
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.
It's the suggestion from the IDE, I believe it's some "idiomatic", but I don't think there is a written rule.
Signed-off-by: Jose I. Paris <jiparis@chainloop.dev>
Signed-off-by: Jose I. Paris <jiparis@chainloop.dev>
This is the first of a set of PRs to implement keyless signing in chainloop vault and CLI.
This PR focuses on the implementation of the signing use case. The use case receives a certificate request and signs it with a configured certificate authority. It uses some of the Sigstore logic for this purpose.
Refs #865