-
Notifications
You must be signed in to change notification settings - Fork 298
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
missing public key that we can use to verify OKD release downloads #2092
Comments
the gpg key used to sign releases resides in the mass open cloud cluster which is used to build the releases. It makes sense to have this key be publicly available. @JaimeMagiera thoughts on where it should reside? we should bring this topic up in the next community meeting. |
I have some thoughts, but let's bring it up in the meeting to give everyone a chance to chime in. Thanks for bringing this to our attention @dustymabe |
A brief off-topic: there is a container signature verification mechanism that, alternatively, you can use. Important note: Only works for First, find the sha256 repo digest:
Before (public key not imported):
Importing the public key
After (public key imported)
I don't know the context of this signature mechanism or if it will be valid in the future. I found it while searching for. |
The most recent release page (4.17.0-okd-scos.0) mentions:
but I can't find any public key uploaded somewhere to do that verification..
We need to make this available. It would probably be good to have it be distributed by another avenue other than GitHub; i.e. maybe https://okd.io/ ?
The text was updated successfully, but these errors were encountered: