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

Update packagecloud.io to fully sign packages #12

Closed
jaredledvina opened this issue Jul 4, 2018 · 3 comments
Closed

Update packagecloud.io to fully sign packages #12

jaredledvina opened this issue Jul 4, 2018 · 3 comments

Comments

@jaredledvina
Copy link

Currently, the https://packagecloud.io/app/sensu/nightly/ repo's are setup to have the metadata of the repo signed. However, the actual .deb and .rpm packages are not signed themselves. Signing the actually packages helps folks who run their own internal package mirrors verify that no one has tampered with them while to move around.

Expected Behavior

https://packagecloud.io/app/sensu/nightly/gpg#gpg-packagekeys should show package signing keys and/or the actual packages should be signed.

Current Behavior

The metadata on the repo's is signed currently, but the actual package files themselves are not.

Possible Solution

I'm not sure how https://sensu.global.ssl.fastly.net/apt/ and https://sensu.global.ssl.fastly.net/yum/ work but, perhaps we can steal the setup for those?

Context

Signed packages was my original blocker for deploying Sensu 1.X and this will also be a hard blocker for 2.X.

Your Environment

  • Sensu version used (sensuctl, sensu-backend, and/or sensu-agent): Lastest nightly
  • Installation method (packages, binaries, docker etc.): Ansible
  • Operating System and version (e.g. Ubuntu 14.04): Debian 9
@grepory
Copy link

grepory commented Jul 10, 2018

@preed and @amdprophet -- can we figure out how to get this done?

@preed
Copy link

preed commented Jul 10, 2018

Certainly we can look into it from a technology perspective, but I believe there's an additional release policy perspective (which, conveniently, we're in the middle of revisiting) which might impact what, exactly, we sign.

But I believe at some point, we'd want to sign the packages, so investigating the details as to how is certainly worth doing.

@grepory grepory transferred this issue from sensu/sensu-go Nov 20, 2018
@annaplotkin
Copy link

We are closing this in favor of #13.

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

No branches or pull requests

4 participants