Automated custom WPK packages creation

Wazuh provides an automated way of building WPK packages using docker so there is no need for any other dependency.

To create a WPK package follow these steps:


  • Docker

  • Git

Download our wazuh-packages repository from GitHub and go to the wpk directory.

$ git clone && cd wazuh-packages/wpk

Execute the script, with the different options you desire. This script will build a Docker image with all the necessary tools to create the WPK and run a container that will build it:

$ ./ -h
Usage: ./ [OPTIONS]

    -t,   --target-system <target>              [Required] Select target wpk to build [linux/windows]
    -b,   --branch <branch>                     [Required] Select Git branch or tag e.g.
    -d,   --destination <path>                  [Required] Set the destination path of package.
    -k,   --key-dir <path>                      [Required] Set the WPK key path to sign package.
    -a,   --architecture <arch>                 [Optional] Target architecture of the package [x86_64].
    -j,   --jobs <number>                       [Optional] Number of parallel jobs when compiling.
    -pd,  --package-directory <directory>       [Required for windows] Package name to pack on wpk.
    -o,   --output <name>                       [Required] Name to the output package.
    -c,   --checksum <path>                     [Optional] Generate checksum
    -h,   --help                                Show this help.

To use this tool, the previously required certificate and the key must be in the same directory.

Linux WPK

Below, you will find an example of Linux WPK package building.

# ./ -t linux -b v3.10.2 -d /tmp/wpk -k /tmp/keys -o LinuxAgent.wpk

Windows WPK

To build a WPK for Windows you need to first download an MSI package of the desired version:

# curl -O

Below, you will find an example of Windows WPK package building.

# ./ -t windows -b v3.10.2 -d /tmp/wpk -k /tmp/keys -o WindowsAgent.wpk -pd /tmp/wazuh-agent-3.10.2-1.msi

If the -c or --checksum option is used there will be a file containing the SHA512 checksum in the same output path or you can indicate where you want to store it.

Here you can see an example of how to build a WPK generation with checksum:

# ./ -t linux -b v3.10.2 -d /tmp/wpk -k /tmp/keys -o LinuxAgent.wpk -c /tmp/wpk_checksum