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

Enhanced verification flow #150

Open
mhdawson opened this issue Nov 2, 2022 · 2 comments
Open

Enhanced verification flow #150

mhdawson opened this issue Nov 2, 2022 · 2 comments
Labels
enhancement New feature or request

Comments

@mhdawson
Copy link
Contributor

mhdawson commented Nov 2, 2022

Description

I think a typical use case will be a project that has N people who are authorized to sign artifacts (releasers in the case of the Node.js project - https://github.com/nodejs/node#release-keys) and the end user wants to be able to easily validate that one of those people have signed an artifact.

I think in the simplest flow where ephemeral keys have been used (which I think is really nice in that certificates don't have to be stored/managed), the equivalent is that the user will want to verify that the artifact has been signed by any one of a list of emails.

sigstore-python has the option -cert-email but that only validates against a single email which does not quite fit this use case. Instead something like a --cert-emails that allows you to provide a list or file containing a list of emails would simplify the verification.

@mhdawson mhdawson added the enhancement New feature or request label Nov 2, 2022
@bdehamer
Copy link
Collaborator

I'm working now to beef-up the verification flow right now and will definitely be adding support for signer identity verification (including the ability to supply a list of "authorized" signers).

@mhdawson
Copy link
Contributor Author

@bdehamer thanks for the update :)

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