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

Clarify meaning of signer as per confusion in slack #972

Conversation

NicoleSchwartz
Copy link
Contributor

As per slack https://openssf.slack.com/archives/C029E4N3DPF/p1695916703852369 conversation trying to clarify signer

@netlify
Copy link

netlify bot commented Sep 28, 2023

Deploy Preview for slsa ready!

Name Link
🔨 Latest commit 97ef2de
🔍 Latest deploy log https://app.netlify.com/sites/slsa/deploys/6515b67e5e94390008c6143b
😎 Deploy Preview https://deploy-preview-972--slsa.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

can sign provenance for the "GitHub Actions" builder, and "Google" can sign
provenance for the "Google Cloud Build" builder, but "GitHub" cannot sign for
the "Google Cloud Build" builder.
Consumers MUST accept only specific signer-builder pairs. The signer is the public key identity,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we want to clarify that it can be the public key identity or identity provider?

@MarkLodato
Copy link
Member

@NicoleSchwartz Do you plan to pick this up? If not, let's close. Thanks!

@MarkLodato MarkLodato closed this Nov 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

3 participants