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
Set KeyUsage properly for CA certs #2896
Conversation
@@ -58,8 +58,7 @@ func (p *Plugin) buildCertificateRequest(request *upstreamauthorityv1.MintX509CA | |||
Request: csrBuf.Bytes(), | |||
IsCA: true, | |||
Usages: []cmapi.KeyUsage{ | |||
cmapi.UsageDigitalSignature, | |||
cmapi.UsageCertSign, |
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 found another bug that the same KeyUsage was set, fixed at the same time
self-signedbefore
after
nesteddownstream spire-ca
after
|
73175a9
to
b20f658
Compare
Signed-off-by: Tomoya Usami <tousami@zlab.co.jp>
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.
Thank you so much for this fix, @hiyosi !
Signed-off-by: Tomoya Usami tousami@zlab.co.jp
Pull Request check list
Affected functionality
SPIRE Server CA
Description of change
Set KeyUsage properly for CA certs.
No longer set KeyUsage
DigitalSignature
for CA certs.Which issue this PR fixes
fixes #2811