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

Add support for recoginizing allow.pub as an spiffe issuer #228

Merged
merged 1 commit into from Oct 31, 2021

Conversation

evanphx
Copy link
Contributor

@evanphx evanphx commented Oct 30, 2021

Summary

Add support for fulcio to allow spiffe tokens signed by allow.pub

Description

I'm building an OCI registry that would like to perform server side
cosign support via fulcio. The OCI registry is called vcr.pub and should
be available in beta form soon.

The reason that the domain used here is allow.pub rather than vcr.pub is
one of the future services we'd like to support is other OIDC related
authentication tasks, so we've separated it from the OCI registry off
the bat.


url: https://allow.pub
contact: evan@phx.io
description: "Server side signing support for the OCI registry vcr.pub"
Copy link
Member

Choose a reason for hiding this comment

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

Neither vcr.pub or allow.pub resolve to anything meaningful in the browser. Perhaps include (comment?) a way to learn more?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Certainly! The websites are absolutely blank atm because I'm just getting those services up and going.

vcr.pub is the focus here, it's a simple, credit based OCI registry. Credit based meaning it's a bit like tarsnap where you pay upfront for credits and usage deducts from there. The idea is to build the best OCI registry that I want to use, which includes image signing, thus my interest in sigstore/fulcio.

vcr.pub is in alpha atm but I'd like to get the automated signing going before promoting it more, since this sort of integration is a great feature to talk about.

More than happy to answer any questions about it or anything else!

Copy link
Contributor Author

Choose a reason for hiding this comment

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

You make a great point, since I'm talking about these things outside my own tiny circle I should go ahead and at least provide something meaningful for browsers. I'll get that sorted out this weekend.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I've at least provided some redirects at https://allow.pub and https://vcr.pub for now.

@dlorenc
Copy link
Member

dlorenc commented Oct 30, 2021

Once you get the DCO fixed this should be good!

I'm building an OCI registry that would like to perform server side
cosign support via fulcio. The OCI registry is called vcr.pub and should
be available in beta form soon.

The reason that the domain used here is allow.pub rather than vcr.pub is
one of the future services we'd like to support is other OIDC related
authentication tasks, so we've separated it from the OCI registry off
the bat.

Signed-off-by: Evan Phoenix <evan@phx.io>
@evanphx
Copy link
Contributor Author

evanphx commented Oct 30, 2021

@dlorenc Ah! Ok, DCO fixed!

@dlorenc dlorenc merged commit 3d64a68 into sigstore:main Oct 31, 2021
@dlorenc
Copy link
Member

dlorenc commented Oct 31, 2021

This should be live!

@evanphx
Copy link
Contributor Author

evanphx commented Oct 31, 2021

@dlorenc Thank you!

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

Successfully merging this pull request may close these issues.

None yet

3 participants