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

Windows: script to produce an osquery choco package #2393

Closed
muffins opened this issue Aug 17, 2016 · 5 comments

Comments

Projects
None yet
3 participants
@muffins
Copy link
Contributor

commented Aug 17, 2016

No description provided.

@muffins muffins self-assigned this Aug 17, 2016

@theopolis

This comment has been minimized.

Copy link
Contributor

commented Aug 29, 2016

The make packages (or equiv .bat script) should produce an osquery choco package.

@theopolis theopolis changed the title Build MSI/EXE Bundle for installation Windows: script to produce an osquery choco package Aug 29, 2016

@theopolis theopolis added the packaging label Aug 29, 2016

@theopolis

This comment has been minimized.

Copy link
Contributor

commented Aug 29, 2016

Here's the existing CMake logic, which only calls to a script in tools: https://github.com/facebook/osquery/blob/master/CMake/Packages.cmake

And the Linux/OS X script: https://github.com/facebook/osquery/tree/master/tools/deployment
That "deployment" directory includes other package artifacts that may be nice on Windows too.

@svmastersamurai

This comment has been minimized.

Copy link
Contributor

commented Sep 30, 2016

Just letting y'all know: consider generating APPX packages as well. With the advent of Server 2016 Nano that is the only format you can install software in that environment since MS ripped out all the GUI components. Maybe in version 2.0?? ;)

@theopolis

This comment has been minimized.

Copy link
Contributor

commented Sep 30, 2016

APPX should be relatively straightforward. We can create the package from a build host, push the result to our intermediate storage (a NAS on the Jenkins server), then periodically scan and sign (manual process) and finally ship/host on S3.

We host the apt/yum repos this way and serve symlinks to the latest package for each supported platform except for Windows.

The project needs 2 things:

  1. A script within the osquery repository to generate the APPX after a build.
  2. Logic/tooling to pull apart the APPX, sign binaries, then rebuild.*

*For OS X, PKG and Mach-O binary signing is proprietary so we have both a Linux signing/package host and an OS X one; if we need to add a third that not a huge issue.

@muffins

This comment has been minimized.

Copy link
Contributor Author

commented Jan 18, 2017

I'm going to consider this issue closed, as #2890 brought in a powershell script to give us this logic. If we need to open up a new issue exploring APPX or package signing or whatnot feel free to open a new issue.

@muffins muffins closed this Jan 18, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.