-
-
Notifications
You must be signed in to change notification settings - Fork 58
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
Sign packages, turn on GPG verification #303
Comments
Yeah, signing the packages with our key would be great. |
According to http://blog.packagecloud.io/eng/2015/07/20/yum-repository-internals/
So the repo metadata is gpg signed, and file checksums are in that signed metadata. Looks not bad. IF signing the metadata is NOT enough, then you need:
|
@armab Yep, I was on their channel and someone else had the same questions. And yep, 1-4 is what I had in mind. |
Seems now it's possible to import own GPG key for repo, the PackageCloud feature announced in Jun, 2017: https://blog.packagecloud.io/eng/2017/06/08/announcing-package-signing-gpg-key-support/ With this, we can potentially sign the packages during the build with own key before uploading.
|
Awesome! We should do this ASAP. Bring this up as part of 18.04 support work we'll do. |
According to packagecloud, they only sign the package meta. The gpg verify is turned off on packages explicitly. I think we need to start signing those packages via st2-packages before shipping it to packagecloud. We also need to add a step in install script to download st2 gpg keys and install it. Also, figure out how to turn on gpg verification with packagecloud.
The text was updated successfully, but these errors were encountered: