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

[feature] Add support for using a custom Sigstore deployment #3607

Open
lcarva opened this issue May 3, 2024 · 1 comment
Open

[feature] Add support for using a custom Sigstore deployment #3607

lcarva opened this issue May 3, 2024 · 1 comment
Labels
type:feature New feature or request

Comments

@lcarva
Copy link

lcarva commented May 3, 2024

Is your feature request related to a problem? Please describe.
I would like to use generator_container_slsa3 to generate SLSA Provenance for my container image but instead of using the public deployment of Sigstore, I would like to use my Sigstore deployment.

Describe the solution you'd like
Provide the ability to specify an alternative TUF mirror/root, Rekor, and Fulcio.

Describe alternatives you've considered
The alternative is to fork this repo and implement the changes there which works but does not benefit the community in general.

Additional context
This feature request has some overlap with #34. I'm happy to use that instead if the differences are not clear to others.

@lcarva lcarva added status:triage Issue that has not been triaged type:feature New feature or request labels May 3, 2024
@ianlewis
Copy link
Member

I think it's fine to have this issue. We intended for private sigstore (including TUF/Fulcio) to be in scope for #34 but it's not explicitly written there.

@ianlewis ianlewis removed the status:triage Issue that has not been triaged label May 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:feature New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants