-
Notifications
You must be signed in to change notification settings - Fork 22
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
Support for Delivered Public Key Certificates #592
Conversation
7c4be37
to
a057e4d
Compare
898fac5
to
e914fb3
Compare
pkg/signing/signutils/certs.go
Outdated
|
||
type Usages []interface{} | ||
|
||
// Specification specified the xontext for the certificate creation. |
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.
typos
// Specification specified the xontext for the certificate creation. | |
// Specification specifies the context for the certificate creation. |
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.
fixed
pkg/signing/signutils/certs.go
Outdated
|
||
PublicKey GenericPublicKey | ||
|
||
// CAPrivateKey is the provate key used for signing. |
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.
typo
// CAPrivateKey is the provate key used for signing. | |
// CAPrivateKey is the private key used for signing. |
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.
fixed
1c53a98
to
37e0aaa
Compare
Description
Support for Public Key certificates has been added, the certificates are published together with the component version
as part of the signature.
If a signature validation is done a public key can be omitted now, if the signature contains a valid
certificate chain for a public key certificate. Additionally to the chain validation the Issuer (Distinguished Name) is checked
for the the public key certificate.
With a dedicated option (--tsa) a signed timestamp (TSA) is stored along with the signature, which is used (if set)
to specify the verification time for the certificate chain. A signature is only accepted if the certificate chai can be verified
for the signing time and the timestamp can be verified.
The commands have been extended to
Internally the the issuer has been migrated from a string to a pkix.Name.
The DN match checks for the existence of given attributes in the public key certificate.
The config has been extended to define expected issuers for signature names and a TSA server URL.
What type of PR is this? (check all applicable)
Related Tickets & Documents
Screenshots
Added tests?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Added to documentation?
Checklist: