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

Linux package repositories #26

Open
directionless opened this issue Sep 13, 2019 · 3 comments
Open

Linux package repositories #26

directionless opened this issue Sep 13, 2019 · 3 comments
Labels
moving parts This involved infra, accounts, or services we need to manage

Comments

@directionless
Copy link
Member

directionless commented Sep 13, 2019

Who has access to the package repositories? How do they work. Etc.

Would we want to think about https://packagecloud.io/ or some other hosted entity?

Relates to: #4

@theopolis
Copy link
Member

myself and @muffins are the only folks with write access to the package repositories. They are hosted in S3. I have a script that takes packages as input, places them into the right directory structure and performs various signing.

For macOS's pkg:

  • Unpackage and sign the binaries using my certificate.
  • Repackage and sign the pkg
  • Upload to S3

For apt:

For yum:

  • Use rpmsign to sign the rpms
  • Use createrepo to manage the repo
  • Upload the output directory tree to S3

@theopolis
Copy link
Member

It would be fairly easy to create pipeline like:

Azure nightly builds packages -> uploads to S3

As well as an Azure pipeline that builds tags -> signs -> uploads to S3

@muffins
Copy link

muffins commented Sep 25, 2019

For windows MSI and Chocolatey package:

  • Build locally
  • Use signtool.exe to sign osqueryd.exe, copy this to osqueryi.exe
  • Use the .\tools\deployment\make_windows_package.ps1 to generate a .nupkg and .msi
  • Sign using signtool.exe to sign the .msi
  • Upload both to S3 and Chocolatey

@theopolis theopolis added the moving parts This involved infra, accounts, or services we need to manage label Jul 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
moving parts This involved infra, accounts, or services we need to manage
Projects
None yet
Development

No branches or pull requests

3 participants