Skip to content
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

Certificate Chain Validation via Cosign #639

Open
garantir-km opened this issue Apr 25, 2022 · 2 comments
Open

Certificate Chain Validation via Cosign #639

garantir-km opened this issue Apr 25, 2022 · 2 comments
Labels
enhancement New feature or request

Comments

@garantir-km
Copy link

Describe the feature
Multiple customers would like to use connaisseur in their environment with signing certificates issued from their own custom organizational CA (e.g., an internal PKI that does not make use of Fulcio). This requires them to be able to perform certificate chain validation.

Cosign has just recently added the ability to achieve this by combining both the --cert and the new --cert-chain flags. However, connaisseur currently only supports verifying signatures using a public key, which means it does not support this new feature.

Could you please include the ability to verify signatures using both --cert and --cert-chain ?

@xopham
Copy link
Collaborator

xopham commented Apr 26, 2022

@garantir-km I like that request, as using signing certificates offers very strong security guarantees and a cert chain would add revocation.
The key interface is currently re-worked (#540) which will make adding more and different key types much easier. Besides keyless and rsa keys, cert validation should definitely be added.

I have an idea as to why organizations may want to use signing certificates, but would you mind sharing your reasoning for preferring certificates?

@xopham xopham added the enhancement New feature or request label Apr 26, 2022
@garantir-km
Copy link
Author

@xopham Our reason is purely to support our larger customers that are made up of multiple divisions that each sign their images with different signing certificates. In some cases the different divisions want to trust each other, and in other cases they may not. By supporting configurable certificate chains, these customers have the flexibility to deploy a trust model that meets their specific requirements.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants